Odd...that fixes it. So why does having a valid timezone in php.ini break whatever date math is going on to cause it to spit out ~1yr intervals...system TZ is UTC but I had the php TZ set America/Los_Angeles ... is having them not agreeing causing this? (No, haven't looked into the code at all yet....)

On Fri, May 9, 2014 at 12:30 PM, Poussin, Mathieu Mathieu.POUSSIN@sodexo.com wrote:

Check your php timezone about your time issue

Sent from my iPhone

...

On 09 May 2014, at 21:10, "Michael Loftis" mloftis@wgops.com wrote:

I'm actually not certain when this started to happen as I've noticed it before, but it seemed like it was just in old events, but now, I've noticed that all relative times are getting computed incorrectly, they'll all show like "364 days, 17h 13m 3s" when you hover for an actual time (system event log particularly) the timestamps are right...it's something going wonk doing date math I'm guessing...

0.14.5.5458 - php 5.4.4 (just svn updated to make sure it wasn't fixed)

not sure what else is relevant...

--

"Genius might be described as a supreme capacity for getting its possessors into trouble of all kinds." -- Samuel Butler _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

This e-mail, attachments included, is confidential. It is intended solely for the addressees. If you are not an intended recipient, any use, copy or diffusion, even partial of this message is prohibited. Please delete it and notify the sender immediately. Since the integrity of this message cannot be guaranteed on the Internet, SODEXO cannot therefore be considered liable for its content.

Ce message, pieces jointes incluses, est confidentiel. Il est etabli a l'attention exclusive de ses destinataires. Si vous n'etes pas un destinataire, toute utilisation, copie ou diffusion, meme partielle de ce message est interdite. Merci de le detruire et d'en avertir immediatement l'expediteur. L'integrite de ce message ne pouvant etre garantie sur Internet, SODEXO ne peut etre tenu responsable de son contenu. _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

On Fri, May 9, 2014 at 1:58 PM, Adam Armstrong adama@memetic.org wrote:

Timezones are all voodoo. You mess with them at your peril!

But it hurts doc! (see below) :)

VBVFM even. Thats why I usually personally prefer to leave everything UTC. But I was anticipating complaints from users. It's going to stay UTC now.

You may have set your PHP timezone, but what about the MySQL timezone? This is probably where the issue occured.

Yeah...that could've done it, PHP doing one thing, MySQL doing another....yupI see how the ~1yr stamps happened now (date maths ending up like date_sub(past,future) instead of date_Sub(future,past) probably, due to the offset - which explains why some seemed ok and others didn't...once it was more than the TZ offset viola)

Any configuration other than having every timezone on the server set identically is unsupported. Not all time calculations and storage performed in Observium are done in PHP.

adam.

TYVM, "doctor says don't do that" :)