PFSense PHP time is incorrect in America/Sao_Paulo time zone

mcury

@cesarmsj Can you check if you are seeing one hour ahead or one hour earlier?
Unfortunately if I change now to answer Stephenw10, it will mess up my logs.
I don't know how to update tzdata manually..

cesarmsj

@mcury America/Sao_Paulo is one more hour.

mcury

@cesarmsj One hour ahead then.
Answering Stephenw10, yes it is showing GMT +2, which means 2 hours behind than GMT. America/Sao_Paulo should be GMT +3, which is 3 hours behind GMT.

cesarmsj

@mcury Why do they say it's GMT +3, I ask again, wouldn't it be GMT -3? See: https://greenwichmeantime.com/time-zone/south-america/brazil/time-brazil/

mcury

I understand, but they calculate like this:
GMT + X = LT

So, X is added to GMT to reach the desired LT.

Can you see the message after Etc/GMT +3 --> (3 hours behind GMT) ?

cesarmsj

@mcury
Our PFSense is in version: 2.4.5-RELEASE (amd64) built on Tue Mar 24 15:25:50 EDT 2020 FreeBSD 11.3-STABLE)

But anyway, will this be fixed in the next version to be released?

mcury

I'm not sure, as far as I'm aware, they didn't know about the summertime changes in Brazil.
2.5.0 is coming, maybe it will be fixed by then.

Change to GMT +3 for now, and it will fix it until a patch or a new version is released.

Same behavior on 2.4.5p1

2.4.5-RELEASE-p1 (arm)
built on Tue Jun 02 17:45:24 EDT 2020
FreeBSD 11.3-STABLE

stephenw10

It looks correct in 2.5 though:

Current date/time 	
Sun Nov 22 17:47:20 -03 2020

3hrs difference when I set Sao Paulo.

It's unlikely this will be corrected before 2.5 is released. I would just set GMT+3 until then.

Steve

cesarmsj

@stephenw10
Is it possible that PFSense 2.5 stable version will take time to be released? The fix may be included in private FreeBSD 12 updates.

Here are the links I've been reading, but we can't put this dev version into production until LTS is released:

https://www.netgate.com/blog/pfsense-2-5-0-development-snapshots-now-available.html

https://docs.netgate.com/pfsense/en/latest/releases/2-5-0.html

stephenw10

I'm not sure what you're asking there.

The next version of pfSense will be released when it's ready. You can follow the open issues here: https://redmine.pfsense.org/projects/pfsense/issues?query_id=106

Steve

johnpoz

@cesarmsj said in PFSense PHP time is incorrect in America/Sao_Paulo time zone:

into production until LTS is released:

Never seen a LTS version of pfsense ;) If that was what your asking.. Here is the lifecycle for hardware. Never seen anything like that for pfsense version. Normally the old version drops off support once its be replaced with new new version, they normally support the previous version. But not the one before that.

https://www.netgate.com/support/product-lifecycle.html

pfsense versions and if supported
https://docs.netgate.com/pfsense/en/latest/releases/versions.html

felipewnp

It is a reality for everyone in brazil. pfsense show the wrong time and we have to select a different timezone.

pfsense tzdata is badly outdated. That is the problem.

There is any way to update and keep updated pfsense tzdata package?

Cant a pkg update/upgrade tzdata be implemented to fetch an updated tzdata package?

A 2/3 year static tzdata doesnt work very well since it is vastly updated with changes arround the world.

My main question is just that, There is any way to update and keep updated pfsense tzdata package?

johnpoz

pfsense doesn't use a tzdata package that I can tell.. From this OLD bug

https://redmine.pfsense.org/issues/4459

It looks to be using the stock tzdata of whatever freebsd version they are using. If that is the case then moving to 2.5 will update that because it will be using new version of freebsd, vs the 11.3 version its using now.

cesarmsj

I found today that PHP is already with the correct time, even before we update to PFSense 2.5. With that, the conclusion I had is that certain packages of the FreeBSD system receive updates before the PFSense system itself, even because if I did not do this I would not receive updates from the repository to notify that there is a new update from it.

Problem solved. FreeBSD version 11.3-Stable.