It means that you have a search peer (configured in Manager -> Distributed Search) which has the same servername as the search head you're on. Pretty self explanatory 🙂
The usual culprit for these is when you are running two splunk instances on the same box for dev or testing, in this case Splunk will use the server host as its servername by default, you can override this in server.conf in $SPLUNK_HOME/etc/system/local/ by setting a value called servername as per the docs;
[general]
serverName = <ascii string>
* The name used to identify this Splunk instance for features such as distributed search.
* Defaults to <hostname>-<user running splunk>.
* May not be an empty string
* May contain environment variables
* After any environment variables have been expanded, the server name (if not an IPv6
address) can only contain letters, numbers, underscores, dots, and dashes; and
it must start with a letter, number, or an underscore.
E.g. in server.conf in SPLUNK_HOME/etc/system/local/
[general]
serverName = bobServ
Of course this is just the usual suspect, it could be another instance on another box which happens to have the same servername, perhaps server.conf has been shared and both servers have the same name or something else altogether 🙂
... View more