I believe I’ve got a repeatable test case here. Thank goodness you had posted about the corrective acceptTOS URL, because I had a moment of panic.
C-7 running 2.2.6.134, hours after successful update from 2.2.6.133. This was not an update from 2.2.6.133 that caused the issue, but may give some insight where to look in your restart code.
TL;DR: soft reset seems broken in 2.2.6.134, causes loop with TOS screen rather than allowing restore from backup.
Fix:
http://hub.ip/hub/acceptTOS
When blank screen appears, then
http://hub.ip
then use restore from backup link at bottom of screen.
Background: I was noticing an explosion of Null Pointer Exception errors in the logs from a Rule that accessed an attribute that I had inadvertently deleted in a community driver I was modifying. That part is not important, just background.
So, I fixed the driver, did a backup (I’m OCD about making backups before and after any change), went to port 8081, did a soft reset, that worked but did not boot, just showed the initializing page without an xx% indicator, just the solid light blue line, message to “please wait”, I waited 1/2 hour, but the cows never came home. So, went to hub IP address, got the usual screen expected after soft reset finish. However, when clicking the link at bottom of page to restore from backup, instead got the screen wanting a TOS accept.
Hub was still accessible at port 8081. Was able to shut hub down cleanly, power down, power up, TOS problem still there. Was able to restore previous firmware version (2.2.6.133), several versions were available (I’ve got DB backups for everything, no devices added recently), but choosing 2.2.6.133 made that firmware restore, showed to be running 2.2.6.133, but stuck in TOS loop still. Used Diag tools to download latest version, successfully downloaded 2.2.6.134, but stuck in same accept TOS loop.
Then tried the URL posted above:
http://hub.IP/hub/acceptTOS
got blank screen, then went to
http://hub.IP
Got screen with link at bottom to restore backup (as usually happens after soft reset), clicked the link to restore from backup, and everything proceeded normally.
Hope this helps you find the issue, @gopher.ny
I’m back up and running.