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

    pfsense 2.7.2 Never completes startup process

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    35 Posts 2 Posters 2.9k 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.
    • yon 0Y
      yon 0 @stephenw10
      last edited by

      @stephenw10 said in pfsense 2.7.2 Never completes startup process:

      Those messages are expected and not necessarily an error.

      Try entering 'ctl+t' there and see what it's waiting for.

      Steve

      ok. done.

      alt text

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

        Did you just switch to Kea for dhcp6?

        Does that output ever change?

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

          @stephenw10 said in pfsense 2.7.2 Never completes startup process:

          Did you just switch to Kea for dhcp6?

          Does that output ever change?

          I have been using Kea for a few months.

          alt text

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

            And the output of ctl+t doesn't change? It continues to wait for Kea?

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

              @stephenw10 said in pfsense 2.7.2 Never completes startup process:

              And the output of ctl+t doesn't change? It continues to wait for Kea?

              yes. It continues to wait for Kea, Many hours have passed..

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

                Hmm, that's odd. The dhcp6 process appears to have started correctly in the logs.

                What version did you upgrade from?

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

                  @stephenw10
                  I'm not sure which version I started with since this problem has been around for a long time. DHCP has been started

                  Last 500 DHCP Log Entries. (Maximum 500)
                  Feb 20 00:17:13 dhcp6c 44436 Sending Solicit
                  Feb 20 00:15:13 dhcp6c 44436 Sending Solicit
                  Feb 20 00:13:06 dhcp6c 44436 Sending Solicit
                  Feb 20 00:11:18 dhcp6c 44436 Sending Solicit
                  Feb 20 00:09:22 dhcp6c 44436 Sending Solicit
                  Feb 20 00:07:32 dhcp6c 44436 Sending Solicit
                  Feb 20 00:05:37 dhcp6c 44436 Sending Solicit
                  Feb 20 00:04:01 kea-dhcp4 63234 INFO [kea-dhcp4.leases.0x102f6d018900] DHCP4_LEASE_ALLOC [hwtype=1 0e:33:de:60 ], cid=[01:0e:33🇩🇪 ], tid=0x879c528d: lease 10.50.2.30 has been allocated for 7200 seconds
                  Feb 20 00:04:01 kea-dhcp4 63234 INFO [kea-dhcp4.dhcpsrv.0x102f6d018900] EVAL_RESULT Expression pool_lan_0 evaluated to 1
                  Feb 20 00:03:26 dhcp6c 44436 Sending Solicit
                  Feb 20 00:03:04 kea-dhcp4 63234 INFO [kea-dhcp4.leases.0x102f6d0ef000] DHCP4_LEASE_ALLOC [hwtype=1 78:62:56:9 ], cid=[01:78:62:56 ], tid=0x1c2e22c9: lease 10.50.2.32 has been allocated for 7200 seconds
                  Feb 20 00:03:04 kea-dhcp4 63234 INFO [kea-dhcp4.dhcpsrv.0x102f6d0ef000] EVAL_RESULT Expression pool_lan_0 evaluated to 1
                  Feb 20 00:03:04 kea-dhcp4 63234 INFO [kea-dhcp4.leases.0x102f6d0ef000] DHCP4_LEASE_ADVERT [hwtype=1 78:62:56: ], cid=[01:78:62: ], tid=0x1c2e22c9: lease 10.50.2.32 will be advertised
                  Feb 20 00:03:04 kea-dhcp4 63234 INFO [kea-dhcp4.dhcpsrv.0x102f6d0ef000] EVAL_RESULT Expression pool_lan_0 evaluated to 1
                  Feb 20 00:03:04 kea-dhcp4 63234 INFO [kea-dhcp4.leases.0x102f6d0ef000] DHCP4_INIT_REBOOT [hwtype=1 78:62:56: ], cid=[01:78:62:56: ], tid=0x639140b2: client is in INIT-REBOOT state and requests address 10.50.2.33
                  Feb 20 00:03:04 kea-dhcp4 63234 INFO [kea-dhcp4.dhcpsrv.0x102f6d0ef000] EVAL_RESULT Expression pool_lan_0 evaluated to 1
                  Feb 20 00:01:26 dhcp6c 44436 Sending Solicit
                  Feb 19 23:59:25 dhcp6c 44436 Sending Solicit
                  Feb 19 23:57:19 dhcp6c 44436 Sending Solicit
                  Feb 19 23:55:10 dhcp6c 44436 Sending Solicit
                  Feb 19 23:53:14 dhcp6c 44436 Sending Solicit
                  Feb 19 23:51:04 dhcp6c 44436 Sending Solicit
                  Feb 19 23:48:58 dhcp6c 44436 Sending Solicit
                  Feb 19 23:46:48 dhcp6c 44436 Sending Solicit
                  Feb 19 23:45:27 kea-dhcp4 63234 INFO [kea-dhcp4.leases.0x102f6d0ef000] DHCP4_LEASE_ALLOC [hwtype=1 ea:26:14:b8: ], cid=[01:ea:26:14:b ], tid=0xe49aba46: lease 10.50.2.31 has been allocated for 7200 seconds
                  Feb 19 23:45:27 kea-dhcp4 63234 INFO [kea-dhcp4.dhcpsrv.0x102f6d0ef000] EVAL_RESULT Expression pool_lan_0 evaluated to 1
                  Feb 19 23:45:27 kea-dhcp4 63234 INFO [kea-dhcp4.leases.0x102f6d0ef000] DHCP4_LEASE_ADVERT [hwtype=1 ea:26:14:b , cid=[01:ea:26:14:b ], tid=0xe49aba46: lease 10.50.2.31 will be advertised
                  Feb 19 23:45:27 kea-dhcp4 63234 INFO [kea-dhcp4.dhcpsrv.0x102f6d0ef000] EVAL_RESULT Expression pool_lan_0 evaluated to 1
                  Feb 19 23:44:47 dhcp6c 44436 Sending Solicit
                  Feb 19 23:42:43 dhcp6c 44436 Sending Solicit
                  Feb 19 23:40:46 dhcp6c 44436 Sending Solicit
                  Feb 19 23:38:53 dhcp6c 44436 Sending Solicit
                  Feb 19 23:37:00 dhcp6c 44436 Sending Solicit
                  Feb 19 23:35:01 dhcp6c 44436 Sending Solicit
                  Feb 19 23:32:56 dhcp6c 44436 Sending Solicit
                  Feb 19 23:30:54 dhcp6c 44436 Sending Solicit
                  Feb 19 23:29:04 dhcp6c 44436 Sending Solicit
                  Feb 19 23:27:10 dhcp6c 44436 Sending Solicit
                  Feb 19 23:25:09 dhcp6c 44436 Sending Solicit
                  Feb 19 23:23:19 dhcp6c 44436 Sending Solicit
                  Feb 19 23:21:24 kea-dhcp4 63234 INFO [kea-dhcp4.dhcpsrv.0x102f6d012000] DHCPSRV_MEMFILE_LFC_EXECUTE executing Lease File Cleanup using: /usr/local/sbin/kea-lfc -4 -x /var/lib/kea/dhcp4.leases.2 -i /var/lib/kea/dhcp4.leases.1 -o /var/lib/kea/dhcp4.leases.output -f /var/lib/kea/dhcp4.leases.completed -p /var/lib/kea/dhcp4.leases.pid -c ignored-path
                  Feb 19 23:21:24 kea-dhcp6 63307 INFO [kea-dhcp6.dhcpsrv.0x28a002212000] DHCPSRV_MEMFILE_LFC_EXECUTE executing Lease File Cleanup using: /usr/local/sbin/kea-lfc -6 -x /var/lib/kea/dhcp6.leases.2 -i /var/lib/kea/dhcp6.leases.1 -o /var/lib/kea/dhcp6.leases.output -f /var/lib/kea/dhcp6.leases.completed -p /var/lib/kea/dhcp6.leases.pid -c ignored-path
                  Feb 19 23:21:24 kea-dhcp6 63307 INFO [kea-dhcp6.dhcpsrv.0x28a002212000] DHCPSRV_MEMFILE_LFC_START starting Lease File Cleanup
                  Feb 19 23:21:24 kea-dhcp4 63234 INFO [kea-dhcp4.dhcpsrv.0x102f6d012000] DHCPSRV_MEMFILE_LFC_START starting Lease File Cleanup
                  Feb 19 23:21:12 dhcp6c 44436 Sending Solicit
                  Feb 19 23:19:18 dhcp6c 44436 Sending Solicit
                  Feb 19 23:17:20 dhcp6c 44436 Sending Solicit

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

                    Oh you were seeing the same issue in earlier versions?

                    How did you upgrade then if bootup never completes. You installed 2.7.2 clean and restore a config?

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

                      @stephenw10 said in pfsense 2.7.2 Never completes startup process:

                      Oh you were seeing the same issue in earlier versions?

                      How did you upgrade then if bootup never completes. You installed 2.7.2 clean and restore a config?

                      You installed 2.7.2 clean and restore a config?

                      yes. In fact, DHCP is working, but the pfsense startup interface is not completed.

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

                        Ah, Ok. Are you able to connect to the firewall at all then? SSH working?

                        Anything shown in the system log?

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

                          @stephenw10 said in pfsense 2.7.2 Never completes startup process:

                          Ah, Ok. Are you able to connect to the firewall at all then? SSH working?

                          Anything shown in the system log?

                          I just tried to delete all the "DHCPv6 Static Mappings" setting and restarted the pfsense system just now. The startup interface was completed.

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

                            @stephenw10 said in pfsense 2.7.2 Never completes startup process:

                            Ah, Ok. Are you able to connect to the firewall at all then? SSH working?

                            Anything shown in the system log?

                            The LAN ipv4 I mentioned before cannot be routed through the ISP WAN. I haven't found a solution to this problem yet. I have set up static routing to let a lot of ipv4 be routed through the ISP WAN. But it doesn't seem to work.

                            bdb48456-001d-406c-8430-e39013f86146-image.png

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

                              What do you have in the v6 static mappings? It seems like something Kea doesn't like.

                              If you switch back to ISC DHCPd does it allow those mappings again?

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

                                @stephenw10 said in pfsense 2.7.2 Never completes startup process:

                                What do you have in the v6 static mappings? It seems like something Kea doesn't like.

                                If you switch back to ISC DHCPd does it allow those mappings again?

                                ipv6 normal, ipv4 route not normal work.

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

                                  @yon-0 said in pfsense 2.7.2 Never completes startup process:

                                  ipv6 normal, ipv4 route not normal work.

                                  That's what happens if you switch back to ISC?

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

                                    @stephenw10 said in pfsense 2.7.2 Never completes startup process:

                                    @yon-0 said in pfsense 2.7.2 Never completes startup process:

                                    ipv6 normal, ipv4 route not normal work.

                                    That's what happens if you switch back to ISC?

                                    back to ISC DHCP, it ipv4 DHCP not work. Lan pc can't get dhcp ip.

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

                                      Hmm, but it was working before you switched to Kea?

                                      The service is running?

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

                                        @stephenw10 said in pfsense 2.7.2 Never completes startup process:

                                        Hmm, but it was working before you switched to Kea?

                                        The service is running?

                                        yes, kea is runing. but i setup Static routing like 117.32.0.0/13 to WAN, other ips via VPN. the LAN's can't route to 117.32.0.0/13 now.

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

                                          @yon-0 said in pfsense 2.7.2 Never completes startup process:

                                          @stephenw10 said in pfsense 2.7.2 Never completes startup process:

                                          @yon-0 said in pfsense 2.7.2 Never completes startup process:

That's what happens if you switch back to ISC?

                                          back to ISC DHCP, it ipv4 DHCP not work. Lan pc can't get dhcp ip.

                                          @yon-0 said in pfsense 2.7.2 Never completes startup process:

                                          yes, kea is runing.

                                          So.... not back to ISC?

                                          Static routes would be completely unrelated to DHCP though anyway.

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

                                            @stephenw10 said in pfsense 2.7.2 Never completes startup process:

                                            @yon-0 said in pfsense 2.7.2 Never completes startup process:

                                            @stephenw10 said in pfsense 2.7.2 Never completes startup process:

                                            @yon-0 said in pfsense 2.7.2 Never completes startup process:

That's what happens if you switch back to ISC?

                                            back to ISC DHCP, it ipv4 DHCP not work. Lan pc can't get dhcp ip.

                                            @yon-0 said in pfsense 2.7.2 Never completes startup process:

                                            yes, kea is runing.

                                            So.... not back to ISC?

                                            Static routes would be completely unrelated to DHCP though anyway.

                                            yes, now it can't back to ISC. I see that the ISC DHCP page has changed and is different from before.

                                            Static routes would be completely unrelated to DHCP though anyway.

                                            Yes, but this is an urgent problem that needs to be solved. I have tried various methods but cannot solve it.

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