|
|
| (3 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| {{header|infra}} | | {{header|infra}} |
| {{shortcut|ISOP:SUPERVISOR}}
| |
|
| |
|
| {{Admon/important | This SOP is slowly going by the wayside. Almost all new apps are being deployed using mod_wsgi. See - [[TurboGears Infrastructure SOP]]}} | | {{admon/important|All SOPs have been moved to the Fedora Infrastructure [https://pagure.io/infra-docs/ SOP git repository]. Please consult the [https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/sops/index.html online documentation] for the current version of this document.}} |
| | |
| Supervisor is a service that supplements the normal !SystemVinit on a machine. It is configured via a config file /etc/supervisord.conf which is managed by puppet. The config file contains an entry for each service that it is in charge of starting. Supervisor handles starting the services at bootup and also respawning in case of errors. People can connect to the supervisor process via the supervisorctl command to manage services even if they don't have root on the box.
| |
| | |
| We use supervisor to control all of our TurboGears apps. (Almost all of our in-house web applications)
| |
| | |
| == Contact Information ==
| |
| Owner: Fedora Infrastructure
| |
| | |
| Contact: #fedora-admin, sysadmin-web group
| |
| | |
| Persons: lmacken, abadger199, ricky, mmcgrath
| |
| | |
| Location: Phoenix Colo
| |
| | |
| Servers: app[1-4] , releng1, publictest1
| |
| | |
| Purpose: We use supervisor to control all of our TurboGears apps. (Almost all of our in-house web applications)
| |
| | |
| === Supervisorctl Commands ===
| |
| <pre>
| |
| supervisorctl status
| |
| </pre>
| |
| <pre>
| |
| supervisorctl tail -f [SERVICE NAME]
| |
| </pre>
| |
| <pre>
| |
| supervisorctl restart [SERVICE NAME]
| |
| </pre>
| |
| | |
| == Troubleshooting and Resolution ==
| |
| | |
| [COMMON ISSUES AND HOW TO FIX THEM]
| |
|
| |
|
| [[Category:Infrastructure SOPs]] | | [[Category:Infrastructure SOPs]] |
