Installation

Why is thereTCPOutAutoLB-0 and TailReader-0 error on fresh install?

stephanedeck
Explorer

Hi,

I just made a fresh install of Splunk server on a CentOS 7 machine.
RPM install, configuration to launch splunk as a splunk user with systemctl etc All good.

Right now in my health check I have TCPOutAutoLB-0 and TailReader-0 in error.
I don't have any message to go with it. Just an error status

Any way I can check those error with a CLI? Any idea of what is going on?

I havn't ever start to index any file yet.

I have this warning to : he TCP output processor has paused the data flow. Forwarding to output group default-autolb-group has been blocked for 10 seconds. This will probably stall the data flow towards indexing and other network outputs. Review the receiving system's health in the Splunk Monitoring Console. It is probably not accepting data.

I don't know where to start.

Thanks.

Regards,

Labels (2)
0 Karma
1 Solution

stephanedeck
Explorer

I have made a loop with a local output file, all good now.

View solution in original post

0 Karma

stephanedeck
Explorer

I have made a loop with a local output file, all good now.

0 Karma

baya151
Explorer

Hi stephanedeck,

could you please specify what do you mean by making a loop with a local output file?

Have you copied the contents of the default/outputs.conf file into local/outputs.conf file?

Answer is much appreciated

aklon
New Member

@baya151 ,  yes crate a copy of default/outputs.conf file into local/outputs.conf 

0 Karma
Get Updates on the Splunk Community!

Splunk Forwarders and Forced Time Based Load Balancing

Splunk customers use universal forwarders to collect and send data to Splunk. A universal forwarder can send ...

NEW! Log Views in Splunk Observability Dashboards Gives Context From a Single Page

Today, Splunk Observability releases log views, a new feature for users to add their logs data from Splunk Log ...

Last Chance to Submit Your Paper For BSides Splunk - Deadline is August 12th!

Hello everyone! Don't wait to submit - The deadline is August 12th! We have truly missed the community so ...