Skip to content
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

Why do event listeners not report the process exit status when stopped/crashed? #1150

Open
pisymbol opened this issue Sep 19, 2018 · 2 comments
Labels

Comments

@pisymbol
Copy link

pisymbol commented Sep 19, 2018

I want to find out the exit status of a process under supervisord using the event listeners API. But looking at the doc there seems to be no mechanism to report the exit status of a process when it goes down.

This seems like a glaringly obvious missing feature. Minimally, I need the exit status code for logging purposes so I can figure out if its a crash, a simple stop, etc. etc.

Is there really no way to get this information using the event API?

@f18m
Copy link

f18m commented Jan 29, 2019

Hi,
I'm in the same situation. For example sometimes I find in supervisord.log prints like:

2019-01-26 15:48:57,765 INFO stopped: mystatemachine (exit status 0)

which is good, and sometimes prints like:

2019-01-26 15:48:45,218 WARN killing 'mystatemachine' (108301) with SIGKILL
2019-01-26 15:48:45,674 INFO stopped: mystatemachine (terminated by SIGKILL)

and the problem is that my event listener will NOT get notified. I would like to know instead if my process has been killed by supervisord (in my case due to the fact it did not respect the "stopwaitsecs" threshold)...

@f18m
Copy link

f18m commented Jan 29, 2019

PS: I can help with this feature by contributing a PR if authors of the projects agree it's useful...

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

No branches or pull requests

3 participants