|
Hi! Since upgrading to v.4.2 we have been having problems with going over our daily indexing volume limits. I have tried following the guidance here to try and identify the cause, but am having problems even seeing the Indexing Volume dashboard. When I browse to Status > Index activity > Indexing volume I get the following error,
Our trial license has expired and we're currently using the free license. We are planning a purchase, but without being able to resolve this problem we are unable to make a decision on the appropriate license needed. Any suggestions welcome! Thanks, Jonathan |
|
This is a bug. Splunk is tracking this as SPL-38603, and it is scheduled to be fixed in 4.2.2. For the interim, you can use the information here to troubleshoot voume issues: http://www.splunk.com/wiki/Community:TroubleshootingIndexedDataVolume |
|
This seems like it could be a bug. Anything in the splunk logs? Thanks. Which logs I should look in? splunkd.log has the following errors, ApplicationUpdater - Error checking for update via https://splunkbase.splunk.com/api/apps:resolve/checkforupgrade: Connect timed out. ExecProcessor - message from ""C:Program FilesSplunkbinsplunk-regmon.exe" --driver-path "C:Program FilesSplunkbin"" splunk-regmon - No enabled entries were found in the conf files. ExecProcessor - message from ""C:Program FilesSplunkbinsplunk-regmon.exe" --driver-path "C:Program FilesSplunkbin"" Using logging configuration at C:Program FilesSplunketclog-cmdline.cfg.
(08 Apr '11, 15:04)
jonathanward
Did not realize you were running this on Windows. Sorry as that is not my area of expertise. Hopefully someone else will chime in shortly. In the meantime I would review all the log files in the Splunk log directory $SPLUNK_HOME/var/log/splunk/
(08 Apr '11, 16:54)
netwrkr
I've now installed a Linux instance and have reproduced the problem, so I'm pretty sure it's a bug. Under the trial license the Indexing volume report runs fine, however when switching to the free license and attempting to run the report it fails with the internal server error message. This happens on both Windows and Linux installations.
(24 May '11, 05:42)
jonathanward
|
