Activity Feed
- Karma Re: Putting a list of hosts under maintenance for richgalloway. 04-12-2024 07:19 AM
- Karma Re: Splunk started complaining "Script execution failed for external search command 'runshellscript'." after 9 for kaurinko. 10-22-2022 06:03 AM
- Got Karma for Re: Splunk started complaining "Script execution failed for external search command 'runshellscript'." after 9. 10-21-2022 11:00 PM
- Posted Re: Splunk started complaining "Script execution failed for external search command 'runshellscript'." after 9 on Alerting. 10-21-2022 12:40 PM
- Karma Re: Splunk started complaining "Script execution failed for external search command 'runshellscript'." after 9 for kaurinko. 10-12-2022 10:39 AM
- Posted Re: Splunk started complaining "Script execution failed for external search command 'runshellscript'." after 9 on Alerting. 10-11-2022 12:33 PM
- Posted Re: Splunk DB Connect V3 - Automated / Programmatic creation of connections and inputs on All Apps and Add-ons. 08-09-2021 08:33 AM
- Posted Re: Splunk DB Connect V3 - Automated / Programmatic creation of connections and inputs on All Apps and Add-ons. 08-05-2021 01:49 PM
- Posted Re: Splunk DB Connect: Is it possible to use Python to make password changes in identities.conf? on All Apps and Add-ons. 08-05-2021 11:51 AM
Topics I've Started
No posts to display.
I received a reply from Splunk Support. They said so far it appears to be a benign message -- the 'runshellscript' actually does complete. The message only occurs on HFs and can be eliminated by setting precalculate_required_fields_for_alerts = 0 in your /local/savedsearches.conf file -- add to the stanza for the saved search associated with your 'run a script' trigger action. They DID mention this is safe if no other alert actions are attached to that search. Basically, the required fields logic is in place for all alert actions but is no use in this one, so the logic is not needed. However, if other alert actions are attached to the search, you could encounter a performance impact. I just decided to create a custom alert action, so I haven't tested this workaround and I cannot confirm that it works but perhaps this could help to fix your issues.
... View more
10-11-2022
12:33 PM
Hi, Have you found any solution to this issue? I'm also getting this following message: SearchMessage orig_component= sid=AlertActionsRequredFields_1665516540.1276 message_key=EXTERN:RUNSHELLSCRIPT_INVALID_SID__%s message=Invalid search ID ''. Thanks!
... View more
08-09-2021
08:33 AM
Hi @mchristopherson! I've found this line very useful: curl -k -u admin:changeme -H "Content-Type: application/json" -X PUT -d '{"name":"test","username":"yourusername", "password":"newPassword"}' https://dbx.splunk.dev:8089/servicesNS/nobody/splunk_app_db_connect/db_connect/dbxproxy/identities/test Which actually works and changes the password of an identity without any other steps required. I hope it helps you. Regards!
... View more
08-05-2021
01:49 PM
Hi! How did you managed to make it work? I'm struggling with this right now, trying to update the identities passwords but I'm getting "Splunkd error: HTTP 409 -- An object with name=test_identity already exists". I'm lost here 😞 Thank you and regards!
... View more
08-05-2021
11:51 AM
Hi! Is there any updated information regarding this? I'm using the Splunk DB Connect Version 3.5.1 and I wanted to know if it is possible to change an identity password via REST API or using other method. I've tested the answer in the solution but it doesn't encrypt the password in the identities.conf file. Thank you and regards!
... View more