Please wait while the update system initializes

Pringles · Aug 18, 2017, 7:08 PM

Package Installer is not working right

all am getting is this Please wait while the update system initializes

i had a look in sys logs all am getting is this

[code<174>Aug 18 20:00:48 pfsense.localdomain nginx: 10.0.0.28 - - [18/Aug/2017:20:00:48 +0100] "POST /pkg_mgr_install.php HTTP/1.1" 200 50 "https://10.0.0.1/pkg_mgr_install.php" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36" 10.0.0.1 18/08 20:00:52.630
<174>Aug 18 20:00:49 pfsense.localdomain nginx: 10.0.0.28 - - [18/Aug/2017:20:00:49 +0100] "POST /pkg_mgr_install.php HTTP/1.1" 200 50 "https://10.0.0.1/pkg_mgr_install.php" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36" 10.0.0.1 18/08 20:00:53.630
<174>Aug 18 20:00:50 pfsense.localdomain nginx: 10.0.0.28 - - [18/Aug/2017:20:00:50 +0100] "POST /pkg_mgr_install.php HTTP/1.1" 200 50 "https://10.0.0.1/pkg_mgr_install.php" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36" 10.0.0.1 18/08 20:00:54.630
<174>Aug 18 20:00:51 pfsense.localdomain nginx: 10.0.0.28 - - [18/Aug/2017:20:00:51 +0100] "POST /pkg_mgr_install.php HTTP/1.1" 200 50 "https://10.0.0.1/pkg_mgr_install.php" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36" 10.0.0.1 18/08 20:00:55.630
<174>Aug 18 20:00:52 pfsense.localdomain nginx: 10.0.0.28 - - [18/Aug/2017:20:00:52 +0100] "POST /pkg_mgr_install.php HTTP/1.1" 200 50 "https://10.0.0.1/pkg_mgr_install.php" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36" 10.0.0.1 18/08 20:00:56.630
<174>Aug 18 20:00:53 pfsense.localdomain nginx: 10.0.0.28 - - [18/Aug/2017:20:00:53 +0100] "POST /pkg_mgr_install.php HTTP/1.1" 200 50 "https://10.0.0.1/pkg_mgr_install.php" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36" 10.0.0.1 18/08 20:00:57.630
<174>Aug 18 20:00:54 pfsense.localdomain nginx: 10.0.0.28 - - [18/Aug/2017:20:00:54 +0100] "POST /pkg_mgr_install.php HTTP/1.1" 200 50 "https://10.0.0.1/pkg_mgr_install.php" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36" 10.0.0.1 18/08 20:00:58.630
<174>Aug 18 20:00:55 pfsense.localdomain nginx: 10.0.0.28 - - [18/Aug/2017:20:00:55 +0100] "POST /pkg_mgr_install.php HTTP/1.1" 200 50 "https://10.0.0.1/pkg_mgr_install.php" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36" 10.0.0.1 18/08 20:00:59.630
<174>Aug 18 20:00:56 pfsense.localdomain nginx: 10.0.0.28 - - [18/Aug/2017:20:00:56 +0100] "POST /pkg_mgr_install.php HTTP/1.1" 200 50 "https://10.0.0.1/pkg_mgr_install.php" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36" 10.0.0.1 18/08 20:01:00.630

Thanks Pringles.

Pringles · Aug 18, 2017, 10:20 PM

lol fixed it i Turn off IPV6 all working now

dlogan · Apr 19, 2018, 1:00 PM

Thanks. System -> Advanced -> Networking, unchecked IPv6, package installer now working.

mlcastillo · Aug 27, 2018, 2:11 AM

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.

Gertjan · Aug 27, 2018, 6:14 AM

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.

mlcastillo · Jul 30, 2020, 1:55 AM

Agreed. Having to disable functionality to make software stable is not a permanent solution. I really hope they fix ipv6 soon.

xparanoik · Jul 30, 2020, 1:55 AM

Any news on this topic? Still seems to be an issue on the latest version (2.4.5-RELEASE-p1)

mlcastillo · Jul 30, 2020, 1:59 AM

@xparanoik Good question. I haven't been brave enough to try it again.

JKnott · Jul 30, 2020, 10:47 AM

@xparanoik

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.

xparanoik · Jul 30, 2020, 12:01 PM

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

JKnott · Jul 30, 2020, 12:45 PM

@xparanoik

So, you're saying it failed even with IPv6 disabled? If so, then it had nothing to do with the problem.

Gertjan · Jul 30, 2020, 1:32 PM

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.

mikeroygbiv · Aug 6, 2020, 6:22 AM

@xparanoik
thanks!
its working

killall -9 pkg-static

then manually update install the packages from the package manager

LoZZoL · Nov 25, 2020, 5:03 PM

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

xparanoik · Nov 25, 2020, 5:18 PM

@mikeroygbiv @LoZZoL glad that helped!

beedsley · Feb 18, 2021, 8:27 PM

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.

bmeeks · Feb 18, 2021, 8:31 PM

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

beedsley · Feb 18, 2021, 8:42 PM

@bmeeks Forced upgrades suck!
I am not going to beta test the new version right away, this is dumb.

bmeeks · Feb 18, 2021, 9:06 PM

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

beedsley · Feb 18, 2021, 9:07 PM

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