Splunk Search

Problem trying to use remote CLI

bcotton
Engager

When trying to run a search from a remote CLI instance, I keep getting a 404.

The command-line I'm running is:

./splunk search bob -uri http://dsc-splunksearch-01:8000 -auth <....>

and the web_access.log says this:

10.32.12.137 - - [04/Apr/2011:12:27:24] "POST /services/search/jobs/export HTTP/1.1" 303 176 "" "SplunkCli/4.1 (build 89596)" - 4d9a0d8cfa1d6c08d0 10.32.12.137 - - [04/Apr/2011:12:27:24] "GET /en-US/services/search/jobs/export HTTP/1.1" 404 2544 "" "SplunkCli/4.1 (build 89596)" - 4d9a0d8cfb1d6c08d0

Tags (1)
1 Solution

Stephen_Sorkin
Splunk Employee
Splunk Employee

You need to use the uri of the splunkd, not the splunkweb.

Instead you should run:

./splunk search bob -uri https://dsc-splunksearch-01:8089 -auth <....>

And to verify, look at splunkd_access.log.

View solution in original post

Stephen_Sorkin
Splunk Employee
Splunk Employee

You need to use the uri of the splunkd, not the splunkweb.

Instead you should run:

./splunk search bob -uri https://dsc-splunksearch-01:8089 -auth <....>

And to verify, look at splunkd_access.log.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Meet the .conf26 AI Agent Buildathon Winners

At the .conf26 AI Agent Buildathon, Splunk users turned their operational expertise into working AI agents ...

Trusted Autonomy in the SOC: A Maturity Journey

AI is compressing attacker timelines and pushing SOC teams beyond human capacity thresholds. The next SOC ...

Supercharging Windows Security Detection Performance: Introducing Hybrid Field ...

Windows event logs—from Security auditing and Sysmon to PowerShell script blocks—form the operational backbone ...