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

    23.05.01 can't normal boot

    General pfSense Questions
    3
    8
    679
    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.
    • yon 0Y
      yon 0
      last edited by

      alt text

      i am upgrade from 23.05 to 23.05.01. it is installed frr. the 23.05.01 can't normal work.

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

        When are you seeing that? After the upgrade completes?

        Where are you seeing it? Any other errors shown in the system or routing logs?

        yon 0Y 1 Reply Last reply Reply Quote 0
        • yon 0Y
          yon 0 @stephenw10
          last edited by

          @stephenw10 said in 23.05.01 can't normal boot:

          When are you seeing that? After the upgrade completes?

          yes, it is After the upgrade completes.

          Where are you seeing it? Any other errors shown in the system or routing logs?

          PVE seeing it.
          system route log show:

          Jun 30 11:22:08 pf zebra[26085]: [EC 100663303] kernel_rtm: 2402:f800::/48: rtm_write() unexpectedly returned -4 for command RTM_DELETE
          Jun 30 11:22:08 pf zebra[26085]: [EC 100663303] kernel_rtm: 2402:f800::/40: rtm_write() unexpectedly returned -4 for command RTM_DELETE
          Jun 30 11:22:08 pf zebra[26085]: [EC 100663303] kernel_rtm: 2402:f800::/32: rtm_write() unexpectedly returned -4 for command RTM_DELETE
          Jun 30 11:22:08 pf zebra[26085]: [EC 100663303] kernel_rtm: 2402:f800:cf00::/48: rtm_write() unexpectedly returned -4 for command RTM_DELETE
          Jun 30 11:22:08 pf zebra[26085]: [EC 100663303] kernel_rtm: 2402:f800:cf00::/40: rtm_write() unexpectedly returned -4 for command RTM_DELETE
          Jun 30 11:22:08 pf zebra[26085]: [EC 100663303] kernel_rtm: 2402:f800:df00::/48: rtm_write() unexpectedly returned -4 for command RTM_DELETE
          Jun 30 11:22:08 pf zebra[26085]: [EC 100663303] kernel_rtm: 2402:f800:df00::/40: rtm_write() unexpectedly returned -4 for command RTM_DELETE
          Jun 30 11:22:08 pf zebra[26085]: [EC 100663303] kernel_rtm: 2402:f800:ef00::/48: rtm_write() unexpectedly returned -4 for command RTM_DELETE
          Jun 30 11:22:08 pf zebra[26085]: [EC 100663303] kernel_rtm: 2402:f800:ef00::/40: rtm_write() unexpectedly returned -4 for command RTM_DELETE
          Jun 30 11:22:08 pf zebra[26085]: [EC 100663303] kernel_rtm: 2402:f800:ff00::/48: rtm_write() unexpectedly returned -4 for command RTM_DELETE
          Jun 30 11:22:08 pf zebra[26085]: [EC 100663303] kernel_rtm: 2402:f800:ff00::/40: rtm_write() unexpectedly returned -4 for command RTM_DELETE
          Jun 30 11:22:08 pf zebra[26085]: [EC 100663303] kernel_rtm: 2402:f800:ffff::/48: rtm_write() unexpectedly returned -4 for command RTM_DELETE

          Jun 30 11:22:11 pf bgpd[56785]: %NOTIFICATION: sent to neighbor 2602:fed2:7023🅰:10 5/0 (Neighbor Events Error/Unspecific) 0 bytes
          Jun 30 11:22:25 pf zebra[26085]: [EC 100663303] kernel_rtm: 2001:df5:b00::/48: rtm_write() unexpectedly returned -4 for command RTM_DELETE
          Jun 30 11:22:25 pf zebra[26085]: [EC 100663303] kernel_rtm: 2001:df5:b00::/48: rtm_write() unexpectedly returned -2 for command RTM_ADD
          Jun 30 11:22:26 pf zebra[26085]: [EC 100663303] kernel_rtm: 2001:df5:b00::/48: rtm_write() unexpectedly returned -4 for command RTM_DELETE
          Jun 30 11:22:26 pf zebra[26085]: [EC 100663303] kernel_rtm: 2001:df5:b00::/48: rtm_write() unexpectedly returned -2 for command RTM_ADD
          Jun 30 11:22:38 pf bgpd[56785]: [EC 100663299] bgp_set_socket_ttl: Can't set MinTTL on peer (rtrid 0.0.0.0) socket, err = 45
          Jun 30 11:23:47 pf zebra[26085]: [EC 100663303] kernel_rtm: 2a03:ce80::/32: rtm_write() unexpectedly returned -2 for command RTM_ADD
          Jun 30 11:23:47 pf zebra[26085]: [EC 100663303] kernel_rtm: 2a03:ce80::/32: rtm_write() unexpectedly returned -4 for command RTM_DELETE
          Jun 30 11:23:47 pf zebra[26085]: [EC 100663303] kernel_rtm: 2a03:ce80::/32: rtm_write() unexpectedly returned -2 for command RTM_ADD
          Jun 30 11:23:47 pf zebra[26085]: [EC 100663303] kernel_rtm: 2a03:ce80::/32: rtm_write() unexpectedly returned -4 for command RTM_DELETE
          Jun 30 11:23:55 pf zebra[26085]: [EC 100663303] kernel_rtm: 2a10:ccc2:9d2d::/48: rtm_write() unexpectedly returned -2 for command RTM_ADD
          Jun 30 11:23:55 pf zebra[26085]: [EC 100663303] kernel_rtm: 2a10:ccc2:9d2d::/48: rtm_write() unexpectedly returned -4 for command RTM_DELETE
          Jun 30 11:23:57 pf zebra[26085]: [EC 100663303] kernel_rtm: 2a10:ccc2:9d4c::/48: rtm_write() unexpectedly returned -2 for command RTM_ADD
          Jun 30 11:23:58 pf zebra[26085]: [EC 100663303] kernel_rtm: 2a10:ccc2:9d4c::/48: rtm_write() unexpectedly returned -4 for command RTM_DELETE
          Jun 30 11:23:58 pf zebra[26085]: [EC 100663303] kernel_rtm: 2a10:ccc2:9d4c::/48: rtm_write() unexpectedly returned -2 for command RTM_ADD
          Jun 30 11:23:58 pf zebra[26085]: [EC 100663303] kernel_rtm: 2a10:ccc2:9d4c::/48: rtm_write() unexpectedly returned -4 for command RTM_DELETE
          Jun 30 11:23:58 pf zebra[26085]: [EC 100663303] kernel_rtm: 2a10:ccc2:9d4c::/48: rtm_write() unexpectedly returned -2 for command RTM_ADD
          Jun 30 11:23:58 pf zebra[26085]: [EC 100663303] kernel_rtm: 2a10:ccc2:9d4c::/48: rtm_write() unexpectedly returned -4 for command RTM_DELETE

          B 1 Reply Last reply Reply Quote 0
          • B
            bavcon22 @yon 0
            last edited by

            @yon-0 After Upgrade process the upgrade script asks for automatic reboot. Do you experience some sort of electrical interruption in phase of reboot?

            yon 0Y 1 Reply Last reply Reply Quote 0
            • yon 0Y
              yon 0 @bavcon22
              last edited by

              @bavcon22 said in 23.05.01 can't normal boot:

              After Upgrade process the upgrade script asks for automatic reboot. Do you experience some sort of electrical interruption in phase of reboot?

              no, This problem has actually existed for many years, and pfsense has never seriously solved the problem. I think it is related to frr routing and pfsense. This problem often occurs when frr gets a large number of routes.

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

                Ah, OK, this is not a regression in 23.05.1 then?

                Have you opened a bug report for this previously?

                yon 0Y 2 Replies Last reply Reply Quote 0
                • yon 0Y
                  yon 0 @stephenw10
                  last edited by yon 0

                  @stephenw10 Have you opened a bug report for this previously?

                  yes, I've filed many times and over the years, usually a bug report is filed and you guys close the bug report. When frr gets a large number of ipv6 routes, it often causes pfsense php to crash or webgui cannot be used normally. e.g. more than 1 million frr ipv6 routes. But I don't have this problem with frr on ubuntu, so I'm guessing there's something special about pfsense

                  https://redmine.pfsense.org/issues/12951
                  https://redmine.pfsense.org/issues/14526
                  https://redmine.pfsense.org/issues/12712
                  https://redmine.pfsense.org/issues/11364
                  https://redmine.pfsense.org/issues/9795

                  1 Reply Last reply Reply Quote 0
                  • yon 0Y
                    yon 0 @stephenw10
                    last edited by

                    @stephenw10 said in 23.05.01 can't normal boot:

                    23.05.1

                    The pf v23.05.1 version will have this problem when the system starts. Other pf versions do not have this problem when the system starts. For other pf versions, this problem will occur after the system has been running for a period of time

                    1 Reply Last reply Reply Quote 0
                    • First post
                      Last post
                    Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.