-
Notifications
You must be signed in to change notification settings - Fork 253
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
how to reload nagios ? #32
Comments
There is a way to do this from within the web panel for nagios. This will trigger nagios to stop and start reloading any new configuration, - be aware that if there are errors in your configuration then the nagios process will fail to restart, it's a good idea to check that the config is OK using:
|
Thank you.
Exectly what I need.
Get Outlook for Android<https://aka.ms/ghei36>
…________________________________
From: Jason Rivers <notifications@github.com>
Sent: Wednesday, June 14, 2017 11:07:02 AM
To: JasonRivers/Docker-Nagios
Cc: Yuri Shterenberg; Author
Subject: Re: [JasonRivers/Docker-Nagios] how to reload nagios ? (#32)
There is a way to do this from within the web panel for nagios.
On the left hand menu select "Process Info" (near the bottom under System) and then select "Restart the Nagios process"
This will trigger nagios to stop and start reloading any new configuration, - be aware that if there are errors in your configuration then the nagios process will fail to restart, it's a good idea to check that the config is OK using:
nagios -v /opt/nagios/etc/nagios.cfg
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#32 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AVQfUhF7-pNpDb_xSW0kRfEd4bbuterKks5sD5SmgaJpZM4N5hUx>.
|
When I tried to restart I got following error Error: Could not open command file '/opt/nagios/var/rw/nagios.cmd' for update! |
As I understand the only way to apply changes is to restart docker container?
IS there any other options to reload nagios?
The text was updated successfully, but these errors were encountered: