Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
-
For those with other unrelated issues like proxies/gateways, please start new threads. This thread is only for the specific style of issues stated in the original post, thanks.
-
I just edited a fix into the first post for people who ended up on 2.3.1 or otherwise have a message saying they're on a version newer than the release. Should fix it all up.
worked for me. you da man!!!
Worked for me too…
-
@marjohh:
I just edited a fix into the first post for people who ended up on 2.3.1 or otherwise have a message saying they're on a version newer than the release. Should fix it all up.
worked for me. you da man!!!
Worked for me too…
Worked for me as well… THANK YOU!
-
Hi all,
Just quick question… where if ntopng package gone? I cant see it in 'Available packages' tab. I did use it a lot and now I am stuck :/
-
Hi all,
Just quick question… where if ntopng package gone? I cant see it in 'Available packages' tab. I did use it a lot and now I am stuck :/
https://doc.pfsense.org/index.php/2.3_Removed_Packages
-
pfSense is booting, then packages will be reinstalled in the background. Do not make changes in the GUI until this is complete.I had this problem a while back with my nano system at home earlier this year. I'd suggest looking through your config.xml file and see it there are any duplicate sections, mine had two sections setting up the local DHCP server on different subnets and once I deleted the bad one everything worked fine.
-
I was on 2.3.1.xxxx and noticed this morning it was unable to check for updates and the packages section shows no packages installed. I went to diagnostics/command prompt and tried pkg upgrade -f and got:
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.
New version of pkg detected; it needs to be installed first.
The following 1 package(s) will be affected (of 0 checked):Installed packages to be UPGRADED:
pkg: 1.7.2 -> 1.7.2_1 [pfSense]2 MiB to be downloaded.
Proceed with this action? [y/N]:
How does one and the y/N question??? Is this even the answer to my problem?
-
I was on 2.3.1.xxxx and noticed this morning it was unable to check for updates and the packages section shows no packages installed. I went to diagnostics/command prompt and tried pkg upgrade -f and got:
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.
New version of pkg detected; it needs to be installed first.
The following 1 package(s) will be affected (of 0 checked):Installed packages to be UPGRADED:
pkg: 1.7.2 -> 1.7.2_1 [pfSense]2 MiB to be downloaded.
Proceed with this action? [y/N]:
How does one and the y/N question??? Is this even the answer to my problem?
'y' is OK there. But please read the original post of the thread, second section, last entry.
-
The problem is you can't answer Y or N in the web gui.
-
The problem is you can't answer Y or N in the web gui.
don't run it from the web gui. use the console.
-
The problem is you can't answer Y or N in the web gui.
The webGUI has already asked the user to confirm they want to upgrade (which incidentally it does (and kind of has to do) before the user can see the full list of bits and pieces that will be upgraded) and so any back-end script code that uses package commands to actually do the bits of the upgrade should use whatever parameter is needed to tell it "go ahead whatever happens, do not ask interactively for confirmation of anything".
I thought that had been sorted out already, but obviously not for this case of it doing some early update before the full-blown thing.
-
Awesome!
Many thanks for this sticky. Has solved the "updating' issue for me. Pfsense Base was missing. Thanks again.
-
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!
