24.1.1 NTOPNG and REDIS no longer working

Started by lshantz, February 14, 2024, 08:51:13 PM

Previous topic - Next topic
I did it from CLI and not there. Did it as you mention, not there. I wonder if it is possible that somehow NTOPNG is somehow causing the issue. Hate to blow it out of the water to prove it. Guess I could rename the directory uninstall try again with just REDIS. It is a head scratcher for me. It does not matter what port I put it to, it always says the same thing, that was what lead me to believe it is a problem with the version of REDIS.

March 09, 2024, 02:11:15 AM #16 Last Edit: March 09, 2024, 02:21:55 AM by lshantz
So I got brave and updated to 24.1.3_1 and no issues, other than REDIS. It still does not come up. I was doing some searching and I have found something of interest. I Hope it is ok to paste a link for the whole story in case anyone wants to read it: https://stackoverflow.com/questions/7417232/redis-server-port-already-in-use?rq=4

The relevant  parts are: redis-cli ping, redis-cli shutdown, redis-server. Since I already knew there was no services running, I went straight to redis-server. What do you know, it came right up!!!
redis-server
45155:C 09 Mar 2024 00:23:39.950 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
45155:C 09 Mar 2024 00:23:39.950 * Redis version=7.2.4, bits=64, commit=00000000, modified=0, pid=45155, just started
45155:C 09 Mar 2024 00:23:39.950 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
45155:M 09 Mar 2024 00:23:39.956 * monotonic clock: POSIX clock_gettime
                _._
           _.-``__ ''-._
      _.-``    `.  `_.  ''-._           Redis 7.2.4 (00000000/0) 64 bit
  .-`` .-```.  ```\/    _.,_ ''-._
(    '      ,       .-`  | `,    )     Running in standalone mode
|`-._`-...-` __...-.``-._|'` _.-'|     Port: 6379
|    `-._   `._    /     _.-'    |     PID: 45155
  `-._    `-._  `-./  _.-'    _.-'
|`-._`-._    `-.__.-'    _.-'_.-'|
|    `-._`-._        _.-'_.-'    |           https://redis.io
  `-._    `-._`-.__.-'_.-'    _.-'
|`-._`-._    `-.__.-'    _.-'_.-'|
|    `-._`-._        _.-'_.-'    |
  `-._    `-._`-.__.-'_.-'    _.-'
      `-._    `-.__.-'    _.-'
          `-._        _.-'
              `-.__.-'

45155:M 09 Mar 2024 00:23:39.963 # WARNING: The TCP backlog setting of 511 cannot be enforced because kern.ipc.somaxconn is set to the lower value of 128.
45155:M 09 Mar 2024 00:23:39.964 * Server initialized

Opnsense still says it is not running, but I can fire up NTOPNG.

So, I would argue, there is something amiss with how the GUI is implementing it. REDIS DOES work, just not from their GUI. Something in the update borked it.

Edit: as a work around I did redis-server &, and it is running fine for now. Still show red in the Services dashboard, hopefully an admin will see this and help figure out what has gone sideways.

I'm just good enough to be dangerous to myself. I started poking around and there are 2 config files on the firewall.
/usr/local/opnsense/service/templates/OPNsense/Redis/redis.conf
/usr/local/etc/redis.conf


# Redis configuration file.
#
# Note that in order to read the configuration file, Redis must be
# started with the file path as first argument:
#
# ./redis-server /path/to/redis.conf

/usr/local/bin/redis-server

So my question is, which config file is in use, and is the gui properly doing the above? Obviously not, but how do I figure out the bread crumbs from here?

The first one is the template, picking the vlues from gui and creates the second one :)

Okay, I suspected as much. Didn't even look at the template one, but how does that help me solve the mystery?  :o

Same issue. 24.1.4 - Redis and NtopNG Showed as "working services" but no access...

Can we stop this thread please? Make your own with the required info attached.


Cheers,
Franco

March 28, 2024, 12:53:11 AM #22 Last Edit: March 28, 2024, 12:54:42 AM by lshantz
Obviously someone finally paid attention and corrected what ever got borked. It is now working after the latest update. You can lock/close this thread now. It would be nice to get an acknowledgement of what was wrong and what was done to fix it in the patch though.

From an engineering perspective no code changed in this area. I'm not sure what problem you were having.


Cheers,
Franco

 :o Really!! Dang... Well thanks for replying and keep up the good work.

At least I have documented a work around above for anyone else suffering from this weird issue. Oh, one thing.. it takes awhile to configure NTOPNG how I want it and it appears that this config data is stored in REDIS. I would very much like to capture/save this config data so when it does down again, I can quickly restore back to my setup. This is the 3rd or 4th this has happened over the last couple of years. Thanks in advance.