So the yearly spring forward has occured, and it appears ALL our FreePBX servers are living an hour in the past still for the System Admin and Time Conditions.
OS configuration is correct:
# timedatectl
Local time: Sun 2023-03-12 12:17:04 EDT
Universal time: Sun 2023-03-12 16:17:04 UTC
RTC time: Sun 2023-03-12 12:17:04
Time zone: America/Toronto (EDT, -0400)
NTP enabled: yes
NTP synchronized: yes
RTC in local TZ: yes
DST active: yes
Last DST change: DST began at
Sun 2023-03-12 01:59:59 EST
Sun 2023-03-12 03:00:00 EDT
Next DST change: DST ends (the clock jumps one hour backwards) at
Sun 2023-11-05 01:59:59 EDT
Sun 2023-11-05 01:00:00 EST
timezone file is correct
# ls -l /etc/localtime
lrwxrwxrwx 1 root root 35 Mar 12 12:13 /etc/localtime -> /usr/share/zoneinfo/America/Toronto
PHP is showing correct:
# cat /etc/php.ini | grep timezone
; Defines the default timezone used by the date functions
; http://php.net/date.timezone
date.timezone = "America/Toronto" ;;;; Automatically updated by Sysadmin
# php -r 'echo date(DATE_RFC2822) . "\n";'
Sun, 12 Mar 2023 12:19:04 -0400
But not freepbx! Going to Admin → System Admin and selecting “Time Zone” it shows the correct time zone but “Server time: 11:20:50 EST”
This isn’t isolated, it’s occurring on all our client FreePBX installs as well, about 30 PBXs all mix of FreePBX14 and FreePBX15 across the board (most 15).
It’s not an OS issue, as none of our others CentOS servers appear to be having this issue… There are no yum updates or system module updates. It just appears that the FreePBX software itself takes the provided DST info and throws it out the window in favor of the flat -5 EST timezone.
Thoughts?