-
Notifications
You must be signed in to change notification settings - Fork 6
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
fix(gorgone) correctly handle gorgone pullwss module shutdown #1530
fix(gorgone) correctly handle gorgone pullwss module shutdown #1530
Conversation
Important Review skippedAuto reviews are limited to specific labels. Labels to auto review (1)
Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
…g pullwss module. Refs:MON-34540
Zmq object need to be undef at the end of the module life or a C stack trace will appear in the logs. The sigterm handler was not called by perl, Mojo::IOLoop::Signal allow to correctly call the signal handler when quiting. Refs:MON-34540
Refs:MON-34540
6bbe6e4
to
340826d
Compare
Description
Migrated from centreon/centreon#4178
This PR remove some C++ stack trace present when pullwss module unload by closing the zmq socket before the global destruction of the module.
It also use a new library Mojo::IOLoop::Signal to correctly handle sigterm signal, which was not always handled.
Fixes # (issue)
Type of change
Target serie
How this pull request can be tested ?
See the robot tests, connecting a poller to a central and disconecting them should not add any C++ level error in the poller logs. you should test both when the poller go down first (with a sigterm) and when the central go down first.Checklist
Community contributors & Centreon team