Version 2.3.3_1 is available
-
Once again the GUI update worked but didn't quite show what was going on and there were misleading error messages. It outright flashed a "system update failed" message on the screen and only a part of the update log was shown in the log window, after the message that showed the system fetching a new kernel file there was nothing in the log window. The system rebooted on its own as expected and the update was successful in the end.
-
had an issue after upgrading to 2.3.3_1 my ospf is stuck on init state (showing from cisco neighbour)
-
hmmm - mine did all steps including 5/6 ok but has been sitting there saying "===> Removing static obsoleted files" for about an hour now. Came from 2.3.3.
How long did it take in your cases until reboot? Are there any steps after deletion of obsolete file other than the reboot? Should I reboot?
Previous updates went ok.
Thx!Edit - Syslog says:
Mar 10 09:32:33 pkg pfSense upgraded: 2.3.3 -> 2.3.3_1 Mar 10 09:32:33 pkg pfSense-base upgraded: 2.3.3 -> 2.3.3_1 Mar 10 09:32:31 kernel pid 25339 (rrdtool), uid 0: exited on signal 11 (core dumped) Mar 10 09:32:31 kernel pid 23384 (pfctl), uid 0: exited on signal 11 (core dumped) Mar 10 09:32:30 kernel pid 19421 (pfctl), uid 0: exited on signal 11 (core dumped) Mar 10 09:32:30 kernel pid 19614 (awk), uid 0: exited on signal 11 (core dumped) Mar 10 09:32:30 kernel pid 18899 (rrdtool), uid 0: exited on signal 11 Mar 10 09:32:30 kernel Failed to write core file for process rrdtool (error 14) Mar 10 09:32:17 pkg pfSense-default-config upgraded: 2.3.3 -> 2.3.3_1 Mar 10 09:32:17 pkg pfSense-rc upgraded: 2.3.3 -> 2.3.3_1 Mar 10 09:32:17 pkg pfSense-upgrade upgraded: 0.17 -> 0.20 Mar 10 09:32:17 pkg curl upgraded: 7.52.1_1 -> 7.53.0Edit - This is where I am on the upgrade page:
>>> Upgrading necessary 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 (7 candidates): ... pfSense-kernel-pfSense-2.3.3 is locked and may not be modified Checking for upgrades (7 candidates)...... done Processing candidates (7 candidates): ....... done The following 6 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pfSense-upgrade: 0.17 -> 0.20 [pfSense] pfSense-rc: 2.3.3 -> 2.3.3_1 [pfSense-core] 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: 6 26 MiB to be downloaded. Fetching pfSense-upgrade-0.20.txz: .. done Fetching pfSense-rc-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 Fetching pfSense-2.3.3_1.txz: . done Fetching curl-7.53.0.txz: .......... done Checking integrity... done (0 conflicting) [1/6] Upgrading curl from 7.52.1_1 to 7.53.0... [1/6] Extracting curl-7.53.0: .......... done [2/6] Upgrading pfSense-upgrade from 0.17 to 0.20... [2/6] Extracting pfSense-upgrade-0.20: .... done [3/6] Upgrading pfSense-rc from 2.3.3 to 2.3.3_1... [3/6] Extracting pfSense-rc-2.3.3_1: .... done [4/6] Upgrading pfSense-default-config from 2.3.3 to 2.3.3_1... [4/6] Extracting pfSense-default-config-2.3.3_1: .... done [5/6] Upgrading pfSense-base from 2.3.3 to 2.3.3_1... [5/6] Extracting pfSense-base-2.3.3_1: ..... done ===> Keeping a copy of current version mtree ===> Removing schg flag from base files ===> Extracting new base tarball ===> Removing static obsoleted files -
hmmm - mine did all steps including 5/6 ok but has been sitting there saying "===> Removing static obsoleted files" for about an hour now. Came from 2.3.3.
How long did it take in your cases until reboot? Are there any steps after deletion of obsolete file other than the reboot? Should I reboot?
Previous updates went ok.
Thx!(Nearly) the same for me. Coming from 2.3.3 the update is stuck at:
... [6/7] Extracting pfSense-base-2.3.3_1: ..... done ===> Keeping a copy of current version mtree ===> Removing schg flag from base files ===> Extracting new base tarballI don't dare to reboot the box :-\
-
@kpa:
Once again the GUI update worked but didn't quite show what was going on and there were misleading error messages. It outright flashed a "system update failed" message on the screen and only a part of the update log was shown in the log window, after the message that showed the system fetching a new kernel file there was nothing in the log window. The system rebooted on its own as expected and the update was successful in the end.
This was my experience as well. First time I've ever had an issue updating via the GUI. I actually closed the GUI after I got the error and updated via the console. After a couple tried because of download timeouts it went through and updated.
-
Mine just updated without issue via the gui.
-
It worked out fine here but half way through the GUI was not showing any progress. I could see the nics shutdown and start again so I closed the browser and logged in again to a good update.
-
I don't dare to reboot the box :-\
Replying to myself: took the risk, rebooted the box after more than 3 hours. Seems to work. Fingers crossed :P
-
I figured the system had logged me out already on the webui, when I logged back in the system reported the p1 status in the dashboard (without reboot). I then rebooted just as a matter of caution and it's back like normal.
Still weird. -
Update via GUI from 2.3.3 without a problem.
-
Updated from the GUI fine here as well:
Installed packages to be UPGRADED:
pfSense-kernel-pfSense: 2.3.3 -> 2.3.3_1 [pfSense-core]
pfSense-rc: 2.3.3 -> 2.3.3_1 [pfSense-core]Number of packages to be upgraded: 2
[1/2] Upgrading pfSense-rc from 2.3.3 to 2.3.3_1…
[1/2] Extracting pfSense-rc-2.3.3_1: …. done
[2/2] Upgrading pfSense-kernel-pfSense from 2.3.3 to 2.3.3_1…
[2/2] Extracting pfSense-kernel-pfSense-2.3.3_1: …....... done
===> Keeping a copy of current kernel in /boot/kernel.old
Upgrade is complete. Rebooting in 10 seconds.Locking package pfSense-kernel-pfSense... done.
Success -
Great - I know what it looks like when it's ok though and would be more interested to learn what went wrong…
-
Like I stated in my previous message,
Anyone know why the FreeBSD version is still p16 when the patch notes say it should be p17?
My system updated successfully as far as I know.
https://doc.pfsense.org/index.php/2.3.3-p1_New_Features_and_Changes
See attached for a screenshot of the GUI.
-
same here - and no idea, sorry
-
Seems that it is on 10.3 p17 if you check via the console cmd.
So I'd assume the versioning on the GUI wasn't changed?
See attached.
-
Yeah, looks like you're right. I have P16 on GUI but console cmd check says P17. It's not a bug, it's a feature :o
-
Yeah, looks like you're right. I have P16 on GUI but console cmd check says P17. It's not a bug, it's a feature :o
Shows P17 in the GUI here. Likely another symptom of the "package manager needs a brain transplant".
-
Now, can someone tell me what's this?
Configuring IPsec VPN... Mar 10 18:23:40 ipsec_starter[42810]: Starting weakSwan 5.5.1 IPsec [starter]... Mar 10 18:23:40 ipsec_starter[42810]: no netkey IPsec stack detected Mar 10 18:23:40 ipsec_starter[42810]: no KLIPS IPsec stack detected Mar 10 18:23:40 ipsec_starter[42810]: no known IPsec stack detected, ignoring! done Mar 10 18:23:41 ipsec_starter[43518]: charon (43621) started after 280 ms(IPsec does actually work, though seeing similar WTF in console output is not exactly what one would expect.)
-
If the GUI shows p16 something must be cached by your browser or maybe it never rebooted after the update.
The kernel version reported by uname wouldn't have anything to do with pkg, and should show the same anywhere.
@doktornotor that IPsec error is harmless, strongSwan whines about that on FreeBSD because that check is Linux-y. https://wiki.strongswan.org/projects/1/wiki/FreeBSD#Known-Problems
-
Had a successful update to 2.3.3_1 on my SG-4860, save one tiny glitch… reporting here for FYI purposes only, not a bitch.
all the ancillary packages packages restarted successfully this time too.My Dynamic DNS Status widget did show the cached IP not only as bad but had a : extension with an 8 digit port number.
Going into the service and punching "Save & Request Update" resolved even this small issue.
