RV update & reboot

  • 1
  • Question
  • Updated 3 years ago
  • Answered
To my understanding RV just issued an update 15.10.7.9312, which crashed our non-managed Chromebox. While it is not a problem I was a bit scared because it had some hard time getting back on track. My real concern is our managed devices still running RV 15.8.20.6847. Should I expect the same from them too? They are running Chrome *44.
Photo of Darius - PRODO.us

Darius - PRODO.us, Champion

  • 26,850 Points 20k badge 2x thumb
  • not cool

Posted 3 years ago

  • 1
Photo of Blake Freeman

Blake Freeman, Official Rep

  • 36,116 Points 20k badge 2x thumb
Darius,

Thanks for the report. We did release a fix for an escalated issue, but I don't think it should have caused a crash. Can you explain what you mean by "it had some hard time getting back on track"?

To more directly answer your question, a crash is NOTanticipated when we release an update to our player. We have seen some oddities when it comes to Chrome Applications, so this may just be another that we have to add to our list.
Photo of LUIS REYES

LUIS REYES

  • 1,016 Points 1k badge 2x thumb
Now I understand...so that is why I saw 35 minutes ago my 4 displays restarted at the same time?
(in my case no crash issues)
Photo of Darius - PRODO.us

Darius - PRODO.us, Champion

  • 26,850 Points 20k badge 2x thumb
Blake, because the player is right in front of me and on at all times I cannot miss all that fun stuff. It simply shut down. I tried to turn it back on and it did, but it was stuck in black screen. The player was on, display recognized the signal (blue light indicator; orange when there is no signal coming in). There were no logos, no splash, no boot up animations. I restarted it again and it slowly came back on alive.

You are right I should not anticipate crash whenever there was an update... it is just... it happened before a couple of times at the worst possible moment :) Oh well, we will see tomorrow.
Photo of Blake Freeman

Blake Freeman, Official Rep

  • 36,116 Points 20k badge 2x thumb
You should work for us!

If you're worried about an update at an inopportune time, or the players crashing and not coming back online after a reboot, you can initiate the update yourself by power cycling your Chromebox. Like Luis, I had no issue updating my personal Chromebox, I'd be interested to know what happens with your other units.
Photo of Darius - PRODO.us

Darius - PRODO.us, Champion

  • 26,850 Points 20k badge 2x thumb
Make me an offer!

On the serious note, you said: "You can initiate the update yourself by power cycling your Chromebox. " How exactly do I do this? I mean, how do I know there was an update, so I could manually restart my player before it got shut off?
Photo of Blake Freeman

Blake Freeman, Official Rep

  • 36,116 Points 20k badge 2x thumb
After looking at your companies, this actually looks like it could be attributable to the version of ChromeOS you are running. Luis, it looks like all of your boxes are on Chrome 44, whereas Darius, it looks like the one that crashed is on Chrome 45. I'm seeing similar results from other companies that are on Chrome 45.
Photo of Jose IQsystems

Jose IQsystems

  • 148 Points 100 badge 2x thumb
We had the same problem as Darius in some of our boxes. They crashed and started working after a while. The players are unmanaged Chromeboxes. How can i update by powercycling and avoid automatic updates?
Photo of Blake Freeman

Blake Freeman, Official Rep

  • 36,116 Points 20k badge 2x thumb
Jose,

Unfortunately you cannot version lock unmanaged Chromeboxes.
Photo of LUIS REYES

LUIS REYES

  • 1,016 Points 1k badge 2x thumb
Ok, thanks...so it seems at least for ASUS CHROMEBOXES the stable Os is 44, (also in my case remember th 45 caused the freezing issue and with 44 no more)
Photo of Blake Freeman

Blake Freeman, Official Rep

  • 36,116 Points 20k badge 2x thumb
Correct, stick with 44.
Photo of Darius - PRODO.us

Darius - PRODO.us, Champion

  • 26,850 Points 20k badge 2x thumb
I remember asking that question before, but is there a way to have RV posting in some place the current stable combination of Chrome OS and Rise Vision for different supported models. I know, I should stay 2 updates behind on Chrome OS, but after *47 has been issued, am I supposed to bump up our devices to *45?