Upgrading from 2.3.2 -> 2.3.2-p1 issue - fetching packages times out
-
Last 3 upgrades actually been quite unimpressed with download/update speeds. Previous upgrade took over half and hour on 150Mbit line.
Ehhhh previous upgrade took longer to actually update then to download for me. On two 300 mbit lines and a 35 mbit line.
Doesn't reflect well on the product as naturally people assume that the network serving it out is using it itself and therefore it may be the cause of the slow speed… not reassuring by any means.
Or it could be the mirror it's being pulled from could be having issues. Having issues downloading a package doesn't make the product look bad, especially if it's a back end problem.
This type of issue definatley wouldn't sit well with a paid customer trying to update their device as its virtually non existent with any of the competitions hardware (firmware) updates.
Its scary to think if something as simple as the update wont work, how the rest of the code is actually checked.Jesus …. I guess haters gonna find a reason to hate. They do offer paid support, and if I was paying for support I'd probably have this issue resolved already. But I'm cheap, and I'm getting what I paid for right now. Which is fine with me, I can wait for the issue to be resolved.
Doesn't reflect well on the product as naturally people assume that the network serving it out is using it itself and therefore it may be the cause of the slow speed… not reassuring by any means.
Sigh. I didn't say it was… I clear state that people may assume that is the issue which doesn't help their sales in terms of paid model.
Not sure what you are trying to prove if not trolling but If you are going to quote a post quote the final version, note my final edit time is a full minute before what you quote here.
-
Sorry, I do apologize for assuming you are being thorough before you post.
We are now aware that its basically just slow speed on download servers.. just have to keep trying until it works.
-
I think we've gotten off the topic. I'm going to delete my previous unhelpful posts in a few minutes.
-
Just kept banging away on option 13, update finally went through. Yay :D
-
I ran into this problem when upgrading from 2.3.2 to 2.3.2_1 as well. I've never had a problem previously with an upgrade via the web UI before, but had to resort to the console for pfSense-upgrade. Even that took two tries to get through all of the packages.
As other reporters of these timeouts have noted, fetching the package manually from a host inside the firewall (e.g. via curl) works fine and in a reasonable d/l time. No problems on the pfSense host or internal hosts with DNS timeouts or other DNS (mis-)configuration issues. No CPU load, disk utilization or other such obvious stuff on the pfSense host. The WAN network appears to be performing swimmingly in both latency and bandwidth. In other words: no smoking guns.
EDIT: My web UI update attempts also consistently timed out on pfSense-base-2.3.2_1.txz. The first pfSense-console attempt got past that, but timed out on the perl package. The second pfSense-console update completed successfully.
-
First attempt from 2.3.2 to 2.3.2_P1 made it this far:
Fetching php56-5.6.26.txz: .......... done Fetching pfSense-rc-2.3.2_1.txz: . done Fetching pfSense-kernel-pfSense_wrap_vga-2.3.2_1.txz: .......... done Fetching pfSense-default-config-2.3.2_1.txz: . done Fetching pfSense-base-2.3.2_1.txz: .......... done Fetching pfSense-2.3.2_1.txz: . done Fetching perl5-5.20.3_15.txz: . done pkg: https://pkg.pfsense.org/pfSense_v2_3_2_i386-pfSense_v2_3_2/All/perl5-5.20.3_15.txz: Operation timed out >>> Locking package pfSense-kernel-pfSense_wrap_vga... done. *** Welcome to pfSense 2.3.2-RELEASE (i386 full-install) on pfSense ***Second attempt pick up where first left off. But the reboot in 10 seconds was more like 30+ seconds.
Then during extraction when booting up. Got a couple of these.
maketwhatis: not found maketwhatis: not found -
Just curious. IPv4 or IPv6?
-
-
So today I tried the update again.
The system downloaded all packages - Yeah!
But then:Number of packages to be upgraded: 41 [1/41] Upgrading perl5 from 5.20.3_13 to 5.20.3_15... [1/41] Extracting perl5-5.20.3_15: .. pkg: archive_read_next_header(): Damaged tar archive [1/41] Extracting perl5-5.20.3_15... done >>> Locking package pfSense-kernel-pfSense_wrap... done. pkg: open(/bin/sh): No such file or directory pkg: open(/bin/sh): No such file or directory pkg: Unable to determine ABI pkg: Cannot parse configuration file! pkg: open(/bin/sh): No such file or directory pkg: open(/bin/sh): No such file or directory pkg: Unable to determine ABI pkg: Cannot parse configuration file!That is worrying.
I had package corruption messages on that system as well when I wanted to upgrade from 2.3.1 to 2.3.2 and thought it might be a faulty flash card. So I flashed a new card, restored backup and had my version updated with that.
Now - I run into the same issue. Very unlikely that the next CF is also faulty. Must be something different. -
Seems like the pfsense package repositories are struggling with the load. Have you considered putting Cloudflare in front of it? It could cache all the packages for you and serve them from the global CDN.
