I’'m now testing this on a 1.2.0 FOG server also on Ubuntu Server 14.04.3. Same problem.
@Wayne-Workman said:
@JeffD So what happens if you log into your FOG server via SSH and issue the date
command?
It should return with the day, month, year, and time… How accurate is it?
Seems accurate down to the second, timezone and all.
@george1421 said:
It would be interesting to know what if anything is posted to the /opt/fog/log/taskscheduler.log when one of these scheduled events are missed. If its not in there, one might think one of the logs would say what just happened. This is very strange that “nothing” happens.
You might want to check to see if the fog task scheduler service is running. I might be able to understand if the scheduler is not running. The web gui looks at the database where the scheduled task is run. It calculates when it should run and displays that to the user. So the time line is correct from the users perspective. Its just the task never kicks off on the back end. This is all speculation, but it sounds logical.
I did not find /opt/fog/log/taskscheduler.log but I did find fogscheduler.log there. I assume this is the same thing? These are the last 10 entries.
[12-10-15 7:51:30 am] * 0 active task(s) awaiting check-in.
[12-10-15 7:51:30 am] * No tasks found!
[12-10-15 7:52:30 am] * 0 active task(s) awaiting check-in.
[12-10-15 7:52:30 am] * 1 task(s) found.
[12-10-15 7:52:30 am] * Task run time: Thu, 10 Dec 2015 08:51:00 +0000
[12-10-15 7:52:30 am] * Task doesn't run now.
[12-10-15 7:53:30 am] * 0 active task(s) awaiting check-in.
[12-10-15 7:53:30 am] * No tasks found!
[12-10-15 7:54:30 am] * 0 active task(s) awaiting check-in.
[12-10-15 7:54:30 am] * No tasks found!
The strange thing is I scheduled a task for 9:24am, and I looked this up at around 9:25 am. The log shows 7:52 am and there definitely weren’t any tasks planned at that time.