Netbox-rq fails to start after trying to add a napalm-driver

[noma...@gmail.com]

Hi

I have this clone of a working prod netbox server running 2.11.4.

I wanted to enable napalm, which went fine.

Then I wanted to enable the driver for napalm-ruckus-fastiron, to see if that would work with our ICX switches.

I added

napalm-ruckus-fastiron

to local_requirements.txt and ran ./upgrade.sh

No visible errors occured but after this, the netbox-rq service will not start anymore.

I tried to reverse the change, by removing the line from local-requirements.txt and running upgrade.sh again, but it did not help.

Any advise?

[Jeremy Stretch]

Just adding a package to local_requirements.txt shouldn't cause any issues on its own. Take another look at your configuration. If you disable NAPALM, does the RQ service start successfully? You can also try executing it directly via "manage.py rqworker" which may yield some clues (be sure to do this from within the Python virtual environment).

Hope that helps!

Jeremy Stretch Distinguished Engineer, NS1 Office of the CTO   website: ns1.com email: jstretch@ns1.com

 

--
You received this message because you are subscribed to the Google Groups "NetBox" group.
To unsubscribe from this group and stop receiving emails from it, send an email to netbox-discus...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/netbox-discuss/7d8d6f46-ca6f-4ecc-a645-f54fcaa7b1ebn%40googlegroups.com.

[Brian Candler]

On Wednesday, 8 December 2021 at 10:35:10 UTC noma...@gmail.com wrote:

No visible errors occured but after this, the netbox-rq service will not start anymore.

Look at its output to see why it's failing to start:

journalctl -eu netbox-rq

systemctl status netbox-rq