The Scheduled Tasks feature is not functioning in version 1.6.0-beta.2167

[swireb]

Describe the bug
I sincerely appreciate FogProject's work. Version 1.5.10 has been flawless for batch OS deployments!
but during my 1.6.0-beta tests, I encountered issues with the Scheduled Tasks functionality:

1. When scheduling a 1-minute recurring task through both hosts and groups, no entries appeared in the Active Tasks list.
2. The group-deployed tasks additionally exhibited incorrect timing behavior.

Screenshots

Software (please complete the following information):

• FOG version [1.6.0-beta.2167]
• OS: [Rocky Linux 9.5]

[darksidemilk]

Did 1-minute recurring tasks work before?
Have you made sure your timezone is correct in /etc/php.ini ?
I don't have any recurring tasks, but I do use scheduled deploy tasks in fog 1.6 on a regular basis without issue.
Is the timezone correct on the server?
When you are in the gui and go to create a scheduled task with a specific date/time, does the default show the correct current time?

I have found there to be a 1-2 minute delay in the tasks starting after the scheduled time passes.
There are also services that fog installed that need to be running, i.e. sudo systemctl status FOGScheduler.service to check if the scheduler is running. other Fog services start with all caps FOG i.e.

sudo systemctl list-units FOG*
  UNIT                        LOAD   ACTIVE SUB     DESCRIPTION
  FOGFileDeleter.service      loaded active running FOGFileDeleter
  FOGImageReplicator.service  loaded active running FOGImageReplicator
  FOGImageSize.service        loaded active running FOGImageSize
  FOGMulticastManager.service loaded active running FOGMulticastManager
  FOGPingHosts.service        loaded active running FOGPingHosts
  FOGScheduler.service        loaded active running FOGScheduler
  FOGSnapinHash.service       loaded active running FOGSnapinHash
  FOGSnapinReplicator.service loaded active running FOGSnapinReplicator

You should also check the /opt/fog/log/fogscheduler.log for any errors. The timestamps in this log should also match your timezone.

[swireb]

Thank you very much for your reply.

I tried to configure the correct timezone for PHP and restarted the server.

However, after re-deploying the task, the incorrect time is still displayed.

Below are the results of my checks.

[root@localhost ~]# php -i | grep "Default timezone"
Default timezone => Asia/Shanghai

[root@localhost ~]# sudo systemctl status FOGScheduler.service
● FOGScheduler.service - FOGScheduler
     Loaded: loaded (/usr/lib/systemd/system/FOGScheduler.service; enabled; preset: disabled)
     Active: active (running) since Thu 2025-05-22 19:02:12 CST; 7h left
   Main PID: 1070 (php)
      Tasks: 2 (limit: 48712)
     Memory: 13.6M
        CPU: 179ms
     CGroup: /system.slice/FOGScheduler.service
             ├─1070 php /opt/fog/service/FOGTaskScheduler/FOGTaskScheduler
             └─1086 php /opt/fog/service/FOGTaskScheduler/FOGTaskScheduler

May 22 19:02:12 localhost.localdomain systemd[1]: Started FOGScheduler.

[root@localhost ~]# sudo systemctl list-units FOG*
  UNIT                        LOAD   ACTIVE SUB     DESCRIPTION        
  FOGFileDeleter.service      loaded active running FOGFileDeleter
  FOGImageReplicator.service  loaded active running FOGImageReplicator
  FOGImageSize.service        loaded active running FOGImageSize
  FOGMulticastManager.service loaded active running FOGMulticastManager
  FOGPingHosts.service        loaded active running FOGPingHosts
  FOGScheduler.service        loaded active running FOGScheduler
  FOGSnapinHash.service       loaded active running FOGSnapinHash
  FOGSnapinReplicator.service loaded active running FOGSnapinReplicator
LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
8 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.


