2.3.1_5 upgrade fails - timeout

kitdavis

Attempting to upgrade to 2.3.1_5 from 2.3.1_1 is consistently failing for me. I get partially through the process, but "Fetching pfSense-base-2.3.1_5.txz fails with a time out error. I have the same result from both the GUI and the Console. I have an abysmally slow connection but I can connect directly to pkg.pfsense.org, navigate to the appropriate directory and successfully download the file, albeit with wildly fluctuating speed. (It took about 20 minutes). It seems that the upgrade process has a timeout function that drops the connection after a set period? Is there an alternative upgrade process?

kitdavis

Screen shot of error

error.png_thumb

Blade Runner

I had similar experiences upgrading to 2.3.1_x from 2.2.4. Suggest review System Logs>System. There will be several NIC error messages.

5/27/2016

>>> 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 (5 candidates): ..... done
Processing candidates (5 candidates): ..... done
The following 5 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
	pfSense-rc: 2.3.1 -> 2.3.1_1 [pfSense-core]
	pfSense-kernel-pfSense: 2.3.1 -> 2.3.1_1 [pfSense-core]
	pfSense-default-config: 2.3.1 -> 2.3.1_1 [pfSense-core]
	pfSense-base: 2.3.1 -> 2.3.1_1 [pfSense-core]
	pfSense: 2.3.1 -> 2.3.1_1 [pfSense]

40 MiB to be downloaded.
Fetching pfSense-rc-2.3.1_1.txz: . done
Fetching pfSense-kernel-pfSense-2.3.1_1.txz: .......... done
Fetching pfSense-default-config-2.3.1_1.txz: . done
Fetching pfSense-base-2.3.1_1.txz: .. done
pkg: https://pkg.pfsense.org/pfSense_v2_3_1_amd64-core/All/pfSense-base-2.3.1_1.txz: Operation timed out
>>> Locking package pfSense-kernel-pfSense... done.
Failed

5/29/2016

>>> 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 (5 candidates): ..... done
Processing candidates (5 candidates): ..... done
The following 5 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
	pfSense-rc: 2.3.1 -> 2.3.1_1 [pfSense-core]
	pfSense-kernel-pfSense: 2.3.1 -> 2.3.1_1 [pfSense-core]
	pfSense-default-config: 2.3.1 -> 2.3.1_1 [pfSense-core]
	pfSense-base: 2.3.1 -> 2.3.1_1 [pfSense-core]
	pfSense: 2.3.1 -> 2.3.1_1 [pfSense]

25 MiB to be downloaded.
Fetching pfSense-base-2.3.1_1.txz: ....... done
pkg: https://pkg.pfsense.org/pfSense_v2_3_1_amd64-core/All/pfSense-base-2.3.1_1.txz: Operation timed out
>>> Locking package pfSense-kernel-pfSense... done.
Failed

I've narrowed it down to either unstable igb0 driver or incorrect PIA configuration. I don't know what changed yet igb0 has been unstable since 2.3.1_x.

My initial pfsense M/B was Supermicro X8SIA-F. I replaced the C2758F with the X8SIA-F, installed pfsense 2.2.4, and configured PIA. No issues upgrading to 2.3.1_x.

I have been checking this forum and searching error messages however issues seem to have been resolved with newer versions of FreeBSD, pfsense, and OpenVPN.

I prefer to use the C2758F yet continue looking for solution.

Hope this helps.

Derelict

I've narrowed it down to either unstable igb0 driver or incorrect PIA configuration. I don't know what changed yet igb0 has been unstable since 2.3.1_x.

Umm. No. If those are the two choices it's your PIA, bro. Turn it off, update, then turn it back on.

Blade Runner

@Derelict:

I've narrowed it down to either unstable igb0 driver or incorrect PIA configuration. I don't know what changed yet igb0 has been unstable since 2.3.1_x.

Umm. No. If those are the two choices it's your PIA, bro. Turn it off, update, then turn it back on.

I've installed pfsense on two M/Bs with igb0 NICs without PIA. Both are unstable.

Supermicro X10SLL-S has em0 and igb0 NIC. Initially assigned WAN to igb0 and LAN to em0. Issues. No update prompt.

Reassigned WAN to em0 and LAN to igb0. No issues. Update prompt within 10-15 seconds.

Capture_01.JPG_thumb

