mirror of
https://github.com/netbox-community/netbox-docker.git
synced 2025-06-20 09:58:24 +02:00
Updated Troubleshooting (markdown)
parent
c2beefadb4
commit
f2d5f27c33
@ -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
|
## 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)"
|
### Getting a "Bad Request (400)"
|
||||||
|
|
||||||
> When connecting to the Netbox instance, I get a "Bad Request (400)" error.
|
> When connecting to the Netbox instance, I get a "Bad Request (400)" error.
|
||||||
|
Loading…
x
Reference in New Issue
Block a user