Installed SOS yesterday. Installed Sideview Utils after I installed SoS.
In SoS everthing appears to be working except for the two dropdowns under "Resource Usage" and "Crash Log Viewer" under "Warnings and Errors". The latter I would expect some results because I had a crash two weeks ago.
Is there something I've missed in the install of SoS? I did it all from the web interface.
Advice appreciated.
Thanks!
Regarding the lack of information in the "Splunk CPU/Memory Usage" view, it seems likely that you haven't enabled the ps_sos.sh
scripted input. Read more about how to configure SoS to monitor the resource usage of your Splunk instance in this Splunk Answer.
Regarding the crash log, it's harder to say. Can you check if there is a crash log file in $SPLUNK_HOME/var/log/splunk
? If yes, the next step would be to check if it's been indexed to the _internal
index by searching for it in the following fashion:
index=_internal source=*crash*.log
Does that return any events?
Regarding the lack of information in the "Splunk CPU/Memory Usage" view, it seems likely that you haven't enabled the ps_sos.sh
scripted input. Read more about how to configure SoS to monitor the resource usage of your Splunk instance in this Splunk Answer.
Regarding the crash log, it's harder to say. Can you check if there is a crash log file in $SPLUNK_HOME/var/log/splunk
? If yes, the next step would be to check if it's been indexed to the _internal
index by searching for it in the following fashion:
index=_internal source=*crash*.log
Does that return any events?
Since you mentioned that you experienced a crash log two weeks ago, I would have expected a crash log there. But if there isn't one, that certainly explains why SOS' crash log viewer isn't showing anything.
Beauty! That did it. I enabled ps_sos.sh and it's all good. Thank YOU.
I do not have a crash.log in that directory. Should I?
I found this thread useful for troubleshooting:
http://splunk-base.splunk.com//answers/38452/the-lookup-table-splunk_instances_info-is-invalid-sos
I appreciate the link. I had not seen that. I am running 4.3.2. Which is not listed in that link as having a bug. Time allowing however, I may try the fixes they suggest.
Thanks!