Scheduling Snapins always says date is in the past

[JJ Fullmer]

Server

• Version: SVN 5956 (RC 11 branch because I’m a daredevil)
• OS: Cent OS 7

Client

• Version: 0.11.5
• OS: win 10 ltsb

Description

When I try to schedule a delayed snapin task for a group it always say that the date is in the past.

[Tom Elliott]

I imagine this also happens with hosts (not only groups?)

I’ve found the lil bugger (I fixed it once before, I thought).

[george1421]

Well for some reason I think FOG lies…

Its not just a timezone issue here its off by days not just hours. If it was hours then I would say we need to update the php.ini file to reflect the correct time. If you drop to the fog linux console, is the time in agreement with the fog web gui?

[Tom Elliott]

I imagine this also happens with hosts (not only groups?)

I’ve found the lil bugger (I fixed it once before, I thought).

[Wayne Workman]

@Tom-Elliott This is why client updating is broke! Wanna bet?

[Tom Elliott]

@Wayne-Workman nope not at all. That is only for delayed tasks

[JJ Fullmer]

@george1421 Good question. The date command brings up the right time. The time in the top left corner of the gui also brings up the right time.
I haven’t double checked the fog time zone settings to make sure they didn’t revert though. I’ll check on that and I’ll check the php.ini file and get back to this.

The time zone was still set proper in the fog gui. But there was no timezone set in /etc/php.ini Not sure if that’s the right php.ini file though because I recall it being more difficult to find the last time I had to edit it.

@Tom-Elliott I was able to schedule some cron tasks over the weekend without the error, however it seems they didn’t actually execute.

These are mostly wireless clients, and it was a simple snapin, just a one line batch script to update group policy and restart. (gpupdate /force & shutdown /r /t 00)

And then I just realized you’re saying you fixed it. I should probably update

[JJ Fullmer]

Updated and confirmed fixed. Making sure the snapin deploys now too.

[JJ Fullmer]

@Tom-Elliott Now this may have been an operator error on my part, but I don’t remember doing anything that would have caused this.
On all my hosts most of the service configurations had been disabled, i.e. snapins. Which is why my tasks didn’t deploy.

[JJ Fullmer]

@Tom-Elliott Figured it out, it’s a different bug, made a new post
https://forums.fogproject.org/topic/8600/group-service-settings-not-applying-sort-of