How-To FIX: Time Groups / Time Conditions (7 hours ahead)

[sawgood1000 (Shawn Frye)]

Hi SangomaOS Team:

We are using a very recent .ISO of SangomaOS
We have the System Admin Pro module

The date/time is 100% correct in all accepts except one.

timedatectl = correct
date = correct
Using *60 feature code = correct

The timezone has been set correctly (System Admin Pro)

/etc/php.ini has the correct setting: “America/Los_Angeles”

/etc/localtime has been looked at

The (2) modules inside of the UI still have incorrect “server time”
Time Conditions
Time Groups

They are both (7 hours) ahead

This is the only place on the PBX where the time is not correct.

Thank you for any tips.

[waldrondigital (Mike Waldron)]

I just installed a new ISO today to convert an on prem system to cloud. Same problem. In Los Angeles. Time is correct everywhere except in System Admin/Time Zone.

Curious to see what the fix might be here…

[dobrosavljevic (Igor Dobrosavljevic)]

FreePBX Daylight Savings Issue

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 bega…

[simon_templar]

There’s bug opened about this.

https://issues.freepbx.org/browse/FREEPBX-24071

Fix coming soon.

[dobrosavljevic (Igor Dobrosavljevic)]

I think the fix is already in if you upgrade the framework module to the latest version, which I think is 16.0.39.

[sawgood1000 (Shawn Frye)]

Today, we upgraded the modules …
We got FreePBX framework to 16.0.39

After the update:
The “server time” shown in both of the two modules is still 7-hours ahead.

Those two modules are using UTC -0
We are in UTC -7

The rest of the time is correct throughout the system (even at the CLI level).

Thanks for any thoughts or tips.

[BlazeStudios (Tom Ray)]

@sawgood1000

Those two modules are using UTC -0

When you say they are using you mean that is what they are set to? Because Time Conditions can their own time zone applied per condition. What are the time zones set to in the Time Conditions?

[sawgood1000 (Shawn Frye)]

Hi Tom:

Have not spoken to you in a long time.

The time inside of the timezone section of System Admin Pro is:

America/Los_Angeles

The “Server time” (in the green box next to the Time Zone):
This is off by -7 hours

UTC -0 (is what it is now)
Should be UTC -7

The rest of the PBX (even the CLI) has the correct UTC -7 time
timedatectl
date

[sawgood1000 (Shawn Frye)]

UPDATE:

Even if I pick a different timezone inside of Time Conditions, the label outside of both Time Groups and Time Conditions keeps its “incorrect” time of UTC - 0 (we are UTC -7) America/Los_Angeles

There are no timezone choices inside of Time Groups only Time Conditions has this option.

Thanks for the tips.

[sawgood1000 (Shawn Frye)]

UPDATE:

FreePBX 16 (all modules up to date / current)
FreePBX Framework = 16.0.39

Even the CDR module is showing the time as being “7-hours” ahead.
The time in the reports is off.

If we run timedatectl = correct time
If we run date = correct time

The time in system admin pro (timezone) (UI) is off (ahead) by 7 hours

---

I have found a 2nd box with this same condition.
We have other FPBX 16 up to date boxes where the time is correct in the UI (and) the modules

Thanks for any tips or suggestions.

[PitzKey (Itzik)]

Is the time zone in advanced settings set correctly?

[PitzKey (Itzik)]

I am trying to reproduce this.