Updating from 2.2.9.137 to 2.2.9.138, all four of my C-7's updated without a hitch.
But, all four C-5's went to blue light, and stayed there; after 15 minutes, I power cycled them, and they're all fine now.
Gave me a helluva scare, though. 
2 Likes
I had the same issue on two C5's. Instead of power cycling I rebooted them using the diagnostic tool.
1 Like
I came here to post because my C5 is doing the same thing right now.
I thought I had a similar issue, but I let my C-5 hub sit there for a while and it came back on its own (I did do a couple of refreshes). It did seem to take a bit longer than usual.
Mine stuck at 15% for a long time so I refreshed the page and I just get a connection refused error now. I can ping the hub though.
I had to reboot mine again…seems hub jvm not running
It did start on reboot
I used the diagnostic tool to reboot it and it seems to be running now.
The same seems to have happened to me. At first, the diagnostic tool was responding, but after waiting about an hour, I couldn't get to that either (or the admin interface). Going to try a pull of the power now.
EDIT: That worked. Hub had a blue LED. Also, this was technically an update from 2.2.9.134 (rarely-used test hub at this point!) to 2.2.9.138, in case that matters.
EDIT 2: Same thing happened on another C-5 I had (also on 2.2.9.134). On this one, I only waited a few minutes and was still able to get to the Diagnostic Tool to perform a reboot. Both did successfully upgrade, other than this issue.
Same here. My C-7 updated fine from 2.2.9.137 to 2.2.9.138, but my C-5 hung, never made it to the Initializing Hub screen. Waited over 10 min. Went to port 8081, noticed that hub said it was on 2.2.9.138, rebooted from Diag Tools menu, everything fine now.
I had to do this as well. both C5s. I thought the C7 had done it, but it did eventually come up, but it seemed longer than normal.
BTW I was coming up from .134. I had to rollback twice so I waited a bit before I updated this time
Yup. One C7 - no problem.
Two C5s got stuck - rebooted one via 8081 port and it was fine.
I rolled back the other C5 (didn’t know yet that just a reboot would work) and it came up then reapplied the update and it came up first time.
Can I reply here? 
I only have 3 hubs, wait 4 (1 in its box still)
2 Likes
Same here with c5, rebooted by 8081
Same issue here... all my hubs failed to reboot. 3 C5's and 1 C4 however I couldn't reboot from 8081 as I never got a mac login screen so had to do a hard reboot on all of them.
Happened to my C-5 as well.
Same with My C5. Went dead... also pretty worried but has rebooted fine after a power cycle @gopher.ny ... might want to investigate
So I wasn't the only one who got a sinking feeling when that happened. I usually just go down the line of my three hubs when I update. As soon as one completes the download I start the next.
I was sitting there staring at three windows and none would boot up, although the C7 did finally come up on it's own. I may have used a expletive or two, especially after the last two updates I did and then had to almost immediately rollback. I felt better after I was able to access the diagnostic page of the first hub. Was still worried until I had all three back up again.
Hotfix coming shortly
5 Likes
Same here.. 2 C5 and 2 C7. The C7 seem ok but the C5 are hanging.
