Nectar Plugin: date/time incorrect

[kbartoletta]

Does anyone know where the nectar plugin might be getting it's date and time from. For example - I go to schedule a daily report to be emailed out... I schedule the report for 10:00am and save it and then it shows the next scheduled time for 15:00... the system date on the box is correct 8:01am PDT. so the report should schedule for 10am with know problems... for some the plugin believes that 10am has already passed.... If I schedule a reports for 2000 then the scheduled time shows 2000 however the reports shows up at some other time other than what is truely 2000 PDT. It is almost as it mysql believes that it is in another time zone...

any ideas?

[kbartoletta]

Disregard - i was able to find that that mysql time stamp is way off from the system time - mysql is configured to use SYSTEM as the time zone so i am not sure what is going on here - regardless... it is not a cacti or nectar problem.


#############################
HERE IS THE TIME STAMP IN THE DATABASE

mysql> select current_timestamp;
+---------------------+
| current_timestamp |
+---------------------+
| 2010-06-16 15:44:45 |
+---------------------+
1 row in set (0.00 sec)

########################
HERE IS THE SYSTEM TIME STAMP

[root@localhost cacti]# date
Wed Jun 16 08:44:49 PDT 2010

[gandalf]

What are your timezone settings, please?
R.

[mcutting]

Sorry to hijack this, but I just posted a similar issue in the same forum. If it helps, my timezone is BST

My thread is here http://forums.cacti.net/viewtopic.php?t=38230

[mcutting]

Another thing that is more cosmetic than anything else is

[gandalf]

Another thing that is more cosmetic than anything else is

I know this. We decided not to fix this in 087g.
Root cause is, that the Cacti Header uses "absmiddle", which is not W3C compliant. I use "middle", which is W3C compliant. The net result is seen in your screenshot
R.

[mcutting]

even after changing "middle" for "absmiddle", the issue is still there.