As an experienced website operations expert, I know that AnQiCMS, an enterprise-level content management system developed based on the Go language, has occupied a place in the hearts of many operators with its high efficiency, lightweight, and high concurrency characteristics.It brings great convenience to small and medium-sized enterprises and content operation teams, but even the most excellent system cannot do without meticulous operation and maintenance management.start.shThe path situation. When this path changes, it is responsible for scheduling automated tasks.crontabIt must also be updated synchronously; otherwise, your AnQiCMS may fail to start or run maintenance tasks as expected, leading to service interruption or data anomalies.

Today, let's delve deep into how to quickly and accurately updatestart.shthe script path changes after AnQiCMScrontabtasks to ensure the continuous and stable operation of your website service.

start.shScript andcrontabthe symbiotic relationship

in the deployment of AnQiCMS, especially when manually deploying on Linux servers or non-containerized deployment,start.shThe script plays a core role.It is usually responsible for checking if the AnQiCMS process is running, if not, it will start the AnQiCMS main program and may record the output to a log file.

whilecrontab, it is the built-in task scheduler of the Linux system, which allows users to execute specified commands or scripts at preset time points. To ensure the high availability of AnQiCMS services, we often configure acrontabTask, run every interval (such as every minute)start.shScript, let it check and maintain the online status of AnQiCMS service.

需要特别强调的是，crontabWhen executing a task, it usually does not inherit the current user's environment variables, therefore, its resolution of the script path isstrictly dependent on the absolute path. That is why whenstart.shWhen the physical storage location of the script changes,crontabthe paths referenced in it must also be updated.

Whystart.shWill the script path change?

caused bystart.shThe reasons for the change of the script path are many, common scenarios include:

  1. Server directory structure adjustment：For the need of system management, storage optimization, or unified specifications, operations personnel may move the installation directory of AnQiCMS from, for example,/www/wwwroot/anqicmsto/opt/anqicmsor to other custom paths.
  2. Website migration and re-deploymentEnglish: The new installation path may be different from the old path when migrating AnQiCMS from one server to another or when redeploying it on the same server.
  3. Version upgrade and managementAlthough AnQiCMS 3.x version recommends using the "Go project" feature for management in panels like Baota, this does not mean that this method is adopted in all deployment scenarios.start.shThe script is still the core component. Its position or file structure may be adjusted after certain specific upgrades or code refactoring.
  4. Multi-site management：In some complex self-built multi-site environments, it may be set to have an independent directory for each AnQiCMS instance, when these directories need to be moved, the correspondingstart.shThe path will also change.

For any reason, oncestart.shthe path changes, the originalcrontabtask is like a compass that can't find its way, and it cannot work normally.

quickly updatecrontabThe steps of the task

UpdatecrontabTask to adaptstart.shThe new path of the script, it is a direct but careful process. The following are the specific operation steps:

  1. Confirmstart.shThe new absolute path and grant execution permissionsPlease make sure to confirm your AnQiCMS before making any modificationsstart.shwhere the script is currently locateda complete and accurate absolute path. For example, if it is located at/data/anqicms/start.shPlease remember this path. Also, confirm that the script has execution permissions. You can check by running in the terminalls -l /path/to/new/start.shIf execution permissions are missing (usually displayed as-rw-r--r--Instead of-rwxr-xr-xPlease use the commandchmod +x /path/to/new/start.shGrant its execution permission

  2. Access and editcrontabConfiguration fileEnter the command in the Linux terminalcrontab -e. This command will open the current user'scrontabConfiguration file. It usually opens it using the default text editor of your system (such as Nano or Vim).

  3. Locate and modify the task entries related to AnQiCMS.In the openedcrontabfile, carefully search for the lines related to AnQiCMS service. These lines usually containstart.shoranqicmssuch keywords. You might see something like: 

    */1 * * * * /www/wwwroot/anqicms/start.sh

    This entry. After finding it, simply replace the old absolute path with the newly confirmed path. For example, change it to:

    */1 * * * * /data/anqicms/start.sh

    If your AnQiCMS deployment also includesstop.shScript it and include itcrontabManage it and update its path accordingly.

  4. Save and exitcrontabFileAfter completing the path modification, you need to save and exitcrontabfile.

    • If you are usingnanoEditor: PressCtrl+XEnter, then inputYConfirm save, finally pressEnterkey.
    • If you are usingvimEditor: Enter:wq（write and quit）then pressEnterkey. After the save is successful, the system will usually promptcrontab: installing new crontab, which means your changes have taken effect.

  5. to verify whether the task has been updated and executed successfullyUpdatecrontabAfter, it is crucial to validate immediately.

    • CheckcrontabList: Usecrontab -lCommand to view againcrontabList to ensure the modification has been saved correctly.
    • Run the new script manually: Run the new path manually once in the terminal.start.shScript (for example)cd /data/anqicms && ./start.sh).
    • Check AnQiCMS process: Useps -ef | grep anqicmsCommand to check if the main process of AnQiCMS has started successfully. You should see the relevant process information.
    • View log file: Checkstart.shInternal log file of the script, for examplecheck.logorrunning.log(If yourstart.shThe script is configured), confirm that the AnQiCMS service is running healthily and there are no error messages.

By following these steps, you can ensure that AnQiCMS services continue to run stably under high availability mechanisms, even if the location of its startup script changes.

EnhancementcrontabTask robustness**practice

To make the AnQiCMS backend task management more robust, the following are some