status.cgi - times out by 1 hour until I restart apache
Karl Skidmore
Karl at multimap.com
Fri Oct 22 12:36:42 CEST 2004
Thanks for the advice. I tried those changes, but unfortunately the
symptoms remain.
Another finding: It seems that even on subsequent refreshes of the same
page https://myhost/nagios/cgi-bin/showlog.cgi the time shown changes by
exactly 1 hour. I can confirm this is not a caching issue as the events
in the content returned are being updated each time.
I never had this with Netsaint. Any ideas?
-----Original Message-----
From: nagios-users-admin at lists.sourceforge.net
[mailto:nagios-users-admin at lists.sourceforge.net] On Behalf Of Tedman
Eng
Sent: 20 October 2004 06:40
To: 'nagios-users at lists.sourceforge.net'
Cc: Karl Skidmore
Subject: RE: [Nagios-users] status.cgi - times out by 1 hour until I
restart apache
Its possible that your nagios or apache accounts are running at system
timezone and you're running in local timezone (though only within your
user
environment). The time displayed in the web interface is offset using
your
timezone setting (not sure if it's apache's or nagios' timezone). To
set it
systemwide, find the appropriate file (ie.
/usr/share/zoneinfo/Europe/Zurich) and copy it over your system's
timezone
file (ie /etc/localtime).
Also, check your UTC time (date -u) once more, and set the system's
hardware
clock (setclock) if needed. If the date changed dramatically, you may
need
to also restart the ntpd daemon if you use that.
-----Original Message-----
From: Karl Skidmore [mailto:Karl at multimap.com]
Sent: Tuesday, October 19, 2004 2:45 PM
To:
Subject: [Nagios-users] status.cgi - times out by 1 hour until I restart
apache
Hi All,
I've found that 'sometimes' times displayed by status.cgi / showlog.cgi
/
etc can be exactly 1 hour out. The status and log entry content is up
to
date, but the times reported are offset by 1 hour. If I restart apache
the
times shown are correct - only for a while though. The system clock is
always valid (and regularly sync'd with an NTP server).
I've not worked out what triggers this offset to take hold yet. Has
anyone
else seen this issue?
My apache config is rather esoteric (fcgi, gzip, ssl, authenticated via
an
external app), but I don't think this has anything to do with it.
Cheers... Karl
Principal Software Architect
Multimap.com
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give
us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out
more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when
reporting any issue.
::: Messages without supporting info will risk being sent to /dev/null
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.
::: Messages without supporting info will risk being sent to /dev/null
More information about the Users
mailing list