OPNsense Forum
Archive => 20.7 Legacy Series => Topic started by: Patrick M. Hausen on July 21, 2020, 04:53:19 pm
-
Hi all,
great to read the RC1 announcement. I am not quite sure if I can update from 20.1.8 to 20.7-RC1 via the UI. When I switch to the "Development" release type and check for updates I am offered "20.7.b_224" - is this identical with RC1 or do I really need to perform a fresh install?
Thanks!
Patrick
-
Update to latest 20.1.8, then go to console:
opnsense-update -t opnsense-devel
opnsense-code core
cd /usr/core && make upgrade
Then again to UI and check for updates to go to 20.7r1
After some reboots you'll see:
OPNsense 20.7.r_13-amd64
FreeBSD 12.1-RELEASE-p7-HBSD
OpenSSL 1.1.1g 21 Apr 2020
-
For anyone who's using a production system take care while proceeding with command line tools. It took quite some time to make the upgrades behave correctly and some things may not work manually as well as they should depending on the version installed, core.git state, etc.
With 20.1.9 the upgrade will be built into the development package. With 20.1.9_1 the upgrade will be available from the production package...
Cheers,
Franco
-
It's my home production system and I have plan B (Edgerouter X) and a plan C (Fritzbox) in case I break anything to the point I cannot quickly repair it.
So the update went pretty smooth, but a minor cosmetic (?) glitch in the update check form remains - see screenshot. Can I repair that or should I just wait for the next update?
Kind regards,
Patrick
-
Update to latest 20.1.8, then go to console:
opnsense-update -t opnsense-devel
opnsense-code core
cd /usr/core && make upgrade
Then again to UI and check for updates to go to 20.7r1
Can this be done remotely (SSH) or does this need to be done at the console?
-
Update to latest 20.1.8, then go to console:
opnsense-update -t opnsense-devel
opnsense-code core
cd /usr/core && make upgrade
Then again to UI and check for updates to go to 20.7r1
Can this be done remotely (SSH) or does this need to be done at the console?
SSH is ok.
Is this version compatible with Sensei?
-
Hi Patrick,
This is not a bug, it is for perpetual upgrade testing on the development side. It will disappear once 20.7 is out...
Cheers,
Franco
-
PS: Please wait for Sensei to give the go on the upgrade. Give them some opportunity to cope with all these changes. 8)
-
Jul 21 21:09:09 haanjdj kernel: pid 11476 (syslog-ng), jid 0, uid 0: exited on signal 11 (core dumped)
Jul 21 21:30:21 haanjdj kernel: pid 83045 (syslog-ng), jid 0, uid 0: exited on signal 11 (core dumped)
Syslog-ng dumps core. I don't have any remote logging configured.
-
syslog-ng core dump is the same as 20.1: during service stop it clashes against HBSD and crashes rather than exiting. Since 20.1 syslog-ng is becoming the core syslog daemon so it is even active in local scenarios. Documentation and GUI representation will change accordingly in the coming months.
Maybe the old syslogd/clog combo will be completely removed in a coming major release only leaving syslog-ng in there.
Cheers,
Franco
-
syslog-ng core dump is the same as 20.1: during service stop it clashes against HBSD and crashes rather than exiting. Since 20.1 syslog-ng is becoming the core syslog daemon so it is even active in local scenarios. Documentation and GUI representation will change accordingly in the coming months.
Hey Franco,
Has a bug report been filed in HardenedBSD's self-hosted git instance? I'd be happy to take a look at the issue, especially if reproduction steps can be provided.
-
To not make unnecessary fuzz no reports have been made to other places at the moment. We still need a reliable config trigger and ideally a debug binary which boils down to "more time" needed so that's something for after 20.7 to look at closely.
Cheers,
Franco