From f2d5f27c3323e2d298a5f59b8f7dcf3da8c956a9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Christian=20M=C3=A4der?= Date: Thu, 12 May 2022 09:15:53 +0200 Subject: [PATCH] Updated Troubleshooting (markdown) --- Troubleshooting.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/Troubleshooting.md b/Troubleshooting.md index 0f400a3..679b642 100644 --- a/Troubleshooting.md +++ b/Troubleshooting.md @@ -109,6 +109,23 @@ docker-compose run --rm netbox /opt/netbox/venv/bin/python /opt/netbox/netbox/ma ## Frequently Asked Questions (FAQ) and Common Problems +### Getting to "process X exited with code 0" + +You find yourself with a NetBox Docker instance that tells you something like: + +``` +[notice] 7#7 process 14 exited with code 0 +``` + +Congratulations! +Your NetBox Docker instance most definitely started successfully. +Your problem is probably somewhere else, if there's even a problem. + +While starting, Django (the Python framework that powers NetBox) creates several child processes. +After a successful start, some of these child processes do exit. +As long as it states that the exit code is `0`, all is well: +The exit code `0` in Unix/Linux-land (usually) indicates a success. + ### Getting a "Bad Request (400)" > When connecting to the Netbox instance, I get a "Bad Request (400)" error.