After hours mode triggering at the wrong time

[architechture]

I have v18 server that was running on a local on-prem computer. That computer died so we decided to move it to ec2. Before the move it was running the in hours and after hours autoswitch correctly. Now it seems to run like it's on UTC even though of course I've reset the timezone and restarted the server etc.

Any advice?

 

[architechture]

This is windows server by the way. I see this in the activity log:
03/03/2022 5:15:40 PM - Timezone offset: 0 min.

Does it mean no offset is being applied?

 

[architechture]

Another bit of evidence. My backups show they are being made at 8pm even I have them set for 02:00.

 

[NickD_3CX]

Hi!

So the server seems to perform all scheduled actions at the wrong time (office hours, backups, etc). This is indeed useful.

So you said you moved to EC2 when your Windows Server died. Are you still now running on EC2? I also assume this means that your 3CX is running on Debian, right?

 

[architechture]

Hi!

So the server seems to perform all scheduled actions at the wrong time (office hours, backups, etc). This is indeed useful.

So you said you moved to EC2 when your Windows Server died. Are you still now running on EC2? I also assume this means that your 3CX is running on Debian, right?

Windows Server

 

[NickD_3CX]

Windows Server

OK, then my first questions is, why not install on Debian? I can say for sure it will be cheaper in AWS than running Windows.
Also we have never tested Windows in AWS or any hosting provider for that matter, only Debian.

Also, can you confirm the other thing I asked too?

So the server seems to perform all scheduled actions at the wrong time (office hours, backups, etc). This is indeed useful.

 

[architechture]

OK, then my first questions is, why not install on Debian? I can say for sure it will be cheaper in AWS than running Windows.
Also we have never tested Windows in AWS or any hosting provider for that matter, only Debian.

Also, can you confirm the other thing I asked too?

Yes as mentioned above Office hours and Backup occur at the wrong times.

 

[architechture]

I know you're trying to push everyone to Debian but I have zero experience with it. Switching all of my clients to that makes me very nervous.

 

[architechture]

Backup schedule for 2am runs at 8pm our time. Office hours go to Out of office at 11am our time, are set to 5pm.

 

[NickD_3CX]

About trying to push everyone to Debian, that was not exactly my intention, I said it mainly because we haven't tested Windows on Hosting Providers so I can't say for sure this is not the fault here.

OK, so all actions are delayed by the same amount of time. Can you check the Server time and the Timezone of the 3CX Server OS?
Not just that the time is correct, it also needs to be set to the same TZ that the 3CX Server expects to be in.

 

[architechture]

Server is set to UTC, 3CX is set to Central Time.

I have 10 3CX servers running in EC2 and have been for over 6 years. There's a test result for you.

 

[architechture]

Ok, so I made a dumb assumption. I assumed all of my instances were set to UTC. But they aren't they're set to Central Time. Duh sorry. I thought the purpose of having the timezone set in 3CX was to offset from UTC. So I guess I'm not sure what the purpose of that setting is...

 

[NickD_3CX]

I thought the purpose of having the timezone set in 3CX was to offset from UTC. So I guess I'm not sure what the purpose of that setting is...

On Debian, 3CX sets the TZ of the OS as well depending on what you select in the Management Console.
On Windows this isn't possible.
Other than that, it mainly affects IP Phone timezones settings.

Generally though I think we've found the culprit! Change the Windows TZ to match what is in 3CX and the TZ you're in and expect the Scheduled Tasks to trigger at and then make sure that the Windows Time is correct, then don't forget to restart all 3CX services because changing the time while services are running might make things go haywire until you do.