Capture_02.JPG_thumb

Capture_03.JPG_thumb

WAN_em0_LAN_igb0.JPG_thumb

Derelict

Zero to do with igb. That is practically guaranteed. Perhaps something to do with igb on that particular board. And 2.2.4? Really?

dnel

I am also getting this error, failing at the same point:

>>> 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.
**** WARNING ****
Duplicate slice required!!

Before starting the upgrade process, the currently mounted nanobsd partition
needs to be cloned to the secondary partition, where the update will happen

After installation a reboot will be required to switch partition.

>>> Cleaning secondary partition... done.
>>> Duplicating current slice... done.
>>> Restoring slice label... done.
>>> Testing duplicated partition integrity... done.
>>> Mounting second partition to run upgrade... done.
>>> Unlocking package pfSense-kernel-pfSense... done.
>>> Downloading upgrade packages... 
Updating pfSense-core repository catalogue...
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
Unable to update repository pfSense
All repositories are up-to-date.
Checking for upgrades (73 candidates): .......... done
Processing candidates (73 candidates): .......... done
The following 75 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
	uclcmd: 0.1 [pfSense]
	libucl: 0.8.0 [pfSense]

Installed packages to be UPGRADED:
	unbound: 1.5.5 -> 1.5.8 [pfSense]
	suricata: 3.0_1 -> 3.0_2 [pfSense]
	sqlite3: 3.9.2 -> 3.11.1 [pfSense]
	smartmontools: 6.4_1 -> 6.4_2 [pfSense]
	rate: 0.9 -> 0.9_1 [pfSense]
	python27: 2.7.11_1 -> 2.7.11_2 [pfSense]
	php56-zlib: 5.6.20 -> 5.6.22 [pfSense]
	php56-xmlwriter: 5.6.20 -> 5.6.22 [pfSense]
	php56-xmlreader: 5.6.20 -> 5.6.22 [pfSense]
	php56-xml: 5.6.20 -> 5.6.22 [pfSense]
	php56-tokenizer: 5.6.20 -> 5.6.22 [pfSense]
	php56-sysvshm: 5.6.20 -> 5.6.22 [pfSense]
	php56-sysvsem: 5.6.20 -> 5.6.22 [pfSense]
	php56-sysvmsg: 5.6.20 -> 5.6.22 [pfSense]
	php56-sqlite3: 5.6.20 -> 5.6.22 [pfSense]
	php56-sockets: 5.6.20 -> 5.6.22 [pfSense]
	php56-simplexml: 5.6.20 -> 5.6.22 [pfSense]
	php56-shmop: 5.6.20 -> 5.6.22 [pfSense]
	php56-session: 5.6.20 -> 5.6.22 [pfSense]
	php56-readline: 5.6.20 -> 5.6.22 [pfSense]
	php56-posix: 5.6.20 -> 5.6.22 [pfSense]
	php56-pdo_sqlite: 5.6.20 -> 5.6.22 [pfSense]
	php56-pdo: 5.6.20 -> 5.6.22 [pfSense]
	php56-pcntl: 5.6.20 -> 5.6.22 [pfSense]
	php56-openssl: 5.6.20 -> 5.6.22 [pfSense]
	php56-opcache: 5.6.20 -> 5.6.22 [pfSense]
	php56-mcrypt: 5.6.20 -> 5.6.22 [pfSense]
	php56-mbstring: 5.6.20 -> 5.6.22 [pfSense]
	php56-ldap: 5.6.20 -> 5.6.22 [pfSense]
	php56-json: 5.6.20 -> 5.6.22 [pfSense]
	php56-hash: 5.6.20 -> 5.6.22 [pfSense]
	php56-gettext: 5.6.20 -> 5.6.22 [pfSense]
	php56-filter: 5.6.20 -> 5.6.22 [pfSense]
	php56-dom: 5.6.20 -> 5.6.22 [pfSense]
	php56-curl: 5.6.20 -> 5.6.22 [pfSense]
	php56-ctype: 5.6.20 -> 5.6.22 [pfSense]
	php56-bz2: 5.6.20 -> 5.6.22 [pfSense]
	php56-bcmath: 5.6.20 -> 5.6.22 [pfSense]
	php56: 5.6.20 -> 5.6.22 [pfSense]
	pfSense-rc: 2.3 -> 2.3.1_5 [pfSense-core]
	pfSense-pkg-openvpn-client-export: 1.3.7_1 -> 1.3.8 [pfSense]
	pfSense-kernel-pfSense: 2.3 -> 2.3.1_5 [pfSense-core]
	pfSense-default-config-serial: 2.3 -> 2.3.1_5 [pfSense-core]
	pfSense-base-nanobsd: 2.3 -> 2.3.1_5 [pfSense-core]
	pfSense-Status_Monitoring: 1.0_1 -> 1.4.2_1 [pfSense]
	pfSense: 2.3_1 -> 2.3.1_5 [pfSense]
	perl5: 5.20.3_8 -> 5.20.3_12 [pfSense]
	pecl-zmq: 1.1.3 -> 1.1.3_1 [pfSense]
	p7zip: 15.09 -> 15.14 [pfSense]
	openvpn-client-export: 2.3.10 -> 2.3.11 [pfSense]
	openvpn: 2.3.9 -> 2.3.11 [pfSense]
	ntp: 4.2.8p7 -> 4.2.8p8 [pfSense]
	nss: 3.22.2 -> 3.23 [pfSense]
	nmap: 7.01 -> 7.12 [pfSense]
	nettle: 2.7.1 -> 3.2 [pfSense]
	mysql56-client: 5.6.27 -> 5.6.30 [pfSense]
	libzmq4: 4.1.3 -> 4.1.4_1 [pfSense]
	libsodium: 1.0.3 -> 1.0.8 [pfSense]
	libnet: 1.1.6_3,1 -> 1.1.6_4,1 [pfSense]
	libedit: 3.1.20150325_1 -> 3.1.20150325_2 [pfSense]
	jansson: 2.7_1 -> 2.7_2 [pfSense]
	gmp: 5.1.3_2 -> 5.1.3_3 [pfSense]
	glib: 2.44.1_3 -> 2.46.2 [pfSense]
	gettext-runtime: 0.19.6 -> 0.19.7 [pfSense]
	filterlog: 0.1_1 -> 0.1_2 [pfSense]
	expat: 2.1.0_3 -> 2.1.1_1 [pfSense]
	dnsmasq-devel: 2.76.0test8 -> 2.76.0test12 [pfSense]
	curl: 7.47.0 -> 7.48.0_1 [pfSense]
	cpdup: 1.17_2 -> 1.18 [pfSense]
	bsnmp-ucd: 0.4.1 -> 0.4.2 [pfSense]
	GeoIP: 1.6.6 -> 1.6.9 [pfSense]

