The Supervisor manager is one of the most commonly asked-about applications. For this reason, I have compiled here some common issues with the Supervisor manager for you to reference before asking questions.
Q: Project startup failed with error run supervisorctl start xxx failed, and there is information like EACCES` in the log.
A: This is a permission issue. It is recommended to deploy the project in the panel installation directory (such as /www) instead of /root. If you insist on deploying in /root, you need to start the application using the root user and bear any potential risks yourself.
If you still get an error after moving the project to the installation directory, please check if the project’s owner and group are set to www.
Q: Project startup failed with error run supervisorctl start xxx failed, and there is information like ‘node’: No such file or directoryor’npm’: No such file or directoryin the log. A: If you installed Node.js via nvm or similar (official installation method), Node.js and npm will not be found by default (they are not linked to /usr/local/bin). In this case, you need to edit the configuration file in the Supervisor manager, add a new line at the end withenvironment=PATH="/root/.nvm/versions/node/version/bin:/usr/local/bin:/usr/bin:/bin"` to specify the location of Node.js.
The specific location and version of Node.js can be viewed via whereis nodejs.
Q: PHP project startup failed with an error that the extension cannot be found, but the extension is clearly installed.
A: This issue occurred because the earlier panel incorrectly set 700 permissions on the php.ini configuration file, which caused Supervisor to use the www user to start PHP but cannot read the configuration file, so it would not load additional extensions. This issue has been optimized and resolved after 2025/04/11. For historical installations, you can modify the php.ini file to 644 permissions and set the owner to root to fix the issue. The php.ini file is located in the /www/server/php/version/etc directory.