Timezone issue

bdeguire

Hello all,

We're running v.1.18 and both our servers and MySQL are configured to America/Toronto. Also, all the configuration within OST is configured to America/Toronto.

However, when we create a ticket (either from email or manually within OST), we have GMT time displayed AND written in MySQL (which is 4 hours later).

Do you have any clues why GMT is taken as the time instead of the specified TZ?

Many thanks!

ramrajone

bdeguire
You can go to this post, it may help you out
https://howtohelpdesk.com/how-to-set-time-zone-in-osticket/

bdeguire

ramrajone

Hi Ramrajone,

Thanks for your answer. Did all of that, yet no improvement.

As you can see, everything points to America/Toronto (or New York, or Eastern, same TZ).

ramrajone

bdeguire
Just for the test, if you change the timezones to central, does your tickets reflect new time?

I assume you have restarted the Web server, if not try restarting the server

bdeguire

ramrajone

Restarted both PHP FPM and nginx, but same erroneous result.

KevinTheJedi

bdeguire

Your DB timezone should really be UTC. That way all dates and times are UTC and they can easily be converted to any timezone. When you use a specific timezone it eventually has issues especially during DST swaps and when you don’t regularly update your MySQL timezone tables and such.

Cheers.

bdeguire

KevinTheJedi

Indeed, MySQL needs to be in UTC. I think OST seems to query MySQL TZ variables and does something with them Having UTC at MySQL seems to do the trick. Thanks!

KevinTheJedi

bdeguire

Yes, we use MySQL timezones to convert values from frontend to DB time so they can be converted back later on.

Cheers.

bdeguire

KevinTheJedi

As a recommended setup check, it might be a good idea to add this check in the information panel. We see the DB timezone at the bottom, but a yellow "!" beside the TZ when it's not UTC might be a good check to add.

KevinTheJedi

bdeguire

Well it’s not always the case you need UTC so we can’t just put that warning. Some people have better setups that can work with a specific db timezone. It really all just depends on the setup. It’s more of a "If you have issues try UTC" kind of thing.

Cheers.