[root@localhost ~]# cat /opt/fog/log/fogscheduler.log
[05-22-25 7:02:12 pm] 
==================================
===        ====    =====      ====
===  =========  ==  ===   ==   ===
===  ========  ====  ==  ====  ===
===  ========  ====  ==  =========
===      ====  ====  ==  =========
===  ========  ====  ==  ===   ===
===  ========  ====  ==  ====  ===
===  =========  ==  ===   ==   ===
===  ==========    =====      ====
==================================
===== Free Opensource Ghost ======
==================================
============ Credits =============
= https://fogproject.org/Credits =
==================================
== Released under GPL Version 3 ==
==================================
[05-22-25 7:02:12 pm] Interface Ready with IP Address: 10.0.0.245
[05-22-25 7:02:12 pm] Interface Ready with IP Address: 127.0.0.1
[05-22-25 7:02:12 pm] Interface Ready with IP Address: 127.0.1.1
[05-22-25 7:02:12 pm] Interface Ready with IP Address: localhost.localdomain
[05-22-25 7:02:12 pm]  * Starting TaskScheduler Service
[05-22-25 7:02:12 pm]  * Checking for new items every 60 seconds
[05-22-25 7:02:12 pm]  * Starting service loop
[05-22-25 7:02:12 pm]  * No tasks found!

I also tried creating a task that runs every minute

[darksidemilk]

The 1970 being the time for the schedule is real odd. Does it work if you specify a time?

[lukebarone]

32 bit os?

[swireb]

The 1970 being the time for the schedule is real odd. Does it work if you specify a time?

In addition to noticing that the task time is incorrect, I also found that the task type is wrong. I created it as a scheduled task, but it ended up being categorized as 'Delayed'. I tried manually modifying the time and type directly in the database, but it still didn't work correctly.

[swireb]

32 bit os?

[root@localhost ~]# uname -m
x86_64

[darksidemilk]

I'm pretty sure delayed and scheduled are the same in this context.
If the time in the server is right and the time setting sin fog are right there must be somewhere we have a revert to the "epoch" time of 1970.

[swireb]

I'm pretty sure delayed and scheduled are the same in this context. If the time in the server is right and the time setting sin fog are right there must be somewhere we have a revert to the "epoch" time of 1970.

I created a 1-hour scheduled task for both hosts and groups through the web interface for comparison.

By checking the scheduledTasks table in the database, I found that the scheduled task created for groups has incorrect values in the following fields.

I manually corrected the incorrect fields in the database.

After refreshing the web interface, the scheduled task times are displayed correctly.

While checking the service operation, I found an alert, but I'm not sure whether this alert is the direct cause of the bug.

[root@localhost ~]# systemctl status FOGScheduler.service
● FOGScheduler.service - FOGScheduler
     Loaded: loaded (/usr/lib/systemd/system/FOGScheduler.service; enabled; preset: disabled)
     Active: active (running) since Mon 2025-05-26 17:26:56 CST; 6min ago
   Main PID: 1454 (php)
      Tasks: 2 (limit: 22943)
     Memory: 26.2M
        CPU: 24.920s
     CGroup: /system.slice/FOGScheduler.service
             ├─1454 php /opt/fog/service/FOGTaskScheduler/FOGTaskScheduler
             └─1542 php /opt/fog/service/FOGTaskScheduler/FOGTaskScheduler

May 26 17:26:56 localhost.localdomain systemd[1]: Started FOGScheduler.
May 26 17:31:31 localhost.localdomain env[1542]: PHP Warning:  Undefined variable $stat in /var/www/html/fog/lib/fog/group.class.php on line 768

Finally, I restarted the server, and the scheduled task created through groups began working normally.

[darksidemilk]

I have now been able to recreate this issue with a cron style every minute task.
Still narrowing it down.

[darksidemilk]

AH01071: Got error 'PHP message: PHP Warning:  Undefined array key 1 in /var/www/html/fog/lib/fog/fogcron.class.php on line 162; 

[darksidemilk]

It appears to be scheduled tasks on groups specifically. Cron and delayed tasks on individual hosts work fine, but the date is wrong for group scheduled tasks.