-
Notifications
You must be signed in to change notification settings - Fork 4
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
set_signal_handler2 exits always #111
Comments
WTF ... sorry for this! I will fix rapidly ! |
Indeed, I added this function to make some tests about killing modules. This function is not, anyway, useful because it exists in the Alignak BaseModule class which is inherited by the module ... but it looks like if it is never called. The problem you found shows that it is called ! 😞 |
I am an expert in this kind of ... errors. Thank you for your rapid response! |
Indeed, I added this function to make some tests for Alignak killing the modules. This function is not, anyway, useful because it exists in the Alignak BaseModule class which is inherited by the module ... but it looks like if it is never called. The problem you found shows that it is called ! 😞 |
I removed the signals management from the module to use the fucntions of the base class. This modification arose a small problem with the unit tests and I also fixed this. Travis tests in progress... |
Fixes #111 - stupid error in the signals management...
exit(12) at https://github.com/Alignak-monitoring-contrib/alignak-module-ws/blob/develop/alignak_module_ws/ws.py#L1837 kills the module, so modulesmanager is trying to restart it forever...
The text was updated successfully, but these errors were encountered: