Bug #6925
closed
System Update Failed
0%
Description
Updating repositories metadata...
Updating pfSense-core repository catalogue...
pfSense-core repository is up-to-date.
Updating pfSense repository catalogue...
pfSense repository is up-to-date.
All repositories are up-to-date.
Unlocking package pfSense-kernel-pfSense... done.
Downloading upgrade packages...
Updating pfSense-core repository catalogue...
pfSense-core repository is up-to-date.
Updating pfSense repository catalogue...
pfSense repository is up-to-date.
All repositories are up-to-date.
Checking for upgrades (6 candidates): ...... done
Processing candidates (6 candidates): ...... done
The following 5 package(s) will be affected (of 0 checked):
Installed packages to be UPGRADED:
pfSense-rc: 2.4.0.b.20161111.1919 -> 2.4.0.b.20161112.2122 [pfSense-core]
pfSense-kernel-pfSense: 2.4.0.b.20161111.1919 -> 2.4.0.b.20161112.2122 [pfSense-core]
pfSense-default-config: 2.4.0.b.20161111.1919 -> 2.4.0.b.20161112.2122 [pfSense-core]
pfSense-base: 2.4.0.b.20161111.1919 -> 2.4.0.b.20161112.2122 [pfSense-core]
pfSense: 2.4.0.b.20161111.1402 -> 2.4.0.b.20161112.1555 [pfSense]
Number of packages to be upgraded: 5
91 MiB to be downloaded.
Fetching pfSense-kernel-pfSense-2.4.0.b.20161112.2122.txz: ... done
pkg: https://beta.pfsense.org/packages/pfSense_master_amd64-core/All/pfSense-kernel-pfSense-2.4.0.b.20161112.2122.txz: Operation timed out
Locking package pfSense-kernel-pfSense... done.
Failed
Updated by Kill Bill about 8 years ago
"Operation timed out" => when download fails, you cannot upgrade.
Updated by Jim Thompson about 8 years ago
- Category set to Upgrade
- Assignee set to Edson Bueno
Updated by Phillip Davis about 8 years ago
I am also getting this the last day or so. I thought it was related to moving back to Nepal and having slower internet.
Updated by Kill Bill about 8 years ago
Nah, Nepal is innocent -- the mirrors have been slow like molasses for some two days or so...
Updated by Edson Bueno about 8 years ago
I've already taken everyone off the network, but I can not update only timeout.
((>>> Updating repositories metadata...
Updating pfSense-core repository catalogue...
pfSense-core repository is up-to-date.
Updating pfSense repository catalogue...
pfSense repository is up-to-date.
All repositories are up-to-date.
Upgrading pfSense-repo... done.
Unlocking package pfSense-kernel-pfSense... done.
Downloading upgrade packages...
Updating pfSense-core repository catalogue...
pfSense-core repository is up-to-date.
Updating pfSense repository catalogue...
pfSense repository is up-to-date.
All repositories are up-to-date.
Checking for upgrades (6 candidates): ...... done
Processing candidates (6 candidates): ...... done
The following 5 package(s) will be affected (of 0 checked):
Installed packages to be UPGRADED:
pfSense-rc: 2.4.0.b.20161115.2159 -> 2.4.0.b.20161116.0701 [pfSense-core]
pfSense-kernel-pfSense: 2.4.0.b.20161115.2159 -> 2.4.0.b.20161116.0701 [pfSense-core]
pfSense-default-config: 2.4.0.b.20161115.2159 -> 2.4.0.b.20161116.0701 [pfSense-core]
pfSense-base: 2.4.0.b.20161115.2159 -> 2.4.0.b.20161116.0701 [pfSense-core]
pfSense: 2.4.0.b.20161115.2154 -> 2.4.0.b.20161116.0551 [pfSense]
Number of packages to be upgraded: 5
91 MiB to be downloaded.
Fetching pfSense-rc-2.4.0.b.20161116.0701.txz: . done
Fetching pfSense-kernel-pfSense-2.4.0.b.20161116.0701.txz: .. done
pkg: https://beta.pfsense.org/packages/pfSense_master_amd64-core/All/pfSense-kernel-pfSense-2.4.0.b.20161116.0701.txz: Operation timed out
Locking package pfSense-kernel-pfSense... done.
Failed
))
Updated by Edson Bueno about 8 years ago
I was able to update. But I had to take the cable out of the router and leave it to pfsense only. Very sensitive. lol. Thanks ...
Updated by Jim Pingle almost 8 years ago
- Status changed from Feedback to Resolved
Updated by Edson Bueno almost 8 years ago
Ok ... But I can only update by removing the network cable after midnight and plugging in only on it. But in my network I have, other systems. Archlinux, debian, alpinelinux and all update at any time.