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

    some services show can't start

    Scheduled Pinned Locked Moved
    Plus 23.09 Development Snapshots (Retired)
    5
    131
    20.3k
    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.
    • johnpozJ
      johnpoz LAYER 8 Global Moderator @stephenw10
      last edited by

      @stephenw10 JFC Steve - you need these developers working on the latest and greatest to up their quality testing and make sure every possible thing works before you release the snapshots ;)

      hahaah

      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.03 | Lab VMs 2.7.2, 24.03

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

        Mmmm. We should have caught that one but.... that's what dev builds are for. 😉

        But in all seriousness we cannot possibly test every possible config and, especially for complex and unusual configs, we expect to see more bugs reported at each stage in the release.

        If you have such a config I encourage you take part in the release testing process to find those bugs as early s possible.

        Steve

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

          @stephenw10

          There are so many mistakes that I can’t even count them on two hands. Upgrading is not that easy.

          pfSense-upgrade -dy
ERROR: It was not possible to determine pkg remote version
>>> Updating repositories metadata...
Updating pfSense-core repository catalogue...
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
repository pfSense-core has no meta file, using default settings
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
repository pfSense has no meta file, using default settings
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
Unable to update repository pfSense
Error updating repositories!
ERROR: It was not possible to determine pfSense-upgrade remote version
ERROR: It was not possible to determine pfSense-upgrade remote version
>>> Upgrading pfSense-upgrade...
Updating pfSense-core repository catalogue...
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
repository pfSense-core has no meta file, using default settings
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
repository pfSense has no meta file, using default settings
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
Unable to update repository pfSense
Error updating repositories!
[23.09-BETA][admin@]/root: pkg update
Updating pfSense-core repository catalogue...
Fetching meta.conf: 100%    163 B   0.2kB/s    00:01
Fetching packagesite.pkg: 100%    2 KiB   1.6kB/s    00:01
Processing entries: 100%
pfSense-core repository update completed. 5 packages processed.
Updating pfSense repository catalogue...
Fetching meta.conf: 100%    163 B   0.2kB/s    00:01
Fetching packagesite.pkg: 100%  191 KiB  17.8kB/s    00:11
Processing entries: 100%
pfSense repository update completed. 727 packages processed.
All repositories are up to date.
          1 Reply Last reply Reply Quote 0
          • yon 0Y
            yon 0 @stephenw10
            last edited by

            @stephenw10

            I participate in a lot of software development tests and provide suggestions. pfsense is the one where I see the most errors, and the most important ones are a lot of errors that have a major impact. Other software test versions do not have major errors that make the system unusable.

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

              @johnpoz

              haha。。 The pfsense team is too conservative. Many of the software developments I have participated in are innovative technologies that do not exist today, and we have developed and created them ourselves. However, pfsense does not even dare to follow up and use them.

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

                That http header error is just extra noise, it's been removed from the latest package version.

                But it is a sign it could not fetch the file which is interesting since pkg update succeeds.

                Does it still fail if you run pfSense-repoc first?

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

                  @stephenw10

                  After entering this command, nothing happens.

                  
[23.09-BETA][admin@]/root: pfSense-repoc
[23.09-BETA][admin@]/root:
                  1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by

                    That's expected. Can it now upgrade?

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

                      @stephenw10

                      waiting for this long time

                      [23.09-BETA][admin@]/root: pfSense-upgrade -dy
ERROR: It was not possible to determine pkg remote version
>>> Updating repositories metadata...
Updating pfSense-core repository catalogue...
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
repository pfSense-core has no meta file, using default settings
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
repository pfSense has no meta file, using default settings
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
Unable to update repository pfSense
Error updating repositories!
ERROR: It was not possible to determine pfSense-upgrade remote version
ERROR: It was not possible to determine pfSense-upgrade remote version
>>> Upgrading pfSense-upgrade...
Updating pfSense-core repository catalogue...
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
repository pfSense-core has no meta file, using default settings
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
repository pfSense has no meta file, using default settings
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
Unable to update repository pfSense
Error updating repositories!
                      1 Reply Last reply Reply Quote 0
                      • stephenw10S
                        stephenw10 Netgate Administrator
                        last edited by

                        IIRC you previously had issues with IPv6 failing there. Try: pfSense-upgrade -d4

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

                          @stephenw10

                          [23.09-BETA][admin@]/root: pfSense-upgrade -d4
