Store active inputs before triggering server restart


When I do a ‘systemctl restart graylog-server.service’ all inputs I have starts up, even then ones I have disabled. I want them there, but I don’t want them running at the moment. Which means I probably don’t want them running after triggering a restart. Can’t you just save the state of them and put them back in the same state after a restart?

Currently on 4.2.5.


1 Like

That seems like a bug to me! Best to report it here:

Graylog bug-n-feature requests


Thanks @NEO-AMiGA and @tmacgbay ,

I’m also bringing this to attention of our core team.

1 Like

cool. have posted a bug report on git as suggested as well.

Good catch,
I tried this out in my environment. After stopping my beats input then restarting my Graylog service that input started backup

2022-01-24T17:47:34.584-06:00 INFO  [connection] Opened connection [connectionId{localValue:13, serverValue:66}] to localhost:27017
2022-01-24T17:47:34.597-06:00 INFO  [InputStateListener] Input [Beats/619318e9d1f2fd03dc7b4b4c] is now RUNNING
2022-01-24T17:47:34.658-06:00 INFO  [InputStateListener] Input [Syslog UDP/61de42ebb99b905bcc09b426] is now RUNNING
2022-01-24T17:47:34.664-06:00 INFO  [InputStateListener] Input [Syslog UDP/61de42ebb99b905bcc09b3fb] is now RUNNING
2022-01-24T17:47:34.672-06:00 INFO  [InputStateListener] Input [Raw/Plaintext UDP/5a6965ef83d72e84ac7ca99b] is now RUNNING
2022-01-24T17:47:34.684-06:00 INFO  [InputStateListener] Input [Raw/Plaintext UDP/5e9f732383d72e05f668a26d] is now RUNNING

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.