Splunk Enterprise

Active: failed (Result: protocol)

Mahi4rus
Explorer

splunk@:~/bin $ systemctl status splunk
● splunkd.service - Splunk Universal Forwarder
Loaded: loaded (/etc/systemd/system/splunkd.service; enabled; vendor preset: disabled)
Active: failed (Result: protocol) since Tue 2021-04-20 11:49:25 UTC; 2h 41min ago
Process: 1869 ExecStart=/opt/splunkforwarder/bin/splunk start --accept-license --answer-yes --no-prompt (code=exited, status=0/SUCCESS)
Main PID: 2050 (code=exited, status=0/SUCCESS)

When i run the comand (systemctl status splunk) it will come like this i have kill the process and  and  restarted the splunk farwarder and its running now and i have removed the  all old PIDs.

can you please tell me how to resolve this issue. 

0 Karma
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!

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

Introducing the 2026 - 2027 SplunkTrust cohort!

The goal of the SplunkTrust™ membership has historically been to acknowledge and recognize those who go above ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...