Getting Data In

Is there a need for for the status command when stopping a forwarder?

ddrillic
Ultra Champion

When stopping a forwarder I see the following -

bash-3.2$ ./splunk stop
splunkd is not running.
bash-3.2$ ./splunk status
splunkd 7085 was not running.
Stopping splunk helpers...

Done.
Stopped helpers.
Removing stale pid file... done.

bash-3.2$ ./splunk status
splunkd is not running.

So, do I really need to run the ./splunk statuswhen stopping a forwarder?

Tags (2)
0 Karma

mayurr98
Super Champion

If your job is just to stop the forwarder then you really do not need to write ./splunk status. Instead just type ./splunk stop

In other words, you do not really need to run the ./splunk status when stopping a forwarder

ddrillic
Ultra Champion

But you see, by running ./splunk status two things took place -

 Stopped helpers.
 Removing stale pid file... done.

One would think that these two actions actually belong to the invocation of ./splunk stop. Why are they done via ./splunk status?

0 Karma
Get Updates on the Splunk Community!

[Puzzles] Solve, Learn, Repeat: Dynamic formatting from XML events

This challenge was first posted on Slack #puzzles channelFor a previous puzzle, I needed a set of fixed-length ...

Enter the Agentic Era with Splunk AI Assistant for SPL 1.4

  🚀 Your data just got a serious AI upgrade — are you ready? Say hello to the Agentic Era with the ...

Stronger Security with Federated Search for S3, GCP SQL & Australian Threat ...

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...