ok, this is quite an old setup, splunk 3.4.14 on rhel4, but I get the following error, any pointers would be greatly appreciated.
2013-09-17 21:39:46,581 ERROR Dispatcher:403 - Unexpected SplunkWeb error: 'No such method name' traceback (most recent call last): File "/opt/splunk/lib/python2.5/site-packages/splunk/appserver/oxiclean/Dispatcher.py", line 358, in delegateRequest responseXml = actionInstance() File "/opt/splunk/lib/python2.5/site-packages/splunk/appserver/oxiclean/V3RestHandlers.py", line 792, in process_get diskStats = cli_common.getDiskUsage(self.authToken) File "/opt/splunk/lib/python2.5/site-packages/splunk/clilib/cli_common.py", line 906, in getDiskUsage usageXML = simpleAPICall(callname, params, authstr) File "/opt/splunk/lib/python2.5/site-packages/splunk/clilib/cli_common.py", line 603, in simpleAPICall % (callName, params, authStr), shouldParseXML) File "/opt/splunk/lib/python2.5/site-packages/splunk/clilib/cli_common.py", line 576, in callAPI raise InvokeAPI, str(elem.text) InvokeAPI: 'No such method name'
This is reviving a very old thread, but the error showed up at a site last week, and they mentioned this thread, so I thought I would update.
The issue was that Splunk was manually started as root at some point, and later restarted as the regular Splunk user. Starting as root changed ownership of some files to root user, causing the error. Running a chown -R on the Splunk install directory to change the ownership back to the Splunk user solved the issue.
Pointer #1: Upgrade Splunk 😉