Reboot not working sometimes

  • 2
  • Question
  • Updated 4 years ago
  • Answered
Has anyone else had intermittent issues with rebooting player from the Displays Tab?

Almost all of the time it works, but sometimes the player doesn't do anything. Then after I do a simply F5 refresh on the player, it receives the command and reboots as it should.

I can't pinpoint what the cause is yet, but maybe someone else can chime in?
Photo of Alex

Alex, Champion

  • 10,070 Points 10k badge 2x thumb

Posted 5 years ago

  • 2
Photo of Neal

Neal

  • 61,252 Points 50k badge 2x thumb
I haven't seen that one as of yet. Do you recall if the Display was reportedly offline when you tried to restart the Display?
Photo of Alex

Alex, Champion

  • 10,070 Points 10k badge 2x thumb
That's the funny thing, the display is online, sitting right next to me lol. I'll wait a few minutes to see if it happens. Then when I hit F5 on the appliance, the restart script immediately shows.

It's tough to figure out why though. It's happened on two appliances so far during my testing. But most don't have a problem. All Win7, all the same appliance model. Weird.
Photo of Neal

Neal

  • 61,252 Points 50k badge 2x thumb
Sorry, I meant whether the Displays page showed a green heart next to the Display, or whether it was red (or black).
Photo of Jason Maggard

Jason Maggard

  • 2,620 Points 2k badge 2x thumb
Could that just be a matter of the polling interval? When I first started using Rise, I was curious about the reboots as well, because they seemed to not work, then I just realized that it might take a minute or two for the reboot to happen.

I'm not sure on this, but I think the reboot command gets to the machine when the player goes out and polls for updates. Hence, hitting F5 causes the machine to poll again and reboot.
Photo of Neal

Neal

  • 61,252 Points 50k badge 2x thumb
Pretty much.

Similarly, if you have the Player network cable unplugged, and send the reboot/restart command. When you plug the cable back in, it will reboot/restart.

The command is sent, but for whatever reason the Player hasn't processed it (which was why I was asking if the Displays page indicated a red/black heart for the Display)
Photo of Alex

Alex, Champion

  • 10,070 Points 10k badge 2x thumb
I wonder if it could be the polling interval that James mentioned - Rise polls about every 15 minutes, right?

Green heart every time I've tried it too. I've refreshed my screen several times before sending the reboot command. It still shows green.

Next time I see it, I'll wait longer than 15 minutes and see if the command ever appears.
Photo of Dave

Dave

  • 2,836 Points 2k badge 2x thumb
Wondering if anything was every determined about this issue?  I have a number of displays running Linux Mint17 and very recently (within the last 2 months) they have all stopped responding to the "reboot computer" option. I can leave them running overnight after the reboot is sent, and the uptime is never reset.

Weird part is: they all continue to respond to a "restart player" without issue.

All are running without firewalls and all have a green heartbeat when the reboot/restart is sent.
Photo of Neal

Neal

  • 61,252 Points 50k badge 2x thumb
Hi Dave,

We never were able to replicate the situation of reboots not occurring.  Even this morning, I tried it successfully on my Displays.  Having said that, we haven't tested on Mint so its possible that the operating system may be playing a role in what you're seeing.

Thanks.
Photo of Dave

Dave

  • 2,836 Points 2k badge 2x thumb
Thanks Neal, 

The thing that is crazy about this issue is that we have been operating without issue for months like this. Then suddenly, no reboot-ability.
  • Our chromeboxes reboot
  • The windows display we have running the Rise Player chrome app restarts the app on a reboot request(I think that is the default behavior)
  • The Mint17 devices will not reboot but the "restart" works every time.
Is there a huge difference in the control flows between the restart option and a reboot?
(Edited)
Photo of Neal

Neal

  • 61,252 Points 50k badge 2x thumb
Restart Player will clear the Player's cache as part of the process - but will not reboot the operating system.  Reboot Computer will reboot the computer, but will not clear the Player's cache. The Chrome Apps will just restart the browser, and not reboot.

There may be some variances with Mint17 that prevent it from rebooting - I tried it with Ubuntu 14.04 and it rebooted within a minute of me pressing the button.
Photo of Eric S.

Eric S.

  • 7,412 Points 5k badge 2x thumb
I've had an issue recently with the commands taking 5+ minutes to get to the player. Not sure if there is a default, but I seem to remember it happening much faster before. Could just be false memories though!
Photo of Neal

Neal

  • 61,252 Points 50k badge 2x thumb
I've seen it take about a minute if I did a change just before that (say update a Presentation). I'm not surprised with that however, since if you make two Presentation updates in quick succession, the second one will be a minute after the first one - which is by design.
Photo of Dave

Dave

  • 886 Points 500 badge 2x thumb
More of this if it is helpful to anyone: Still an ongoing problem for us and perhaps for others as well.

I have reloaded a Lab player (identical hardware to the production players) to run Ubuntu 14.04.1 32bit. Open JDK JRE7 and latest at and RVplayer. All installed from a "fdisk" clean build so no remnants of anything else left on the drive.

Once configured, we immediately reproduced the "no response to reboot" issue. It continues. The new player (like the Mint17 players) still continues to "restart" without a problem. Good news, the problem is not unique to Mint17. Bad news, the problem is not unique to Mint17.

Though I may not know what I am looking for , the syslog reveals nothing abnormal. Below please find find the tail-f of the lab player RisePlayer.log
/home/player/rvplayer/RisePlayer.log

Nov 2 06:50:18.807 INFO: Server started (this is me doing a Power up)
Nov 2 10:16:18.819 INFO: Exec: [killall, chrome] (this is me doing a restart)
Nov 2 10:16:20.836 INFO: Exec: [bash, -c, '/home/player/rvplayer/chrome-linux/ch
rome' --kiosk --no-default-browser-check --noerrdialogs --no-message-box --disab
le-desktop-notifications --allow-running-insecure-content --always-authorize-plu
gins --allow-outdated-plugins --user-data-dir='/home/player/.config/rvplayer' --
disk-cache-dir='/home/player/.cache/rvplayer' --ppapi-flash-path='/home/player/r
vplayer/chrome-linux/libflashplayer.so' 'http://rvashow.appspot.com/Viewer.html?
type=display&player=true&id=D9JRDY5ERM7Y&claimId=&sysinfo=os%3Dlnx%26iv%3D2.2.00
29%26pv%3D2.0.035%26ev%3D1.0.008' > '/home/player/rvplayer/chromium.log' 2>&1]

Nov 2 10:17:21.766 INFO: reboot_required received (this is me sending a reboot request)
Nov 2 10:17:21.768 INFO: Exec: [bash, -c, dbus-send --system --print-reply --des
t=org.freedesktop.ConsoleKit /org/freedesktop/ConsoleKit/Manager org.freedesktop
.ConsoleKit.Manager.Restart]

(and then: this is nothing happening after sending a restart)


Screen capture of presentation running through multiple reboot requests. This capture was taken from one of the production Mint17 devices. Log tails from the lab unit is identical.

As always, any advice would be greatly appreciated.
 
(Edited)
Photo of Neal

Neal

  • 61,252 Points 50k badge 2x thumb
With Ubuntu 14.04, there was a change done with its reboot command, It is different than the one for 13.10 and earlier operating systems.

For the time being, the reboot button won't perform an action on Ubuntu 14.04.  We'll let everybody know when that changes.

Thanks.
Photo of FAC Signage

FAC Signage

  • 732 Points 500 badge 2x thumb
See also this thread 

I think it may just be a matter of the Rise Vision folks testing the new command for 14.04 and then releasing an rvplayer update with it.