24.1.1 NTOPNG and REDIS no longer working

[lshantz]

After the update REDIS no longer works. I watched on an attached monitor upgrading another box and saw where it said something about directory invalid or not found. So am I the only one? it happened on 2 different boxes.

[mimugmail]

Did you try to reset the db?

[lshantz]

I've not had time to do much. Fighting getting two upgraded systems happy. I did a reinstall, but didn't bother to look at the log yet to see if there were the same error messages. I would assume anybody that did the upgrade had the same issue. Apparently a bad assumption.   

I will have to re-read the docs to see if that is all it needs and how to do it.

[lshantz]

So looking in /var/db/redis, it is empty!

I looked at the logs and got:
/var/log/system/system_20240220.log | grep redis
<13>1 2024-02-20T10:43:47-07:00 xxxxxxxxxxxxxx.com kernel - - [meta sequenceId="314"] <118>Starting redis.
<12>1 2024-02-20T10:43:47-07:00 xxxxxxxxx.com redis 97787 - [meta sequenceId="315"] WARNING: The TCP backlog setting of 511 cannot be enforced because kern.ipc.somaxconn is set to the lower value of 128.
<12>1 2024-02-20T10:43:47-07:00 xxxxxxx.com redis 97787 - [meta sequenceId="316"] Warning: Could not create server TCP listening socket xxxxxxx.8:6379: bind: Address already in use
<12>1 2024-02-20T10:43:47-07:00 xxxxxx.com redis 97787 - [meta sequenceId="317"] Failed listening on port 6379 (tcp), aborting.
<11>1 2024-02-20T10:44:29-07:00 xxx.com ntopng 20907 - [meta sequenceId="369"] 20/Feb/2024 10:44:29 [Redis.cpp:153] ERROR: ntopng requires redis server to be up and running

Some of this may be erroneous, since we did change from .1 to .8 trying to get CARP running. It failed prior to this. Hopefully this will make sense to someone. I can't find the ipc.somaxconn setting anywhere.

Any help appreciated.

[lshantz]

HA, I tried to reinstall again and I see there is a 24.1.2, so maybe that will fix it. Fingers crossed.

[mimugmail]

This is the error:
Could not create server TCP listening socket xxxxxxx.8:6379: bind: Address already in use
<12>1 2024-02-20T10:43:47-07:00 xxxxxx.com redis 97787 - [meta sequenceId="317"] Failed listening on port 6379 (tcp), aborting.

The 511 is just a warning.
Go to CLI, sockstat -4 and search for the port and process

[lshantz]

->Go to CLI, sockstat -4 and search for the port and process

Thanks for replying. Good to know that is a simple warning, but I did stop the warning in turneables section.

Okay, but it doesn't matter what port you set it to, you still get the same error. I did do as you suggested and it is not listed.

[mimugmail]

And you hit the "reset db" in redis, correct? Can you post a screenshot or redis config page?

[lshantz]

I did the reset, but no change.
I attached a copy of the setup page.

Here is the log. It is still unhappy with the port, so that HAS to be somehow related, but like I said I changed ports and it was still not happy. ??

024-02-27T06:16:37-07:00   Warning   redis   Failed listening on port 6379 (tcp), aborting.   
2024-02-27T06:16:37-07:00   Warning   redis   Warning: Could not create server TCP listening socket 192.168.100.1:6379: bind: Address already in use   
2024-02-27T06:16:37-07:00   Notice   redis   Running mode=standalone, port=6379.   
2024-02-27T06:16:37-07:00   Notice   redis   monotonic clock: POSIX clock_gettime   
2024-02-27T06:16:37-07:00   Notice   redis-server   Configuration loaded   
2024-02-27T06:16:37-07:00   Notice   redis-server   Redis version=7.2.4, bits=64, commit=00000000, modified=0, pid=31815, just started   
2024-02-27T06:16:37-07:00   Notice   redis-server   oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo

[mimugmail]

Can you download config.xml, remove the whole redis Container, restore, reboot, remove os-redis, install again and start without ANY modification beside enable checkbox

[lshantz]

Sure, I'm willing to do that, but have two work from homes right now, so will try that tonight.

[lshantz]

Well I did as you suggest and deleted everything REDIS. Alas I got: Installation out of date. The update to opnsense-24.1.2_1 is required.

I've been holding off because my last two updates were a nightmare. Now I have to decide if I want to update and risk being down again, or take a chance. 

[mimugmail]

If you type "pkg install os-redis" via CLI, you dont need to be on the latest version

[lshantz]

DOH! I did not realize that. I guess I'm getting rusty at CLI and becoming a child of the GUI.

Okay, so I did completely delete everything related to REDIS. Then installed via CLI. I got the exact same error message! This is so weird. I did a netstat -l and there is no 6379. I even changed it to 6378 and it gives the same error.  I wonder if the Opnsense update has changed some environment and it is getting confused, although apparently few are having this issue.

[mimugmail]

I did a fresh install on a clean system, latest updates, just installed redis, NO changes (also no listen oder password), on enabled and it works.

Interface : Diagnostics : Netstat : Sockets -> search for 6379 lists the open port with command redis-serv