Deployment Architecture

No logs from 2 SHC search heads

davebo1896
Communicator

Two of our three search heads have stopped forwarding logs.
It doesn't matter if they are captain or not.

I have verified server.conf and outputs.conf look good using splunk btool server all and splunk btool outputs all

I have tried cleaning all search heads (remove from cluster, remove non-standard apps and user, run splunk clean all, and put back in the cluster)

The logs are being written, but are not being forwarded to the indexers.

Any ideas what to check next?

0 Karma
1 Solution

davebo1896
Communicator

I got it figured out.

in /opt/splunk/etc/system/local/inputs.conf

  [default]
  host =<server>

host was set to the same hostname on all three search heads.
No idea how that happened, but setting host to the respective hostname and cluster restart fixed the problem

View solution in original post

0 Karma

davebo1896
Communicator

I got it figured out.

in /opt/splunk/etc/system/local/inputs.conf

  [default]
  host =<server>

host was set to the same hostname on all three search heads.
No idea how that happened, but setting host to the respective hostname and cluster restart fixed the problem

0 Karma

sk314
Builder

Does the outputs.conf have this line

[indexAndForward]
index = false

Ref: http://docs.splunk.com/Documentation/Splunk/latest/DistSearch/Forwardsearchheaddata

0 Karma

davebo1896
Communicator

Yes. They are using index=false

0 Karma
Get Updates on the Splunk Community!

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...

Updated Team Landing Page in Splunk Observability

We’re making some changes to the team landing page in Splunk Observability, based on your feedback. The ...

New! Splunk Observability Search Enhancements for Splunk APM Services/Traces and ...

Regardless of where you are in Splunk Observability, you can search for relevant APM targets including service ...