New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sidecar processes are shown as "running" even after host is offline #5097

Open
lennartkoopmann opened this Issue Sep 11, 2018 · 3 comments

Comments

Projects
None yet
3 participants
@lennartkoopmann
Member

lennartkoopmann commented Sep 11, 2018

I have a host with an installed sidecar but the host is currently not running. The whole machine is shut down.

This is properly reflected in the list of sidecars because it's marked as inactive and hidden by default, until I enable the option to show inactive sidecars:

screenshot from 2018-09-11 18-48-06

However, it still shows all the collector processes as running:

screenshot from 2018-09-11 18-47-50

Your Environment

  • Graylog Version: Graylog 3.0.0-alpha.2-SNAPSHOT+73c96fa

@lennartkoopmann lennartkoopmann added this to the 3.0.0 milestone Sep 11, 2018

@edmundoa

This comment has been minimized.

Show comment
Hide comment
@edmundoa

edmundoa Sep 12, 2018

Member

This was fixed here, at least we include an inactive indicator now: #5092

Please reopen if you think this is still not clear enough :)

Member

edmundoa commented Sep 12, 2018

This was fixed here, at least we include an inactive indicator now: #5092

Please reopen if you think this is still not clear enough :)

@edmundoa edmundoa closed this Sep 12, 2018

@edmundoa

This comment has been minimized.

Show comment
Hide comment
@edmundoa

edmundoa Sep 12, 2018

Member

Now that I read this again: I'll reopen, since the collectors themselves shouldn't be marked as running anyway.

Member

edmundoa commented Sep 12, 2018

Now that I read this again: I'll reopen, since the collectors themselves shouldn't be marked as running anyway.

@edmundoa edmundoa reopened this Sep 12, 2018

@edmundoa

This comment has been minimized.

Show comment
Hide comment
@edmundoa

edmundoa Sep 12, 2018

Member

Regarding the running state, it has been fixed in #5052, and it's in master already.

@lennartkoopmann can you update your branch and see if the problem still occurs? Thank you!

Member

edmundoa commented Sep 12, 2018

Regarding the running state, it has been fixed in #5052, and it's in master already.

@lennartkoopmann can you update your branch and see if the problem still occurs? Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment