core Config manager Apply twice problem

[niebais]

We've found a bug in the system where it causes us to apply twice for every new item or change we make. We're running 2009R1.2.

When I add a new service to Nagios, I click on "save" then "apply configuration". I go over to "Home->Service Detail" and I see the newly added service in pending. When I click on it, it shows the next check will be in 1970. If I click on apply configuration again the service will set to the correct time. At times, these services won't update until I click on apply configuration again.

[Box293]

After you click apply the first time, what happens if you go to the Admin menu and restart the Monitoring Engine?

[tonyyarusso]

I would imagine there would be a minute or two delay before changes took effect - you're saying though that you have tried waiting, and no check occurs?

[niebais]

After you click apply the first time, what happens if you go to the Admin menu and restart the Monitoring Engine?

Well, I've noticed I can do a restart on the command line "service nagios restart" and it has the same effect.

[niebais]

I would imagine there would be a minute or two delay before changes took effect - you're saying though that you have tried waiting, and no check occurs?

The odd part is that the check does occur most of the time. However, we've had a couple that haven't done any checks until we've restarted the monitoring engine.

[admin]

The check time may show 1970 sometimes, as that's the Unix epoch time (0 seconds). This is a temporary display issue only and gets updated when the Nagios Core monitoring engine either checks or reschedules the host or service. It shouldn't affect the actual check of the host or service. Also note that it may take up to 5 minutes (or whatever you set the check interval to be) before the host/service times are updated in the UI.

We'll put this behavior issue on our list of things to change in a future version, as it can be confusing.

[niebais]

The problem with it is that you can't schedule an immediate check on those kinds of services and people in other departments get confused with the weird time stamp. It's not a huge bug, but it is annoying when you're doing demos to other departments. Thanks for looking into this.