Please wait while the update system initializes
-
lol fixed it i Turn off IPV6 all working now
-
Thanks. System -> Advanced -> Networking, unchecked IPv6, package installer now working.
-
This puzzled me for awhile. Installing any package or changing the update branch made the web interface stop responding, as well as ssh. In my case, routing continues as normal while the router is otherwise inaccessible.
System -> Advanced -> Networking -> Allow IPv6
Uncheck to block all IPv6 traffic, all symptoms disappear. It doesn't exist in the bug tracker as far as I can tell.
-
The solution, disabling IPv6, actually asks for a better solution : make IPv6 work.
I never had to disable IPv6 on my pfSense, even back in time when I had not any IPv6 support from my ISP. This ISP didn't t offer any IPv6 support back then, and they still don't do so today.
Updating, or package management on pfSense worked well.I decided to add IPv6 support using he.net.
No change, everything still works.
he.net fails ? Or I disable this IPv6-Only-WAN connection ? Still ok, all is well. -
Agreed. Having to disable functionality to make software stable is not a permanent solution. I really hope they fix ipv6 soon.
-
Any news on this topic? Still seems to be an issue on the latest version (2.4.5-RELEASE-p1)
-
@xparanoik Good question. I haven't been brave enough to try it again.
-
What is actually happening? Is the device getting a global IPv6 address, when there's no IPv6 provided? If it's only getting a link local address, it should cause this problem.
-
I actually already had IPv6 disabled this time around. In order to get the package installer GUI to work I had to run killall -9 pkg-static then pkg-static upgrade -f
-
So, you're saying it failed even with IPv6 disabled? If so, then it had nothing to do with the problem.
-
Not sure.
IPv6 can be shut down using a click.
The blocked pkg-static process would still be blocked and locked in memory.
For good order, a reboot would have done some good here. -
@xparanoik
thanks!
its workingkillall -9 pkg-static
then manually update install the packages from the package manager
-
@xparanoik - thanks, using killall -9 pkg-static in the shell meant that I didn't need to reboot after the 2.4.5 -> 2.4.5-RELEASE-p1 upgrade stopped me from being able to install package updates via Package Manager.
I think this is the top hit on DuckDuckGo so hopefully it will help others. Strange that it's seemingly been a problem for years.
-
@mikeroygbiv @LoZZoL glad that helped!
-
Confirmed on the latest version of pfsense: 2.4.5-RELEASE-p1 (arm64)
Rebooted pfsense
Tried: killall -9 pkg-static
Result: No matching processes were found
Manually installed package: openvpn-client...
Result: No change, still hangs on "lease wait while the update system initializes"Also, same failure, different pfsense install, just updating a different package, same result.
Gotta be a way to get this working.
-
@beedsley said in Please wait while the update system initializes:
Confirmed on the latest version of pfsense: 2.4.5-RELEASE-p1 (arm64)
Rebooted pfsense
Tried: killall -9 pkg-static
Result: No matching processes were found
Manually installed package: openvpn-client...
Result: No change, still hangs on "lease wait while the update system initializes"Also, same failure, different pfsense install, just updating a different package, same result.
Gotta be a way to get this working.
You are NOT on the latest version of pfSense. That is now 2.5 as of this week, so you need to update to the 2.5 version. You cannot install any packages (nor update any existing packages) until you update pfSense. If you try and force it, you will likely break your firewall to the point a fresh install and configuration restore from a backup will be required.
-
@bmeeks Forced upgrades suck!
I am not going to beta test the new version right away, this is dumb. -
@beedsley said in Please wait while the update system initializes:
@bmeeks Forced upgrades suck!
I am not going to beta test the new version right away, this is dumb.It's not that pfSense is really trying to "force you" to upgrade. It's just that the package building system always builds on the latest pfSense version. It would be a lot of extra work to keep building packages for EOL versions of pfSense - not to mention the potential for leaving packages with security vulnerabilities still available for installation.
Packages have to be compiled against an underlying OS version with certain assumed shared library versions. Always compiling against the "current" pfSense version is the best way.
-
@bmeeks Got it all sorted and working.
Just needed to cycle the OS updates to develepment
Wait for it to load the catalog of packages for that version, then toggle back to:
"Previous stable version (2.4.5 DEPRECATED"
so the catolog of packages for the current OS could be loaded and available for install.
Then I could install packages for the 2.4.5 version WITHOUT upgrading the OS.Thankful!
-
@beedsley said in Please wait while the update system initializes:
@bmeeks Got it all sorted and working.
Just needed to cycle the OS updates to develepment
Wait for it to load the catalog of packages for that version, then toggle back to:
"Previous stable version (2.4.5 DEPRECATED"
so the catolog of packages for the current OS could be loaded and available for install.
Then I could install packages for the 2.4.5 version WITHOUT upgrading the OS.Thankful!
Yes, that works, but the firewall gets an update for a reason. Usually there are vulnerabilities that need patching. FreeBSD 11.3, which is what pfSense-2.4.5 is based on, went EOL (End-of-Life) in September 2020. Here is the schedule: https://www.freebsd.org/security/unsupported/. It's not a good idea to have your firewall running an EOL operating system. Doing so for a few days or even a couple of weeks is one thing, but leaving it on an older version for months is not wise.
