Migration is not required, as supervisord will still continue to function.
# apt-get remove -y supervisord
We'll use systemd to control the daemonization of NetBox services. First, copy
contrib/netbox-rq.service to the
# cp contrib/*.service /etc/systemd/system/
These service files assume that gunicorn is installed at
/usr/local/bin/gunicorn. If the output of
which gunicorn indicates a different path, you'll need to correct the
ExecStart path in both files.
You may need to modify the user that the systemd service runs as. Please verify the user for httpd on your specific release and edit both files to match your httpd service under user and group. The username could be "nobody", "nginx", "apache", "www-data" or any number of other usernames.
Then, start the
netbox-rq services and enable them to initiate at boot time:
# systemctl daemon-reload # systemctl start netbox.service # systemctl start netbox-rq.service # systemctl enable netbox.service # systemctl enable netbox-rq.service
You can use the command
systemctl status netbox to verify that the WSGI service is running:
# systemctl status netbox.service ● netbox.service - NetBox WSGI Service Loaded: loaded (/etc/systemd/system/netbox.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2019-12-12 19:23:40 UTC; 25s ago Docs: https://netbox.readthedocs.io/en/stable/ Main PID: 11993 (gunicorn) Tasks: 6 (limit: 2362) CGroup: /system.slice/netbox.service ├─11993 /usr/bin/python3 /usr/local/bin/gunicorn --pid /var/tmp/netbox.pid --pythonpath /opt/netbox/... ├─12015 /usr/bin/python3 /usr/local/bin/gunicorn --pid /var/tmp/netbox.pid --pythonpath /opt/netbox/... ├─12016 /usr/bin/python3 /usr/local/bin/gunicorn --pid /var/tmp/netbox.pid --pythonpath /opt/netbox/... ...
At this point, you should be able to connect to the HTTP service at the server name or IP address you provided. If you are unable to connect, check that the nginx service is running and properly configured. If you receive a 502 (bad gateway) error, this indicates that gunicorn is misconfigured or not running.
Please keep in mind that the configurations provided here are bare minimums required to get NetBox up and running. You may want to make adjustments to better suit your production environment.