I am running Splunk Add-on for Tenable 5.1.1 on a heavy forwarder that is running Splunk 6.6.3 to pull vulnerability data from Tenable Security Center. I am having an issue where the add-on stops pulling. This usually happens around once a day. The odd the is I am not getting any errors or even warnings in the logs. It will be working perfectly and then just stops pulling. When it stops I can go in, disable the input, change the checkpoint value to the timestamp of the last event pulled in, then re-enable the input and it will start pulling in again without issue.
I can see in the logs that it is actually still attempting to do something even though it isn't pulling anything. The following is getting logged every 2 minutes (which is the schedule it runs on):
2017-09-11 20:06:57,601 +0000 loglevel=INFO, pid=13810, tid=Thread-2, file=scheduler.py, funcname=getreadyjobs, codelineno=100 | Get 1 ready jobs, next duration is 119.999509, and there are 1 jobs scheduling
2017-09-11 20:06:57,601 +0000 loglevel=INFO, pid=13810, tid=Thread-6, file=threadpool.py, funcname=run, codelineno=261 | Thread workqueuesize=0
Any ideas would be greatly appreciated.
Note: I have been dealing with this for quite a while. Even when the HF was on Splunk 6.5.x.
The latest version of the Splunk Add-on for Tenable is 5.1.2. It was released in October 2017.
The Fixed Issues section for 5.1.2 says:
Version 5.1.2 of the Splunk Add-on for Tenable fixes the following issues. 2017-08-22 ADDON-13413 Tenable input stops pulling vulnerability data
Have you tested 5.1.2?
The same issue just started with our tenable add-on.
we were receiving data and now it stopped
I restarted the Splunk service on the DCN but still doesn't work
Anyone have any additional recommendations?