What is the main function of the startup script `start.sh` written by "author fesion" in the AnQiCMS task schedule?

In the daily operation of AnQiCMS (AnQiCMS), the stable operation of the system is the key to ensuring user experience and content distribution efficiency.To ensure that the AnQiCMS service can provide content continuously and uninterruptedly, even if it encounters an unexpected interruption, a meticulously designed startup script plays a crucial role in the scheduled task.Among them, written by 'author fesion'start.shThe script is born for this, it constitutes the core of the self-protection mechanism of AnQiCMS services.

start.shThe core function of the script

start.shThe main function of the script is to monitor the running status of the AnQiCMS application and ensure that it runs continuously in the specified path.In short, it is a lightweight watchdog script that regularly checks if the AnQiCMS main program is running.Once the service stops running, it will immediately attempt to restart the program to minimize service downtime and ensure the continuous availability of the website.This mechanism is crucial for enhancing the robustness and automated operation capabilities of AnQiCMS, especially suitable for small and medium-sized enterprises and self-media operators with limited resources, which can maintain the online status of the service without complex manual intervention.

Analysis of the working principle of the script

thisstart.shThe script is implemented through a series of standard Bash commands. The script first defines two key variables:BINNAME(The name of the AnQiCMS executable program, default asanqicms), andBINPATH(The absolute path of the AnQiCMS program). These variables allow users to flexibly configure according to the actual deployment, ensuring that the script can accurately find and operate the target program.

The core logic of the script is a conditional judgment: it usesps -ef | grep '\<anqicms\>' | grep -v grep | wc -la command chain to check if a system exists namedanqicmsprocess.ps -efList all processes,grep '\<anqicms\>'Filter out processes related to AnQiCMS (\<\>Used for precise matching to prevent matching other unrelated processes containing 'anqicms' in the filename)grep -v grepexcludegrepThe process itself, lastwc -lCount the number of lines that meet the conditions, that is, the number of running AnQiCMS processes.

If the detection results indicate that the number of AnQiCMS processes is zero (i.e.exists -eq 0)，The script will determine that AnQiCMS is "not running". At this point, it will executecd $BINPATH && nohup $BINPATH/$BINNAME >> $BINPATH/running.log 2>&1 &command to start AnQiCMS.nohupThe command ensures that the AnQiCMS program can continue to run in the background even if the terminal session is closed.>> $BINPATH/running.log 2>&1Then the program's standard output and standard error are redirected torunning.logIn the file, for subsequent log analysis and fault troubleshooting. The entire startup process is performed asynchronously in the background, to avoid blocking the script's execution.

For easy tracking, the script will also record the results of each check and the startup attempts.$BINPATH/check.logIn the file, detailed records of the time and process status were kept, which provided valuable audit clues for operations personnel.

Integration with AnQiCMS scheduled tasks

start.shScripts are typically configured for Linux systemscrontabSchedule a task to run automatically at fixed time intervals (for example, once a minute).In this way, the AnQiCMS service can achieve nearly real-time fault recovery capability.Once the program crashes for any reason (such as memory overflow, code error, external attack, or system resource exhaustion), the scheduled task will detect and restart it in a short period of time, greatly improving the availability of the service.This automated management method is exactly the embodiment of AnQiCMS's 'lightweight and efficient' operation concept, allowing users to focus more energy on content creation and business development rather than being busy dealing with technical failures.

Frequently Asked Questions (FAQ)

1. Ifstart.shThe script is not working as expected, how should I troubleshoot the problem?First, checkBINPATHandBINNAMEAre the variables correctly configured in the script, ensuring they point to the actual path and name of the AnQiCMS executable. Next, checkcheck.logThe file can be used to understand the script's execution history and process detection results, which can help determine whether the script has been correctly scheduled and whether there are any issues with its detection logic. Ifrunning.logThere is content, checking the error information may reveal the reasons for the startup failure of the AnQiCMS program. Finally, you can try to execute manually./start.shObserve the output or use it directly on the serverps -ef | grep anqicmsManually check the process status using the command

2. Whystart.shDoes the script need to run once a minute? Will this frequency consume too many system resources?tostart.shSet to run every minute to achieve rapid fault recovery. If the AnQiCMS service crashes unfortunately, it can be detected and automatically restarted at the latest within one minute.start.shIt is a very lightweight script, mainly performing process checks and simple file I/O operations, with negligible resource consumption.Only when AnQiCMS is indeed not running, will it attempt to perform a real program startup, thus this frequency will not impose a significant burden on system resources, and it is an effective strategy to ensure high availability of the service.

3. When deploying multiple AnQiCMS instances on the same server,start.shWhat are the points that need special attention in the script?When running multiple AnQiCMS instances on the same server, each instance needs to have its independentstart.shscript (or parameterize the main script), and each script must containBINNAMEandBINPATHThe variable must point to independent AnQiCMS executable programs and their installation paths. In addition, each AnQiCMS instance also needs to beconfig.jsonConfigure a unique running port and correctly map it in reverse proxies such as Nginx.Ensure that each instance's scripts, binary files, configuration files, and log files are independent to avoid conflicts and confusion.