On 18 May 2010, at 23:39, Phillips, Dustin B wrote:
Ton,
See the attached file for the output of that command. If there were
errors I did not see them.
Also, not to confuse the issues but we just noticed that the WebUI
is not in sync with Nagios. In other words, the host and service
status displayed when you first log in to the Opsview WebUI are
stale - when you click on a host or service to reach the pages
generated by the Nagios CGIs, the host and service status is
accurate and up to date.
We've seen this in the past and have found it happens when the
server is backed up on processing ndo logs but that is not the case
this time. Is there a way to force Opsview to refresh the host and
service status shown in the WebUI? I manually rescheduled a host
check as a test but that had no effect.
My guess is that you've had a problem on your Opsview server with the
clock.
If the time on the server has been pushed to say, 1 week, in the
future, then the RRDs will be updated with this new time and the
database will be updated with this new time. Then if you've seen this
problem, you revert the time back to now, but the RRDs and the
database say that the last updated time is 1 week in the future and
will refuse to update anything until that time has passed.
This would explain why RRD inserts appear to work (though it is a bit
rubbish that we are not propagating the error back up - I'll look into
that).
This also explains why the runtime status for all your hosts/services
are not being updated.
Could this have happened? To check the RRDs, pick an RRD file that is
not updating and run rrdtool dump {filename}.
To check the runtime database, run: select * from nagios_programstatus\G
To check the hosts, run: select max(status_update_time) from
nagios_hoststatus;
Ton
_______________________________________________
Opsview-users mailing list
[email protected]
http://lists.opsview.org/lists/listinfo/opsview-users
