Hello. Ran across Pandorafms looking for a Nagios replacement... and must say that I am in love with this! I am having an odd issue though. Both with a VM and on a separate physical machine. I have gone through the WIKI and several other things on the net dealing with PHP and xml. Everything appears to be set correctly and the times across the system match up. But my agents will not check. This happened after I rebooted the physical server after the inital appliance CD install. Here's the system data and things I have gone through thus far. The only thing I cannot change and keep the change applied is for mysql. But its pulling from the system time so it should be correct. TZ's have all been set to: America/New_York Pandora -> Setup: America/New_York WIKI Items: Set the zones in include/config_process.php. # date +"%z" -0400 # date Wed Mar 18 14:43:13 EDT 2015 mysql> select now(); +---------------------+ | now() | +---------------------+ | 2015-03-18 14:43:46 | +---------------------+ 1 row in set (0.00 sec) mysql> SELECT @@global.time_zone, @@session.time_zone; +--------------------+---------------------+ | @@global.time_zone | @@session.time_zone | +--------------------+---------------------+ | SYSTEM | SYSTEM | +--------------------+---------------------+ 1 row in set (0.00 sec) ]# perl -e 'my $t = localtime(); print "$t";' Wed Mar 18 14:44:38 2015 Returns - 2015/03/18 14:45:00 -0400 /include/config.php putenv("TZ=America/New_York"); Also found an addition to the php test file to see if the ini/server tz was the same. It reports it is correct: date_default_timezone_set('America/New_York'); $script_tz = date_default_timezone_get(); if (strcmp($script_tz, ini_get('date.timezone'))){ echo 'Script timezone differs from ini-set timezone.'; } else { echo 'Script timezone and ini-set timezone match.'; } Returns: Script timezone and ini-set timezone match. hwclock --debug hwclock from util-linux-ng 2.17.2 Using /dev interface to clock. Last drift adjustment done at 1426696800 seconds after 1969 Last calibration done at 1426696800 seconds after 1969 Hardware clock is on UTC time Assuming hardware clock is kept in UTC time. Waiting for clock tick... ...got clock tick Time read from Hardware Clock: 2015/03/18 19:32:48 Hw clock time : 2015/03/18 19:32:48 = 1426707168 seconds since 1969 Wed 18 Mar 2015 03:32:48 PM EDT -0.937902 seconds Correct time... got held up posting Help!
[
](//pandorafms.com/community/media/forum/0/18282=791-Capture.PNG)
