OPNsense Forum
Archive => 16.1 Legacy Series => Topic started by: NUeB on June 06, 2016, 05:04:56 pm
-
After upgrading to 16.1.16 on my PC Engines apu1d4 the Dashboard is empty (Headliune + "add widget" is there only). Except for this all services seem to operate normal.
What information may I supply for bug–tracking?
-
We've had this on IRC just now too. It's a browser cache issue. Try with a different one, or close all windows of your current browser and reopen. :)
-
Yeah, or simply re-install favorite Apps in favorite layout, otherwise update went fine (via wifi as WAN :-D )
-
Re-started browser, tried a different one: Widgets are back, but now all in the right handed column (2 column layout); there has s'thing gone wrong (but no big deal).
-
Yeah, when you switch to 2 column, all are on the right column. I re-shuffled them, all back to normal... :-D
-
Same for me (I don't use the cache in FF) and it doesn't matter if I change to multiple columns (2 or more) they are all on the right hand side and single column correctly spreads right across the panel.
I also noticed that this update did not reboot my machine, I had to reboot manually.
-
The old code was position independent so they all go into one row initially. Rearranging them manually per column is less surprising in the long run. The automatic layout did not work very well so that was changed.
-
Ok, that makes sense. Thanks! :)
-
That was a minor hiccup. :)
About the system not rebooting. I got slightly carried away when I went to the console a moment ago, I hit option 12 in error (I think I was on autopilot) and it started to download a kernel update (the dashboard showed me as up-to-date when I hit the 'check' button) and this failed with this error:
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 (20 candidates): 100%
Processing candidates (20 candidates): 100%
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.1.16-amd64.txz: ...opnsense-verify: error:04091068:rsa routines:INT_RSA_VERIFY:bad signature
Signature is not validDoes that mean I had a failed update when I did this earlier?
-
Reboot was automagically in i386 nano!
-
Seems like an update for the kernel has fixed this. :)
-
Bill, yes, the firmware will not attempt to reboot if the kernel/base parts fail for whatever reason. Reasons in descending order of probability:
(a) You've selected a mirror that was not fully synced yet so the download failed.
(b) The download was corrupted and the signature check failed (either because the real file or the signature were bad)
(c) Someone is trying to push rogue updates that are not properly signed. ;)
Changing the mirror and/or simply rerunning from the console helps in those cases
-
Franco, thatnks for the explanation. The only problem is that doing the update through the UI doesn't throw any obvious error unless (I'm guessing) that you go to the progress page.
-
Errors in the GUI are the same as on the console with 16.1.16 onward. We previously missed them there as the file redirection would not catch stderr.
Not always helpful, but definitely better.
Fabian and me were briefly taking about the possibility of an upgrade log, but I'm not entirely sure how that could look like.. something you could view away from the console or progress page. Maybe you got thoughts about this? :)
-
Yes, an error log would be useful. I did look at the progress page while the update was running but, IIRC, I didn't see anything about the kernel problem on that page and it was a surprise when the system didn't reboot so I assumed it was OK. It was only in error that I did the update from the console and saw the error there.
Doesn't the package management system (or whatever you use for the updates) produce an error log as well as console output? When installing an update that requires a reboot is it not possible to query a failure and output a pop-up (at least) to mention a failed update? You can see here that I'm not a developer. :)
-
Package messages are pushed to the system log, but not all of them. I don't know about pkg's logic here. I will try to think of something as we should probably make a "report" of what to do next when the firmware upgrade didn't finish completely for one reason or another, like e.g.:
stage x of y failed, here's your error log!