ERROR: It was not possible to determine pkg remote version
>>> Updating repositories metadata...
Updating pfSense-core repository catalogue...
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
repository pfSense-core has no meta file, using default settings
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
repository pfSense has no meta file, using default settings
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
Unable to update repository pfSense
Error updating repositories!
ERROR: It was not possible to determine pfSense-upgrade remote version
ERROR: It was not possible to determine pfSense-upgrade remote version
>>> Upgrading pfSense-upgrade...
Updating pfSense-core repository catalogue...
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
repository pfSense-core has no meta file, using default settings
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
repository pfSense has no meta file, using default settings
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
pkg-static: An error occured while fetching package
pkg-static: Impossible to get the value from Last-Modified HTTP header
Unable to update repository pfSense
Error updating repositories!
                          1 Reply Last reply Reply Quote 0
                          • stephenw10S
                            stephenw10 Netgate Administrator
                            last edited by

                            And I assume the same if you force v6?

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

                              @stephenw10

                              Oct 15 01:31:53 php_wg 53450 /usr/local/pkg/wireguard/includes/wg_service.inc: Configuration Change: (system): [pfSense-pkg-WireGuard] De-installed earlyshellcmd(s).
                              Oct 15 01:31:53 check_reload_status 507 Syncing firewall
                              Oct 15 01:31:53 php_wg 53450 /usr/local/pkg/wireguard/includes/wg_service.inc: Configuration Change: (system): [pfSense-pkg-WireGuard] Installed earlyshellcmd(s).
                              Oct 15 01:31:53 check_reload_status 507 Syncing firewall
                              Oct 15 01:31:54 php_wg 53450 /usr/local/pkg/wireguard/includes/wg_service.inc: Configuration Change: (system): [pfSense-pkg-WireGuard] De-installed interface group (WireGuard).
                              Oct 15 01:31:54 php_wg 53450 /usr/local/pkg/wireguard/includes/wg_service.inc: Configuration Change: (system): [pfSense-pkg-WireGuard] Installed interface group (WireGuard).
                              Oct 15 01:31:55 php_wg 53450 /usr/local/pkg/wireguard/includes/wg_service.inc: Configuration Change: (system): [pfSense-pkg-WireGuard] De-installed Unbound ACL group (WireGuard).
                              Oct 15 01:31:55 check_reload_status 507 Syncing firewall
                              Oct 15 01:31:55 php_wg 53450 /usr/local/pkg/wireguard/includes/wg_service.inc: Configuration Change: (system): [pfSense-pkg-WireGuard] Installed Unbound ACL group (WireGuard).
                              Oct 15 01:31:55 check_reload_status 507 Syncing firewall
                              Oct 15 01:31:56 php_wg 53450 /usr/local/pkg/wireguard/includes/wg_service.inc: Configuration Change: (system): [pfSense-pkg-WireGuard] Applied package default settings as necessary.

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

                                @stephenw10

                                I successfully upgraded once after restarting the system, but the problem remains the same. It can only succeed occasionally.

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

                                  Since frr8 requires that the fe80:: address must be configured, but pfsense appears to block such addresses

                                  Oct 15 01:31:57 kernel wg0: changing name to 'tun_wg0'
                                  Oct 15 01:31:57 php_wg 53450 /usr/local/pkg/wireguard/includes/wg_service.inc: The command '/sbin/ifconfig tun_wg0 inet6 'fe80::981f:60ff:fee9:56d3' -alias' returned exit code '1', the output was 'ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address'
                                  Oct 15 01:31:57 kernel tun_wg0: link state changed to UP
                                  Oct 15 01:31:58 kernel [fib_algo] inet6.0 (radix6_lockless#844) rebuild_fd_flm: switching algo to radix6

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

                                    my wireguard config connect to DTLS tunnle local forward to remote server, pfsense service seem can't allow this. but wiregaurd allow this, only pfsense limited it.

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

                                      pfsense frr bgp session incorrectly monitors the wiregaurd service status according to pfsense and interrupts the connection of frr bgp sessions. In fact, all wiregaurd and frr bgp can be connected normally. The biggest problem at present is a series of errors caused by pfsense. In other words, if there is no pfsense Error limits, everything works fine.

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

                                        The previous pfsense versions frr bgp will not interrupt bgp sessions due to the wiregaurd service status. I don’t know what code pfsense has changed.

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

                                          Does pkg update always succeed or did we just happen to see it succeed previously?

                                          Its very odd that pkg update succeeds and repoc succeeds but pfSense-upgrade fails. And that it fails with an error that implies it cannot find the file. pkg update clearly was able to find it. 🤔

                                          You should be seeing FRR 9 if you're on the latest beta build.

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

                                            @stephenw10

                                            pkg update is ok. pfSense-upgrade not normal work.

                                            i have using frr9. Since frr8- frr9 requires that the fe80:: address must be configured. so wiregaurd need add this fe80:: address.

                                            How do I now change Pfsense's limit on wiregaurd service status errors? And how to cancel frr bgp sessions to establish a connection based on the wireguard service status?

                                            The main problem now is that wiregaurd has connected to the tunnel normally, and pfsense mistakenly believes that wiregaurd is not working properly and stops the service. At the same time, frr bgp sessions also stop working.

                                            i am using the version

                                            23.09-BETA (amd64)
                                            built on Fri Oct 13 14:00:00 CST 2023
                                            FreeBSD 14.0-CURRENT

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post