I've been tinkering with a custom search command that uses win32com.client. When I try to invoke my search command I get the following error
I've tried to call the offending section using the bundled interpreter, and it works just fine.
Any ideas I'm kinda stumped. I really don't want to have my search command, exec an external interpreter.
== Update == I've implemented another version that execs a vbs script to invoke the win32 com component. It also fails which leads me to believe that splunkd is doing something funny.
Running splunk under a normal user account solves the problem. On Windows splunk cmd python doesn't run in the same context as the service.
answered 10 Oct '11, 03:28
I would follow sys.stderr Not logging to splunkd on Splunk Answers
I have been having issues with trying to find errors with custom commands and the link above has an answer which explains how to add logging information to your script so you can try to track where it is producing errors or how far it is going.
answered 27 Sep '11, 13:11