Installed packages to be REINSTALLED:
	rrdtool-1.5.5_1 [pfSense] (options changed)
	nginx-1.8.1,2 [pfSense] (options changed)

The process will require 1 MiB more space.
91 MiB to be downloaded.
>>> Locking package pfSense-kernel-pfSense... done.
Failed

This is the embedded image of 2.3_1 upgrading to 2.3.1_5, although it failed upgrading to earlier patches too.

It runs in a bhyve VM with virtual nics.

RipNRun

Are you running gateway monitoring? I had this same behavior, disabled the gateway service, and it worked just fine. Re-enable it and I have the same problem….

dnel

@RipNRun:

Are you running gateway monitoring? I had this same behavior, disabled the gateway service, and it worked just fine. Re-enable it and I have the same problem….

I am, tried disabling it but the result is the same.

cmb

If nanobsd (at least one of them here is), it's probably this.
https://redmine.pfsense.org/issues/6557

Derelict

Can someone who is having this problem please try this:

Enable DNS Forwarder or DNS resolver and make sure it is listening on the localhost interface.

Try the upgrade again.

This command will have to return something meaningful for this temp fix to maybe work:

drill @127.0.0.1 pkg.pfsense.org

jamaican

Thank you. Adding my ISP DNS fixed the issue!

;D ;D ;D

MaxPF

@Derelict:

Can someone who is having this problem please try this:

Enable DNS Forwarder or DNS resolver and make sure it is listening on the localhost interface.

Try the upgrade again.

This command will have to return something meaningful for this temp fix to maybe work:

drill @127.0.0.1 pkg.pfsense.org

I had that issue yesterday until I enabled DNS resolver and set it to listen to localhost.
All good after that.

cmpufxr

I disabled the Gateway Monitoring Daemon and it worked for me.