Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
-
First to say … mypfsense box is 1200 km away and I have only access over the web frontend and not over a direct console.
As I got the issue that the update stopped somewhere in the middle, I rebooted the machine. Then the Frontend claimed to be on 2.3.2, but was still on 2.3.1.
I followed the instructions in the first post "Upgrade resulted in running 2.3.1 or the version claims to be newer", except that I used an additional -y parameter on commands who are asking Y/N.
pkg upgrade -f -y
Ran first into an "504 Gateway Time-out"if I repeat this .... it happens sometimes again and sometimes it does more and stops then there:
[4/131] Extracting python27-2.7.12: Child process pid=87727 terminated abnormally: KilledI can reproduce it …. now third time exactly this message (except logically the pid)
My knowledge about FreeBSD is very limited. On a linux I would try to completely uninstall the python package and install it again.
Is there a better approach?
How to force this uninstall / install?
Will the frontend still work if python is missing? Remember, I do not have a real console and the box is 1200km away from me (additionally all staff members over there are in holidays!)Sorry for asking probably beginner questions, but I need to be VERY sure, that the box will not fail completely, becasue email would be the only service what would not fail if my VPN fails .... everything else in the company would be down and currently all flights are overbooked here on our airoport, as I sit on a holiday island with my local office. With ship and car I would need more than a day to get there.
-
Are you running that from ssh or from the GUI? If you are trying to run that from the GUI, use SSH instead.
There was an issue yesterday morning (US time) with the update server but it was cleared up by the afternoon. Everything should be back to normal now.
If you're running that from the shell and it's still failing, that is a bit more confusing. I've hit a few random issues here and there when testing (while the server was having a problem, mostly) but I've not seen it die in that way.
The GUI can run without python (except, perhaps, for RRD graphs) if you need to force its removal, but it should be reinstalled automatically when you attempt to upgrade since it's a dependency of glib, which is a dependency of rrdtool
And use "pfSense-upgrade -d" to run the upgrade if you can.
-
I alsways used the frontend …. in future ssh only! Thanks for the hint.
pfSense-upgrade -d looked good in the beginnig. It told me something about second partition required, as I saw it on the other box.
Then .... connection dropped .... and never came back. :o
No response on any port. Neither https, nor ssh, nor the two OpenVPN ports.
So my box is completely crashed in Germany and I sit in Spain. >:(
On Monday I have somebody there into our building .... but she is a pure user .... if a hard reboot fails, I'll try a factory reset. The basic configuration until I get the box remotely will be an adventure in blind flight ....
May I ask to modify this upgrade procedure, please? If something is wrong with the server the upgrade should just do nothing. My boss is ...... pissed is the wrong word ... too weak .... can't tell it in english, but I guess you know. ;)
Thank you that you tried to help. I learned from this ..... NEVER do an upgrade if nobody is onsite.
-
If it mentioned a second partition, you must be on NanoBSD. I've not seen one of those yet fail in a way that would cause it to die like that because of software. We have seen some fail due to hardware (bad CF/disk, etc), but not from the upgrade procedure itself.
The NanoBSD update procedure is very safe. If there are problems it does not switch over to boot from the updated slice, and it won't even reboot. If it rebooted, it must have completed the upgrade procedure successfully.
FYI- NanoBSD is not going to be a part of pfSense 2.4, so it's even less likely to be a concern in the future.
-
Don't know if it warrants an update to the sticky or not, but I just ran into a scenario where the GUI was unable to check for updates on a 2.3 install.
Tried various suggestions via the sticky on both GUI and shell, managed to get my self to a point where the GUI couldn't determine the current version and the shell wouldn't attempt an update (don't remember the shell error - sorry).Searched out:http://doc.pfsense.org/index.php/UpgradeGuide and found a reference for older snapshots (which this one was possibly) needing "find / -type l -lname '/usr/pbi/*' -delete" to clear old symlinks.
Once done I was able to use the shell to work forward through errors, and with the sticky make the upgrade work.
I mention this only to try and reduce the searching needed to resolve upgrade issues for older systems without needing to do a full reinstall.
Might be worth adding the potential need to kill the symlinks into the sticky.
-
I've SSH'd into my pfsense box and tried to upgrade it from the console.
I've tried the auto option and install from URL (using the right one for my box) and keep getting an error because the SHA256's don't match.
Anyone any ideas what I'm doing wrong!?
TIA
-
I've SSH'd into my pfsense box and tried to upgrade it from the console.
I've tried the auto option and install from URL (using the right one for my box) and keep getting an error because the SHA256's don't match.
Anyone any ideas what I'm doing wrong!?
TIA
It sounds like you are attempting an upgrade scenario that is much different from this thread. Start a new thread with more specifics about your current setup and someone can assist there.
-
Just update a guess from me. My box is fully broken, reset to manufacurers setting failed.
I had nobody onsite there as I updated. The person who came onsite yesterday morning reported, that our server was down and our printer was down. This means we had an power outage. As I told her the time when I updated my pfsense, she reported that there had been a huge thunderstorm at this time of the day in this area. So probably system crashed becasue this power outage. It was probably just Murphys Law ….
What I learned now from this issue: Never do a remote upgrade of such an important system without checking the weather onsite!
-
Here is some information for one of the problems caused by a missing resolv.conf in the chroot during upgrade…
https://forum.pfsense.org/index.php?topic=117905.msg653100#msg653100
I have not seen it discussed before.
-
I've followed this post, and am experiencing the same issues, running nanobsd, i have 2.3.2-release
pkg info gives me this output
pfSense-2.3.2
pfSense-Status_Monitoring-1.4.4_2
pfSense-base-nanobsd-2.3.2
pfSense-default-config-serial-2.3.2
pfSense-kernel-pfSense_wrap-2.3.2
pfSense-rc-2.3.2
pfSense-repo-2.3.2
php56-pfSense-module-0.12pkg update -f gives me this output
Updating pfSense-core repository catalogue…
pkg: https://pkg.pfsense.org/pfSense_v2_3_2_i386-core/meta.txz: Internal Server Error
repository pfSense-core has no meta file, using default settings
pkg: https://pkg.pfsense.org/pfSense_v2_3_2_i386-core/packagesite.txz: Internal Server Error
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg: https://pkg.pfsense.org/pfSense_v2_3_2_i386-pfSense_v2_3_2/meta.txz: Internal Server Error
repository pfSense has no meta file, using default settings
pkg: https://pkg.pfsense.org/pfSense_v2_3_2_i386-pfSense_v2_3_2/packagesite.txz: Internal Server Error
Unable to update repository pfSenseI have verified that the connectivity is good, can access the net from clients on the box.
I have checked that all of the files mentioned do exist, and they match your output (With the exception of the version number)
Any ideas??? -
I've followed this post, and am experiencing the same issues, running nanobsd, i have 2.3.2-release
pkg info gives me this output
pfSense-2.3.2
pfSense-Status_Monitoring-1.4.4_2
pfSense-base-nanobsd-2.3.2
pfSense-default-config-serial-2.3.2
pfSense-kernel-pfSense_wrap-2.3.2
pfSense-rc-2.3.2
pfSense-repo-2.3.2
php56-pfSense-module-0.12pkg update -f gives me this output
Updating pfSense-core repository catalogue…
pkg: https://pkg.pfsense.org/pfSense_v2_3_2_i386-core/meta.txz: Internal Server Error
repository pfSense-core has no meta file, using default settings
pkg: https://pkg.pfsense.org/pfSense_v2_3_2_i386-core/packagesite.txz: Internal Server Error
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg: https://pkg.pfsense.org/pfSense_v2_3_2_i386-pfSense_v2_3_2/meta.txz: Internal Server Error
repository pfSense has no meta file, using default settings
pkg: https://pkg.pfsense.org/pfSense_v2_3_2_i386-pfSense_v2_3_2/packagesite.txz: Internal Server Error
Unable to update repository pfSenseI have verified that the connectivity is good, can access the net from clients on the box.
I have checked that all of the files mentioned do exist, and they match your output (With the exception of the version number)
Any ideas???See this message and the recent posts above it in the thread:
https://forum.pfsense.org/index.php?topic=119511.msg662743#msg662743
The issues with the package server should be resolved now. -
FYI- NanoBSD is not going to be a part of pfSense 2.4, so it's even less likely to be a concern in the future.
If you don't mind me asking, why is NanoBSD going away? Will 4GB CF cards still be supported?
-
FYI- NanoBSD is not going to be a part of pfSense 2.4, so it's even less likely to be a concern in the future.
If you don't mind me asking, why is NanoBSD going away? Will 4GB CF cards still be supported?
It's going away because it doesn't make sense to maintain it anymore. As hardware and media changes over time it makes less sense to operate the way it does.
We're looking into ways to accommodate headless systems without a working console, but there are very few such devices that are 64-bit. We're also looking into ways to in-place upgrade from NanoBSD to a full install.
CF will still work with a full install, as long as the hardware is 64-bit.
-
Unable to upgrade on the GUI of pfsense it gives me the following error:
pfSense-default-config: 2.3.3 -> 2.3.3_1 [pfSense-core]
pfSense-base: 2.3.3 -> 2.3.3_1 [pfSense-core]
pfSense: 2.3.3 -> 2.3.3_1 [pfSense]
curl: 7.52.1_1 -> 7.53.0 [pfSense]Number of packages to be upgraded: 7
41 MiB to be downloaded.
Fetching pfSense-kernel-pfSense-2.3.3_1.txz: …....... done
Fetching pfSense-default-config-2.3.3_1.txz: . done
Fetching pfSense-base-2.3.3_1.txz: . done
pkg: https://pkg.pfsense.org/pfSense_v2_3_3_amd64-core/All/pfSense-base-2.3.3_1.txz: Operation timed outLocking package pfSense-kernel-pfSense... done.
Failed -
pkg.pfsense.org doesnt even resolve here.
-
pkg.pfsense.org doesnt even resolve here.
You're doing it wrong.
https://forum.pfsense.org/index.php?topic=130708.msg719850#msg719850 -
After upgrade:
Version 2.3-RELEASE (amd64)
built on Mon Apr 11 18:28:29 CDT 2016
FreeBSD 10.3-RELEASEUnable to check for updates
–-----------------------------------------------------------------
pkg info -x pfSense
pfSense-2.3
pfSense-Status_Monitoring-1.0_1
pfSense-base-nanobsd-2.3
pfSense-default-config-serial-2.3
pfSense-kernel-pfSense-2.3
pfSense-pkg-AutoConfigBackup-1.43_1
pfSense-pkg-aws-wizard-0.5_1
pfSense-pkg-ipsec-profile-wizard-0.9_1
pfSense-pkg-openvpn-client-export-1.4.3
pfSense-rc-2.3
pfSense-repo-2.3
php56-pfSense-module-0.12pkg upgrade -f
Nothing happensrm /usr/local/etc/pkg/repos/pfSense.conf
rm: /usr/local/etc/pkg/repos/pfSense.conf: Read-only file systemfetch -qo /usr/local/share/pfSense/keys/pkg/trusted/ https://raw.githubusercontent.com/pfsense/pfsense/RELENG_2_3_0/src/usr/local/share/pfSense/keys/pkg/trusted/pkg.pfsense.org.20160406
fetch: /usr/local/share/pfSense/keys/pkg/trusted//pkg.pfsense.org.20160406: mkstemps(): Read-only file systemError: /usr/local/etc/pkg/repos/pfSense.conf: Read-only file system.
Error: /var/tmp/vi.recover/: Permission denied; Modifications not recoverable if the session failsLast here is present content of /usr/local/etc/pkg/repos/pfSense.conf
FreeBSD: { enabled: no }
pfSense-core: {
url: "pkg+http://firmware.netgate.com/pkg/pfSense_factory-v2_3_0_amd64-core",
mirror_type: "srv",
signature_type: "fingerprints",
fingerprints: "/usr/local/share/pfSense/keys/pkg"
enabled: yes
}pfSense: {
url: "pkg+http://firmware.netgate.com/pkg/pfSense_factory-v2_3_0_amd64-pfSense_factory-v2_3_0",
mirror_type: "srv",
signature_type: "fingerprints",
fingerprints: "/usr/local/share/pfSense/keys/pkg"
enabled: yes
}Simple question which step am I missing here?
-
@Rajko:
rm /usr/local/etc/pkg/repos/pfSense.conf
rm: /usr/local/etc/pkg/repos/pfSense.conf: Read-only file system
[…]
Simple question which step am I missing here?You have a filesystem problem which needs addressed. Failing to update is a symptom of some other problem you have, it's most likely not a problem with your updates.
Reboot into single user mode (option 2 at the boot menu IIRC) and then run "fsck -y /" repeatedly until it does not find any problems. Don't stop when it says the filesystem is clean, keep going until it finds no problems/makes no corrections. If that doesn't help, you might have a disk issue, or may need to reinstall. Start a new thread if you need more help with that since it isn't directly related to this thread.
-
Using admin username which isn't built-in admin behaves differently on pfsense.
Once I re-enabled "admin" account and logged to firewall via SSH console, I was able to complete update.
2 firewalls fixed with these steps so far.
File system was fine.
-
@Rajko:
Using admin username which isn't built-in admin behaves differently on pfsense.
Once I re-enabled "admin" account and logged to firewall via SSH console, I was able to complete update.
2 firewalls fixed with these steps so far.
File system was fine.
When you used a non-root/admin account, did you run the update via sudo?
I would expect it to fail without sudo from an unprivileged user. That also explains the errors.
