Package Manager / Install is incredibly slow on 6100 since updating to 23.05.1
-
Hi,
I recently replaced a NG3100 with a NG6100, which worked ok so far. Since the last update I have noticed, that the Package Manager takes ages to show packages. Installing or removing packages that used to take a minute or so, are now taking several minutes. Any ideas what could have caused this? Is this an effect of the latest FW?
Seems it is slow on my lab box (i5 / 16GB, bare metal) as well...Thanks
Frank -
Try installing a package at the command line and see where it's waiting. Or just any pkg command like:
pkg -d update -
@stephenw10 I ran into this issue today as well. It did go away a few hours later
-
Thanks for the tip. Nothing to update, so the command runs smoothly.
-
@michmoor
I can see this now on 3 different boxes (NG3100, NG6100 and a China Box with Pfsense +. All off them take an awful long time to load the packages repository (ranging from 30s to 3 minutes, independent of the box). I updated them already some time ago, still this did not change -
@zaphood said in Package Manager / Install is incredibly slow on 6100 since updating to 23.05.1:
(ranging from 30s to 3 minutes, independent of the box)
Could this be the "IPv6 announced to be present, but actually not working so it falls back to IPv4 after XX time" ?
See the Netgate pfSense manual (packahe / update issues) and a zillion examples here on the forum how to do a console or SSH base command where you can do the package requesting 'manually', and see if there is a time out for one of them.
And if the used host names resolved fine.
Etc. -
It could be.
If
pkg -d updateseems to wait butpkg -d4 updatecompletes quickly that's probably the issue. -
@Gertjan
Installed cron manually (pkg install pfSense-pkg-Cron), all fine and very fast via ssh.
Seems the effect is related to the Web UI.BTW: I have blocked all IPV6 traffic
-
Are you still seeing that? There was an issue with the backend load handling yesterday that is now resolved.
-
Just installed nut via Web UI to check, went super fast. Seems to me you are right, that this problem on the backend might have caused the package manager process to slow down that heavily.
Thanks to everyone for your help!
-
@stephenw10 Any idea if this issue came back today 8/30? I'm seeing this on at least one firewall (Netgate 3100), incredibly slow package manager loading times (including for already installed packages). Updating a package (system patches) also took like 10 minutes instead of the usual less than 1.
Rest of the GUI is super snappy, throughput is good, CPU isn't maxed, and RAM is below 50%; oh and DNS works super fast.
-
@planedrop Same issue here - really slow getting installed packages, or looking for system updates etc.
-
@planedrop said in Package Manager / Install is incredibly slow on 6100 since updating to 23.05.1:
Updating a package (system patches) also took like 10 minutes instead of the usual less than 1.
Check, for example these messages, and do the tests proposed.
-
Looks like a possible IPv6 issue. Easy to test by checking for pkg updates and specifying v4 at the CLI:
pkg-static -d4 update
If that returns quickly andpkg-static -d6 updatejust eventually timesout that's the problem.
You can workaround it, until it's resolved, by setting prefer IPv4 in Sys > Adv > Networking.Steve
-
@stephenw10 Yep ipv6 access is borked - IIRC this has happened before. Will set the prefer IPv4 switch - I assume that's just for pfsense's own use of DNS?
-
Yes, that's just for pfSense's own connections.
-
I also had this problem with Packet Manager on a pfSense 2.7 CE installation some weeks ago and Googled the issue without a solution, until I encountered the problem today on both a 8200MAX and a custom installed system and actually checked the forum and finally know the issue is related to IPv6.
My IPv6 connection is working just fine and I can ping Google/YouTube/etc. IPv6 addresses and load the websites no problem. It appears Netgate server IPv6 is down. Tried pinging www.pfsense.org and forum.netgate.com and they both resolve to IPv6 addresses but there was no response. IPv4 ping did get a response.
To make sure it's not just the pfSense website doesn't respond to PING requests, I actually tested on my laptop with IPv4 disabled, and neither site will load in web browser. Other IPv6 enabled sites are fine. I also tested on my phone's cellular data which has IPv6, and I'd have to wait several seconds before the site starts loading, so I'm assuming it was trying IPv6 first and then fell back to IPv4.
At least it's good to know the issue seems to be with Netgate's server and it's not my configuration error or file corruption or so. I'd rather keep IPv6 enabled so that websites can see me logging in with IPv6 address, but hopefully the issue will get resolved eventually.
-
Yes, it looks like a routing issue. It should be resolved shortly.
-
@stephenw10 Thanks for the help and the answers here, I concur ipv4 seems to be fine, good to know!
-
The Netgate servers' IPv6 connection is back up and looks like we're all good now. There was a new version of Snort on my 8200MAX and it updated super fast (which I tried earlier and kept getting stuck), and Package Manager is loading as it should, with IPv6 enabled on my WAN.
