Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    PFSense PHP time is incorrect in America/Sao_Paulo time zone

    Scheduled Pinned Locked Moved General pfSense Questions
    23 Posts 5 Posters 2.1k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • cesarmsjC
      cesarmsj @mcury
      last edited by

      @mcury Very very strange, because the correct one would not be GMT -3?

      1 Reply Last reply Reply Quote 0
      • M
        mcury
        last edited by

        Yes, I guess the tzdata is not up to date.
        Remember that the new government changed how the summertime in Brazil works? It happened in 2019

        https://pt.wikipedia.org/wiki/Hor%C3%A1rio_de_ver%C3%A3o_no_Brasil#:~:text=No%20dia%2025%20de%20abril,vai%20aumentar%20produtividade%20do%20trabalhador.

        But this is only a guess, not sure if this is the problem indeed.

        dead on arrival, nowhere to be found.

        cesarmsjC 1 Reply Last reply Reply Quote 0
        • cesarmsjC
          cesarmsj @stephenw10
          last edited by

          @stephenw10 Is this an official repository? Why doesn't this updated package come with the latest version of pfsense? What would be the most correct process of updating pecl-timezonedb?

          1 Reply Last reply Reply Quote 0
          • cesarmsjC
            cesarmsj @mcury
            last edited by

            @mcury This is the problem, but I would like to know how to update tzdata correctly in pfsense.

            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              Yes, that is the pfSense repo and that is the 2.4.5 release branch. That is the version that's in 2.4.5p1.

              But I assume you are setting Sao Paulo directly and seeing GMT+2 instead?

              Steve

              1 Reply Last reply Reply Quote 0
              • cesarmsjC
                cesarmsj
                last edited by

                But the correct thing would be America/Sao_Paulo to be GMT -3

                M 1 Reply Last reply Reply Quote 0
                • M
                  mcury @cesarmsj
                  last edited by

                  @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..

                  dead on arrival, nowhere to be found.

                  cesarmsjC 1 Reply Last reply Reply Quote 0
                  • cesarmsjC
                    cesarmsj @mcury
                    last edited by

                    @mcury America/Sao_Paulo is one more hour.

                    M 1 Reply Last reply Reply Quote 0
                    • M
                      mcury @cesarmsj
                      last edited by

                      @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.

                      dead on arrival, nowhere to be found.

                      cesarmsjC 1 Reply Last reply Reply Quote 0
                      • cesarmsjC
                        cesarmsj @mcury
                        last edited by

                        @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/

                        1 Reply Last reply Reply Quote 0
                        • M
                          mcury
                          last edited by mcury

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

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

                          3a6f1518-6378-4050-a702-afba6ca1cccc-image.png

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

                          dead on arrival, nowhere to be found.

                          cesarmsjC 1 Reply Last reply Reply Quote 0
                          • cesarmsjC
                            cesarmsj @mcury
                            last edited by

                            @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?

                            1 Reply Last reply Reply Quote 0
                            • M
                              mcury
                              last edited by 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

                              dead on arrival, nowhere to be found.

                              1 Reply Last reply Reply Quote 0
                              • stephenw10S
                                stephenw10 Netgate Administrator
                                last edited by 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

                                cesarmsjC 1 Reply Last reply Reply Quote 1
                                • cesarmsjC
                                  cesarmsj @stephenw10
                                  last edited by

                                  @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

                                  johnpozJ 1 Reply Last reply Reply Quote 0
                                  • stephenw10S
                                    stephenw10 Netgate Administrator
                                    last edited by

                                    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

                                    1 Reply Last reply Reply Quote 0
                                    • johnpozJ
                                      johnpoz LAYER 8 Global Moderator @cesarmsj
                                      last edited by 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

                                      An intelligent man is sometimes forced to be drunk to spend time with his fools
                                      If you get confused: Listen to the Music Play
                                      Please don't Chat/PM me for help, unless mod related
                                      SG-4860 24.11 | Lab VMs 2.8, 24.11

                                      1 Reply Last reply Reply Quote 0
                                      • F
                                        felipewnp
                                        last edited by 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?

                                        johnpozJ 1 Reply Last reply Reply Quote 0
                                        • johnpozJ
                                          johnpoz LAYER 8 Global Moderator @felipewnp
                                          last edited by

                                          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.

                                          An intelligent man is sometimes forced to be drunk to spend time with his fools
                                          If you get confused: Listen to the Music Play
                                          Please don't Chat/PM me for help, unless mod related
                                          SG-4860 24.11 | Lab VMs 2.8, 24.11

                                          1 Reply Last reply Reply Quote 0
                                          • cesarmsjC
                                            cesarmsj
                                            last edited by

                                            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.

                                            1 Reply Last reply Reply Quote 1
                                            • F Fandangos referenced this topic on
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.