Data Source Sync Status stuck in 'queued' - Netbox Docker #1578
Replies: 1 comment
-
|
Looks like netbox-rq was a red herring and it's a known bug that someone's proposed a fix for |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm working on getting Netbox Docker implemented and am running in to an issue where after disabling sync on my data sources they are stuck in the 'queued' state. To un-stick the 'queued' status I tried manually changing the status in nbshell as per this thread but it was not effective.
It appears that the netbox-rq service is having problems:
Running
sudo journalctl -eu netbox-rqgives me not a whole ton of detail:Tried updating manually restarting the service, updating Netbox, but no luck. Next step will be testing with rebuilding from scratch. I don't think it's the cause but I am differing from the standard Netbox Docker setup since I've merged those steps in to larger docker-compose.yml since I'm running other services off that host. Having no other issues than this one. Any ideas where to look?
Versions:
Netbox: NetBox Community v4.3.7-Docker-3.3.0
Host: Ubuntu 24.04.3 LTS
Docker: Docker version 29.1.2, build 890dcca
Beta Was this translation helpful? Give feedback.
All reactions