On 2025.2.5 on rocky, (not sure which version). 2023. I constantly getting the above and have to restart both wiretap services to fix it.
Anyone else see this? have a fix for it?
Nobody?
We did have this problem especially on machines running long without restart. Restarting services is the only solution when it happens but overall can be caused by a few things. Gonna be in front of a machine in a few hours I will check cfg paths because I don’t remember them of the top of my head ![]()
It’s really doing my head in, I’m having to restart services sometime 3x in succession to get it to work.
The box I’m on also has 2023 on it, however, all running services appear to be 2025.
to find out which version of rocky linux:
open a terminal
uname -r
you’ll get a response like this:
[root@echo ~]# uname -r
5.14.0-611.16.1.el9_7.x86_64
where 9_7 is the version of rocky linux
you probably need to tidy up the version mismatches in your services which probably means ‘letting go’ of 2023, and upgrading your projects to a newer version.
Thanks Phil, I’ll check tomorrow but as I’m freelance, I’m not sure they can dump 2023
Rocky 8.5
