OPNsense Forum
Archive => 16.7 Legacy Series => Topic started by: Zapp on July 28, 2016, 10:47:01 am
-
Hi!
I just upgraded to OPNsense 16.7 from 16.1.20 and all seams to have gone well except for the kernel part...
(Did upgrade with IE cause Chrome was not able to do it)
This is what showed up in the end of the log:
...
!!!!!!!!!!!!! ATTENTION !!!!!!!!!!!!!!!!!
! A kernel/base upgrade is in progress. !
! Please do not turn off the system. !
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Fetching kernel-16.7-amd64.txz: ..pgrep: Pidfile `/tmp/opnsense-fetch.pid.SSKwbd' is empty
.pgrep: Pidfile `/tmp/opnsense-fetch.pid.VNXHJf' is empty
opnsense-verify: Unable to open /var/cache/opnsense-update/28895/kernel-16.7-amd64.txz: No such file or directory
failed
***DONE***
So right now my system is up and the System Information widget on the dashboard shows:
Versions OPNsense 16.7-amd64
FreeBSD 10.2-RELEASE-p19
OpenSSL 1.0.2h 3 May 2016
Shouldn't that be "FreeBSD 10.3..." something????
Any suggestions?
/Jonas...
-
In this case you can finish the update using option 12) from the console.
I have a fix for this in 16.7.1[1].
Cheers,
Franco
[1] https://github.com/opnsense/update/commit/55bb3d9dcbc80031a0ef48934259d922d59e121e
-
In this case you can finish the update using option 12) from the console.
I have a fix for this in 16.7.1[1].
...
That's good news. :)
Only problem for me is that I run the FW headless in a remote place and will have a bit of a problem carry this out with console. Any chance of doing it via ssh or something?
/Jonas...
-
Hi Jonas,
SSH as root works too. You'll see the menu.
Cheers,
Franco
-
Yupp, that made the trick.
0) Logout 7) Ping host
1) Assign Interfaces 8) Shell
2) Set interface(s) IP address 9) pfTop
3) Reset the root password 10) Filter Logs
4) Reset to factory defaults 11) Restart web interface
5) Power off system 12) Upgrade from console
6) Reboot system 13) Restore a configuration
Enter an option: 12
This will automatically fetch all available updates, apply them,
and reboot if necessary. Proceed with this action? [y/N]: y
Updating OPNsense repository catalogue...
OPNsense repository is up-to-date.
All repositories are up-to-date.
Updating OPNsense repository catalogue...
OPNsense repository is up-to-date.
All repositories are up-to-date.
Checking for upgrades (16 candidates): .......... done
Processing candidates (16 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
Checking integrity... done (0 conflicting)
Nothing to do.
Nothing to do.
Restarting webConfigurator...done.
!!!!!!!!!!!!! ATTENTION !!!!!!!!!!!!!!!!!
! A kernel/base upgrade is in progress. !
! Please do not turn off the system. !
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Fetching kernel-16.7-amd64.txz: ..... done
Fetching base-16.7-amd64.txz: ..... done
Fetching base-16.7-amd64.obsolete: ..... done
[1/3] Installing kernel-16.7-amd64.txz...
[1/3] Extracting kernel-16.7-amd64.txz: ... done
[2/3] Installing base-16.7-amd64.txz...
[2/3] Extracting base-16.7-amd64.txz: ... done
[3/3] Installing base-16.7-amd64.obsolete...
[3/3] Extracting base-16.7-amd64.obsolete: ... done
Please reboot.
Stopping flowd.
Waiting for PIDS: 29198 29225.
Stopping flowd_aggregate...done
Stopping suricata.
Waiting for PIDS: 80514.
tar: Removing leading '/' from member names
flowd_aggregate not running? (check /var/run/flowd_aggregate.pid).
tar: Removing leading '/' from member names
tar: Removing leading '/' from member names
Shutdown NOW!
shutdown: [pid 11638]
*** FINAL System shutdown message from root@OPNsense.home ***
System going down IMMEDIATELY
System shutdown time has arrived
Came up/back with this
Versions OPNsense 16.7-amd64
FreeBSD 10.3-RELEASE-p5
OpenSSL 1.0.2h 3 May 2016
BIG Thanks!
/Jonas...
-
Anytime :)
-
I had similar problems on one of our two firewalls when upgrading from 16.1.20 to 16.7.0.
FreeBSD stayed at version 10.2.
I found this thread and tried to open a console.
But no matter how I tried to login all I got was "Access denied".
I addition I started to receive notification mails with the following content:
There were error(s) loading the rules: pfctl: DIOCADDRULE: Operation not supported by device - The line in question reads
Via the WEB Interface I did a reboot of the device.
At least that's what I thought I did. And it did not solve the problems.
Then suddenly I saw on the dashboard that the system was up for 107 days!!!
So there was no reboot at all. Not now and not after several of the earlier 16.1.x updates.
Now I tried to execute a "Power Off" via the WEB GUI.
Like the reboot it did not work.
As a last resort I performed a hard power off by pulling the plug.
Now after the restart I see FreeBSD 10.3 running.
I can log into the console again.
No more error messages, too.
So the root problem seemed to be the failing reboot.
No idea what could have caused it.
My two cents
Stefan
-
Stefan, is this a nano-type system?
-
Franco,
our systems are OPNsense A10 Quad Core SSD rack appliances by Deciso.
SKU: OPN20077R-EUPC3-S2YN
Stefan
-
Ok, thanks. We have only 1-2 reports of this happening in all of our major releases. Frankly I do not know where it hangs. I suspect that typing "reboot" should work, which would mean a larger component could hang (IPS, Proxy, Captive Portal, NetFlow), or it could be something far more subtle.
For now I'm happy that this could be resolved. I can only promise to keep an eye out on this one.
Cheers,
Franco