Cron start and end timestamps are incorrect they can show as times in different timezones

Bug #1949519 reported by Robert Lyon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mahara
Status tracked in 22.04
20.10
Undecided
Unassigned
21.04
Undecided
Unassigned
21.10
Undecided
Unassigned
22.04
High
Unassigned

Bug Description

An example of the cron output

[INF] 48 (lib/cron.php:55) ---------- cron running Wed, 03 Nov 2021 09:00:21 +1300 ----------
[INF] 48 (lib/cron.php:193) Running core cron check_imap_for_bounces
[INF] 48 (lib/cron.php:193) Running core cron watchlist_process_notifications
[INF] 48 (lib/cron.php:193) Running core cron export_process_queue
[INF] 48 (lib/cron.php:193) Running core cron activity_process_queue
[INF] 48 (lib/cron.php:193) Running core cron import_process_queue
[INF] 48 (lib/cron.php:235) ---------- cron finished Tue, 02 Nov 2021 20:00:22 +0000 ----------

Note the start time is in the future compared to the end time

Need to sort out so that both timestamps are in the same timezone

Robert Lyon (robertl-9)
Changed in mahara:
importance: Undecided → Medium
importance: Medium → High
milestone: none → 22.04.0
status: New → In Progress
Revision history for this message
Robert Lyon (robertl-9) wrote :

It seems as though during the cron process the timezone changes so am suspecting there is a cron job that changes the timezone so that the finish time ends up being UTC time

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers