Refine your search:

Got these error messages with all users under one particular role "Search operation 'rangemap' is unknown. You might not have permission to run this operation" or "Search operation 'gauge' is unknown. You might not have permission to run this operation."


change_own_password = enabled

get_metadata = enabled

get_typeahead = enabled

list_inputs = enabled

request_remote_tok = enabled

rest_apps_view = enabled

rest_properties_get = enabled

rest_properties_set = enabled

search = enabled

schedule_search = enabled

srchIndexesAllowed = *

srchDiskQuota = 500

srchJobsQuota = 50

asked 31 Aug '11, 17:03

Splunker_J's gravatar image

Splunker_J ♦
accept rate: 62%

could you post the search?

(01 Sep '11, 07:44) rroberts

One Answer:

It appears this is not limited to just rangemap and gauge. It seems to be a problem with all .py scripts on my system. My symptom was that "admin" could run all the .py scripts located in $SPLUNK_HOME/etc/apps/search/bin, including rangemap and gauge. But regular users in any role I created could not run the scripts, even though they were set up with "read" permission and the scripts were "global".

A work-around that I used was:

Step 1. Copy ( likewise with and any other *.py script you need ) from the $SPLUNK_HOME/etc/apps/search/bin directory to the $SPLUNK_HOME/etc/system/bin directory.

Step 2. Add the following stanza to $SPLUNK_HOME/etc/system/local/commands.conf:


filename =

supports_getinfo = true

supports_rawargs = true

Step 3. Add the following stanza to $SPLUNK_HOME/etc/system/local/authorize.conf:


Step 4. Add the following to your custom role stanza. This is the stanza you created when you setup a new role in Splink Manager > Access Controls > Roles :


run_script_rangemap = enabled

Step 5. restart splunk.

This worked for me although I would not consider it a permanent fix because I would have to copy the *.py scripts again if Splunk updates them.


answered 22 Dec '11, 11:07

xtrjx's gravatar image

accept rate: 66%

Post your answer
toggle preview

Follow this question

Log In to enable email subscriptions



Answers + Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "Title")
  • image?![alt text](/path/img.jpg "Title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: 31 Aug '11, 17:03

Seen: 1,181 times

Last updated: 22 Dec '11, 11:07

Related questions

Copyright © 2005-2014 Splunk Inc. All rights reserved.