Error -2 connecting to redis:6379. Name does not resolve.

[Hasan T. Emdad]

Getting the following error on my netbox docker-

<class 'redis.exceptions.ConnectionError'>
Error -2 connecting to redis:6379. Name does not resolve.

[Jacob Mansfield]

Are the connection details for your redis server set correctly in the Netbox configuration?

--
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/38dbf011-75b7-4e2b-9d4f-0a882f4f398cn%40googlegroups.com.

[Hasan T. Emdad]

It was a live and production system until a reboot was needed. Ever since reboot, getting this error. There was no change in the environment (hosting) or the application end.

Is there a settings or configuration file where I should make some change now?

 

[Markku Leiniö]

Hi, you didn't mention your NetBox version, but see REDIS in https://netbox.readthedocs.io/en/stable/configuration/required-settings/.

Also see /opt/netbox/netbox/netbox/configuration.example.py

Your configuration is in /opt/netbox/netbox/netbox/configuration.py. It is loaded only when netbox is restarted, so maybe someone had edited it without restarting earlier.

Markku

[Hasan T. Emdad]

Hi, 

Thanks for Helping out. However, the problem still remains. Checked the configuration file. Nothing unusual. Have mentioned that the system used for a production setup had invested hundreds of man hour :(

Version of Netbox is 2.8.6

Shared the Configuration file screenshot as attached. No CHANGES were made ever since installed some 4 months back and populated with data from netbox UI.

The machine hostname is 'netbox' and resolves to 127.0.0.1

TIA.

--
You received this message because you are subscribed to a topic in the Google Groups "NetBox" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/netbox-discuss/6sKx-aSv5jk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to netbox-discus...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/netbox-discuss/cf3af0b9-5cdc-4acb-a2d4-619c7b525627o%40googlegroups.com.

[markku...@gmail.com]

Hi, did you check your REDIS configuration that it does not contain hostname "redis"? I mean, you don't show it fully in the screenshot.

Markku

[Markku Leiniö]

Also, here is the documentation for REDIS configuration in 2.8.6: https://github.com/netbox-community/netbox/blob/v2.8.6/docs/configuration/required-settings.md

If you don't have a separate server running redis, then your hostname in REDIS configuration section should be "localhost" for both "tasks" and "caching".

Markku

[Hasan T. Emdad]

Still no luck. Sharing more screenshot values.

Nothing unusual it seems. Redis CLI or Redis log seems to be OK. 

Didn't find netbox error log path on docker edition. (/var/log/netbox.log is missing).

Hasan T. Emdad Rumi

Cell: +880.17.11673093 | Skype: h.t.emdad

To view this discussion on the web visit https://groups.google.com/d/msgid/netbox-discuss/5eec1ce3-7135-4f05-a459-3772400dfcabo%40googlegroups.com.

[markku...@gmail.com]

Sorry, I haven't run NetBox in Docker.

But I see in https://github.com/netbox-community/netbox-docker/blob/release/env/netbox.env that there is "REDIS_HOST=redis" that could explain your problem. Maybe someone more expert in running NetBox in Docker can help you further.

Markku