Yesterday we were given a task of changing the SSL levels for the web interface in SPLUNK. After doing so, we restarted SPLUNK. After attempting to log back in, we were greeted with the following crash report.
2012-02-15 18:05:14.916 +0000 splunkd started (build 115073) terminate called after throwing an instance of 'PropertyPagesException' what(): Cannot get user to act as: No user info provider registered (user: XXXXXXX, app: user-prefs, root:/opt/splunk/etc)
After researching this for awhile, we found out that this is a bug in the current version of SPLUNK which they will be fixing in the next release. In the mean time, here is the work around.
rm –rf $SPLUNK_HOME/var/run/splunk/dispatch/*
Then restart SPLUNK.
The dispatch directory is where SPLUNK caches information for current or previous searches. The data changes or is regenerated as needed, similar to /tmp or the swap/page file. Deleting this data will not affect the application
Guarding your IT Experience!
Add new comment