Software error in bookkepper.c line 401: Entry not found in list
Signal launcher[29578] to terminate.
I do not believe this to be the semaphore error, as I have increased those already. Do you have any ideas or past experiences on what could cause this error? I am not sure where to look for the correct file that contains the entry on line 401.
cd /tmp
wget https://github.com/phaag/nfdump/archive/master.zip
unzip master.zip
cd /tmp/nfdump-master
./configure --prefix=/usr/local --enable-sflow --enable-nsel --enable-nfprofile --enable-nftrack
make
make install
ldconfig -v
service nagiosna restart
Try that and let us know if this fixes the issue.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Guys, sorry for putting this to the side but now I am back with a need to find a resolution on this. So, to summarize, when we reboot the Nagios NA server, it does not autostart the sources and requires us to go in the web GUI and start them one at a time, which takes hours with the amount of sources we have. I am unable to copy and paste from the screen because our systems are classified and on a different enclave. What I do see, however is the following activity when I restart the nagiosna.service and attempt to autostart all of the sources:
Another collector with PID 23898 is already running, and configured for '/usr/local/nagiosna/var/[hostname]/flows'
initialize bookkeeper failed.
Software error in bookkeeper.c line 394: Entry not found in list
Signal Launcher [1999] to terminate.
Then the launcher terminates, and consequently nfcapd.
And so I just manually started the source that that PID error was on via the "start" option on the GUI, and it started up fine. However, I restarted nagiosna.service and it failed again on the same source with the same error, except it was a different PID number. So, perhaps there's something wrong with the source? Could it be something to do with the fprobe settings?
Guys, I apologize but I must have missed a step the first time I tried following tgrieps instructions but after I followed it step-by-step this morning, it appears that it is now working, slowly but surely. How embarrassing, but also very awesome that it is working now.
Thanks so much for your patience and assistance with this! This issue appears to be resolved...
Sarg0n wrote:Guys, I apologize but I must have missed a step the first time I tried following tgrieps instructions but after I followed it step-by-step this morning, it appears that it is now working, slowly but surely. How embarrassing, but also very awesome that it is working now.
Thanks so much for your patience and assistance with this! This issue appears to be resolved...