2.3.1 to 2.3.2 Problems
-
Bump???
-
Hmm. That should be trying to download pfSense_v2_3_2_i386-core/All/pfSense-rc-2.3.2_1.txz not pfSense_v2_3_2_i386-core/All/pfSense-rc-2.3.2.txz
What exact version are you upgrading from?
-
2.3.1-RELEASE (i386)
built on Tue May 17 18:46:37 CDT 2016
FreeBSD 10.3-RELEASE-p3Version 2.3.2 is available.
-
What DNS servers do you have enabled? Is it DNSmasq (DNS
forwarder), or Unbound (DNS resolver)? -
Maybe drop to the shell and run:
pkg update -f
pfSense-upgrade -d
I don't think there will be any privacy issues in that output other than, perhaps, the shell prompt host name, if you could paste it here.
-
Enable DNS resolver
-
DiagnosticsCommand Prompt
Shell Output - pkg update -f
Updating pfSense-core repository catalogue…
Fetching meta.txz: . done
Fetching packagesite.txz: . done
Processing entries: .. done
pfSense-core repository update completed. 13 packages processed.
Updating pfSense repository catalogue...
Fetching meta.txz: . done
Fetching packagesite.txz: .......... done
Processing entries: .......... done
pfSense repository update completed. 405 packages processed. -
Shell Output - pfSense-upgrade -d
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...
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.
The following 1 package(s) will be affected (of 0 checked):Installed packages to be UPGRADED:
pfSense-repo: 2.3.2 -> 2.3.2_1 [pfSense-core]Number of packages to be upgraded: 1
2 KiB to be downloaded.
Fetching pfSense-repo-2.3.2_1.txz: . done
Checking integrity… done (0 conflicting)
[1/1] Upgrading pfSense-repo from 2.3.2 to 2.3.2_1…
[1/1] Extracting pfSense-repo-2.3.2_1: ….... 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 happenAfter installation a reboot will be required to switch partition.
Proceed with upgrade? (y/N) read: read error: Socket is not connected
Aborting... -
So what happened here??:
After installation a reboot will be required to switch partition.
Proceed with upgrade? (y/N) read: read error: Socket is not connected
Aborting…If that was ssh try from the console. It looks like it's been kicked to look for 2.3.2_1 at least.
NanoBSD….
-
For some reason it upgraded. Not sure what changed but all is well.
-
Good deal. Thanks.