Time set to UTC on mail queue

jordan2908

seems that the mail queue is stuck on UTC time, I have set my timezone on the system, check in php settings and set via web UI.

What is happening is, I reply to a ticket and it does not send until the UTC time of the queue crosses over with the system time.

I am on central time so if i reply to a ticket at 9am the reply will send at 2pm.

johnny

Hi @jordan2908 I believe you have to restart the server once you set the timezone or mariaDB will not update

jordan2908

johnny i have restart the server. I have tried restarting the mariadb server with --default-time-zone.

configured system time and host server time are all set to the correct time.

johnny

@jordan2908

How did you install ITFlow via script or manual?
What OS:

jordan2908

johnny

debian 12, with the script. but my timezone was set to UTC when I installed.

jordan2908

i confirmed php time is correct with

<?php
echo "The time is " . date("h:i:sa");
?>

johnny

I see although changing the timezone after will not affect existing records put into SQL when the timezone was UTC.

Send a new test mail from Settings > Mail

and see if the new email queue time is correct

jordan2908

Yes, I have been testing every time I change something, I figured it would not effects already queued emails. what table should I check in the database.

johnny

Hey @jordan2908 it almost sounds like MariaDB is holding onto UTC and ignoring your system time.

I'm going to install a new instance with Debian 12 using the script and see if I can reproduce.

Bigbug

johnny I think i have the same issue

as i didnt have the time to check it out… i'm just using UTC….

I'm also running Debian 12 with script installation

jordan2908

I was going to spin up a new VM and restore a backup to see what happens.

I wonder if it has something to do with lxc VM on proxmox

I went back to UTC for now.

johnny

@jordan2908 and @Bigbug Im starting to see the same behavior on my instance now as well, This started for me after a restart last night. I don't know if a PHP or MariaDB update caused this but im trying to figure this out as well.

We have not made any code modifications that would cause this either

johnny

Please Anyone else that is having this issue please report here, im going to pin this topic

Bigbug

Submit your vote

johnny

This deff appears to be a PHP datetime thing as PHP is not respecting my System Time and defaulting to UTC. I know this because I added a contact using PHPMyAdmin and the creation time that SQL generated using TIMESTAMP() on the created at field was correct.

Looking at the php.ini Configuration of my server I noticed this

It used to say eastern timezone. So it looks like PHP update reverted the config

but oddly enough not for my second instance.

So I think the solution would be to bring back setting PHP timezone upon login, this function was disabled long ago because PHP was taking the system timezone before and wasnt nessessary well now it looks like it is.

Stay tuned for a quick update

johnny

Pushed out a test fix.

We re-implemented setting the selected timezone in PHP as the new PHP version seem to not respect System Timezone anymore but revert to UTC. While SQL still uses System Timezone.

itflow-org/itflow2f4ddd8

Im not sure how this will affect with Cron need to test this further

Go ahead and update and let us know if this fixed the issue

This can easily be tested by using the test mail feature in settings > Mail and then checking the queued at time in Admin > Mail Queue to make sure the Time matches when you clicked send.

Bigbug

johnny Hey! it's fixed for me!

johnny

We pushed out another fix as well to set the timezone in the PHP CRONs as the php shell command was not respecting the system timezone either and reverting to UTC

itflow-org/itflow5266f12