Hi All
I have configured an Alert in Nagios Log Server.
If I press the Icon "Run the alert now" the Date an Time in the "Lat Run" field are okay.
But as soon the schedule runs this alert, the Time of the "Last Run" is changed to a future time.
Our Cluster Timezone is set (UTC+01:00) Bern.
We have also configure NTP on the Nagios Log Servers.
Where else do we need to correct/set up the time?
We are running the latest version of Nagios Log Server 2015R1.3.
Thank you for your help in this matter.
Last Run Time is in Future for alerting
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Last Run Time is in Future for alerting
Can you run the following
Code: Select all
date
cat /etc/php.ini|grep date.timezone
Re: Last Run Time is in Future for alerting
Hi scottwilkerson
Thank you for your feedback.
Below the information you requested:
[root@cnalg346 ~]# date
Fri Feb 27 09:28:51 CET 2015
[root@cnalg346 ~]# cat /etc/php.ini|grep date.timezone
; http://www.php.net/manual/en/datetime.c ... e.timezone
date.timezone = Europe/Berlin
[root@cnalg346 ~]#
Thank you for your feedback.
Below the information you requested:
[root@cnalg346 ~]# date
Fri Feb 27 09:28:51 CET 2015
[root@cnalg346 ~]# cat /etc/php.ini|grep date.timezone
; http://www.php.net/manual/en/datetime.c ... e.timezone
date.timezone = Europe/Berlin
[root@cnalg346 ~]#
Re: Last Run Time is in Future for alerting
Have you restarted the httpd server since making the php.ini changes?
Code: Select all
service httpd restartFormer Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
-
jdalrymple
- Skynet Drone
- Posts: 2620
- Joined: Wed Feb 11, 2015 1:56 pm
Re: Last Run Time is in Future for alerting
It might be helpful for us if you could tell us ~how far in the future the Last Run Time is. Does it seem to be a random small number, a random large number, or does it seem to be a timezone offset problem?
Thanks
Thanks
Re: Last Run Time is in Future for alerting
Hi All
The Problem is solved.
The DNS IP on the 2nd Nagios Log Server instance was wrong.
We run 2 Nagios Log Server instances.
The DNS IP on the 1st Nagios Log Server was okay but the DNS IP on the 2nd Nagios Log Server was wrong.
We corrected that and it's okay now.
The Problem is solved.
The DNS IP on the 2nd Nagios Log Server instance was wrong.
We run 2 Nagios Log Server instances.
The DNS IP on the 1st Nagios Log Server was okay but the DNS IP on the 2nd Nagios Log Server was wrong.
We corrected that and it's okay now.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Last Run Time is in Future for alerting
Glad you got this resolved.