Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
| Excerpt | ||
|---|---|---|
| ||
Supervisord is a process manager that can be used to control scripts as a service. |
Recommended Articles
| Info |
|---|
We recommend to read the following articles before continuing with this tutorial. |
What is supervisord?
Supervisord is a process manager that can be used to control scripts as a service. See http://supervisord.org/.
We offer this process manager with two options:
Option 1: we configure Root360 configures the supervisor service to run the command the customer requiresyou require
Option 2: the customers can You write and configure supervisord services themselvesyourself
To use supervisord, open a ticket and write us at service@root360.de what you need it for.
After we understand what you need, we install and configure supervisor on the needed systems . Supervisord can then be used by the customer.using either option 1 or 2.
Details on Option 2: running services yourself
| Note |
|---|
The customer is You are responsible for the configuration and correct functioning of their your supervisor services! |
Functionality
A supervisord service is started in the context of the user www-data. This monitors a shared path to supervisord We set up supervisord to monitor a path where it will look for service configuration files.
Requirements for these configuration files are:
File suffix must be
.confMay only contain the configuration for '
[program]' ( . See http://supervisord.org/configuration.html#program-x-section-settings ).Has only access to the Webrootwebroot
may May not depend on defining the option '
user' as the program service is always started as userwww-data.
Supervisord is automatically restarted after each deployment, so that new and changed configuration for new supervisord services can be imported and started.
Logging
Supervisord logs all output and errors to /var/log/application/supervisord_www-data/ on the server instance on which it is running.
These logs, like all logs in /var/log/application/ (see also Standard Logging (root360) ) are registered in the central log system and collected on the jump server (see also Standard Logging (root360)).
Process control
All configured processes services and the supervisor can be controlled by the following command:
| Code Block | ||
|---|---|---|
| ||
sudo -u www-data supervisorctl -c /etc/supervisor/supervisord_www-data.conf |
(For more information about the command, see http://supervisord.org/running.html#supervisorctl-command-line-options )
Related tutorials
| Filter by label (Content by label) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Related components
| Filter by label (Content by label) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
| Table of Contents | ||
|---|---|---|
|
| Filter by label (Content by label) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
E