All Apps and Add-ons

External search command 'getlocalhost' returned error code 1

gcgrtorres
Engager

Unable to run Splunk S.O.S on indexer, there is no Server to query in the drop down list. I get the following error when I select the app home page

[subsearch]: External search command 'getlocalhost' returned error code 1.  External search command 'getallhosts' returned error code 1.

hexx
Splunk Employee
Splunk Employee

This indicates that the getlocalhost.py python search command did not execute properly. We should be able to find out what happened by :

  • Looking in $SPLUNK_HOME/var/log/splunk/python.log
  • Running the command manually with $SPLUNK_HOME/bin/splunk cmd python getinternalhost.py
  • If the former command doesn't show anything of interest, set export PYTHONVERBOSE=1 then run it again and let us know what output you get.
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!

Data Outage Monitoring and Reporting

We’ve all been there, right? Living our best life, working on our Splunk environment, when out of nowhere a ...

Manage Datasets and Connections in Catalog on Splunk Cloud Platform

Set Up Data Where You Use It Catalog already helps teams find and understand data across Splunk indexes, ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...