JSS time issue

[fsjjeff]

Recently I've started seeing some strange time issues with my JSS, hoping someone has an idea on how to resolve this...

Essentially, when I look at the inventory/connection status of devices, they are often reporting last connection/inventory time in the future by several hours. If you look in the attached screenshot, you can see my computer is at 8:59am, but one of the computers is reporting it's last checkin time as today at 2pm, which is several hours in the future.

I've looked at the Linux server running the JSS and the time is correct there, and also checked the mysql server and the time there is also correct. I tried looking in settings to see if there was somewhere to configure time zone, but not seeing anything. I generated a JSS Summary and interestingly it shows as being generated an hour ago, so something is definitely strange.

Anyone know of something I'm missing?

Thanks,

Jeff

[emily]

What version of the JSS are you on? And do you use SSO? I remember at some point there being an issue where if you used SSO it didn't save your timezone preferences.

[mike_paul]

Some things are based off of server time and some are based off of the time zone you specify in your JSS user's Account Preferences. If you are running 9.100.0 or above you can also disable the whole use of Relative Dates as well.

Hopefully that helps but let us know if you are still seeing issues after modifying your user preferences.

Thanks
Mike

[fsjjeff]

Emily, we're on the newest version, 9.100.0-t1499435238 to be exact, and not using SSO.

Mike, I hadn't looked at my personal account preferences, but just did and I'm set to the correct time zone. I tried disabling relative dates, but the computer checkins are still showing as 7 hours in the future.

I'm hosting the JSS on an Ubuntu 16.04.2 LTS server, and if I enter the date command, I get the correct result: Thu Sep 7 14:17:05 PDT 2017.

I also read somewhere that it could be the mysql service having the wrong time, but using the SELECT CURDATE(); and SELECT CURTIME(); also gives me the correct results.

Like I said, I'm a bit stumped on why this would be happening. Could it be a setting on the clients themselves somehow? They should all be pointed to our NTP servers.