SG-1000: failed upgrade (maybe I was too impatient)
-
Yesterday I applied the upgrade from 2.4.5p1 to 21.02p1 on a SG-1000. I uninstalled the packages before and exported the config ... I was glad to have done that later:
I ran the upgrade from the CLI (menu point 13), it pulled ~160 tarballs, installed some time and then announced it would reboot. But the reboot didn't start (I pinged and the ping wasn't interrupted, I could ssh in again, and the box seemed idle and not doing anything).
So I waited a few minutes and then decided to re-run number 13 ... this wasn't so good, it lead to PHP errors and a somehow corrupted installation.
Right now I can't ssh in, the WebGUI shows an ugly PHP error and I am happy that at least the connectivity for the customer still is up. Today I plan to show up there with a prepared 2nd SG-1000 to swap / and maybe reflash their appliance to fix things quickly.
Could I have avoided this by waiting longer? Was I too impatient?
I want to understand that better, I have some other SG-1000 appliances out there, some at far away customers where I can't just drive by.
Thanks for any help on this.
If of any use: I can try things on the half-updated box in about 2hrs from now.
-
@sgw I had exactly the same thing happen to me. GUI would not start but the device functioned correctly.
I left it alone, ordered another SG-1100 and installed it, then reflashed the original one. So now I have a hot spare ready to go should I need it.
As far as not waiting long enough, mine (updated via the GUI) sat for a long time on waiting for the GUI to reload, which it never did. That's why I power cycled it. Would it eventually have come up? Don't know.
Anyhow, now I'm really gunshy about attempting another update, especially with all of the users reporting problems. I'm content to leave that green light flashing.