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

Deep insights, no barriers: Splunk Observability Cloud Free Edition

As software delivery cycles continue to accelerate, observability shouldn’t be a luxury — it should be a ...

Monitoring AI Agents with Splunk Observability Cloud

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...

[Puzzles] Solve, Learn, Repeat: Tiling

This puzzle (first published here) is based on finding groups of tessellated tiles (inspired by floor tiles I ...