Rise Player on Ubuntu Crashing? Use this script to automatically re-launch Rise Player.

  • 2
  • Announcement
  • Updated 1 year ago
  • (Edited)
Archived and Closed

This conversation is no longer open for comments or replies and is no longer visible to community members.

Recently, we have seen some users experiencing that Rise Player closes or crashes and does not automatically re-launch. Our technicians have written a script that will automatically re-launch Rise Player if closed. We have included all needed steps to get this watchdog script set up on your local media player. We would very very interested to know of any successes or questions our users may have regarding this script. Please let us know if you notice any problems.
  • Open a Terminal window
  • Type gedit /home/rise/rise_player_watchdog.sh
  • Paste the following into the new document

#!/bin/bash
CHROME_PS_CHECK=`ps ax | grep chrome | grep app-id=mfpgpdablffhbfofnhlpgmokokbahooi
if [ -z "$CHROME_PS_CHECK" ]; then       #if chrome is not running, then launch it
   echo "Chrome/Player crashed.  Restarted:  `date`" >> /home/rise/player_restarted.log
   export DISPLAY=":0"
   # an assumption was made about the profile directory. if player doesn't start correctly, replace the following
   # line with the one in the desktop shortcut properties (and append      &>/dev/null &     like you see below)
   /opt/google/chrome/chrome \"--profile-directory=Profile 1\" --app-id=mfpgpdablffhbfofnhlpgmokokbahooi &>/dev/null &
fi
  • Save and Exit
  • In terminal, type chmod +x /home/rise/rise_player_watchdog.sh
  • In terminal, type crontab -e
  • If prompted, press for the default editor
  • Use the arrow keys on your keyboard to scroll to the bottom of this document
  • Copy/paste the following two lines
* * * * * /home/rise/rise_player_watchdog.sh
15 01 01 */3 * rm -f /home/rise/player_restarted.log 2> /dev/null
  • Press Control + X to exit the document
  • Press Y  to save the buffer
  • Press Enter to use the file name already specified
  • Wait up to 60 seconds. If the player does not start, the launch string will need to be changed
  • The following steps are only needed if the player does not automatically start.
  • Right click the desktop icon for Rise Player and select Properties
  • Highlight the entire Command line and copy the text
  • In terminal, type gedit /home/rise/rise_player_watchdog.sh
  • Replace the line beginning with/opt/google/chrome/chrome with the text copied from the shortcut.
  • Save and exit

Photo of Blake Freeman

Blake Freeman, Official Rep

  • 36,116 Points 20k badge 2x thumb

Posted 3 years ago

  • 2
Photo of Nick Goddard

Nick Goddard

  • 70 Points

Have been testing rise vision with windows 7 for a while. We have some old video wall monitors with built in embedded xp so decided to try rise vision using Ubuntu installed on a usb. I am using chrome but also have chromium installed. The Monitors in question are not the best hardware but run Ubuntu with occasional freezing fine. I can get the screen to start on boot but as soon as I change anything in presentations or schedules it crashes but does not restart. Also the restart player or computer options does not work at all.

Photo of Blake Freeman

Blake Freeman, Official Rep

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

Are you using an image of Ubuntu booting directly from a USB drive, or did you install Ubuntu on the computer itself?
Photo of Nick Goddard

Nick Goddard

  • 70 Points

Ubuntu is installed on the usb itself and isn't acting like a livecd or installation media.

Photo of Blake Freeman

Blake Freeman, Official Rep

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

It's likely that you will need to change some of the above inputs to your own username. Replace any references to /home/rise to /home/'username'.
Photo of DSquared

DSquared

  • 302 Points 250 badge 2x thumb
When I'm finished going thru the steps I get this message in terminal over and over again:

(gedit:5564): Gtk-WARNING **: GtkScrolledWindow 0x229d880 is mapped but visible child GtkScrollbar 0x22a4ae0 is not mapped

Clicking on the .sh file and running it works, so is this an issue with cron?
Photo of Matthew Fisher

Matthew Fisher

  • 1,420 Points 1k badge 2x thumb
DSquared,

Can you confirm what version of Ubuntu you're running (including whether it's 32 or 64 bit) and if updates have been applied?  Also, have you installed the crontab (crontab -e) as the current, logged in user (as opposed to root or some other user account)?

Thanks,

Matthew
Photo of Andrew Kreger

Andrew Kreger

  • 140 Points 100 badge 2x thumb
This reply was created from a merged topic originally titled Risevision player crashing in both Chrome and Chromium on Ubuntu 14.10.

Player is crashing in both browsers immediately after launching. Chromium lasts a couple seconds longer than chrome, but still crashes every time. Had a player die and I'm converting from the old application-based player to the new browser extension and not having a whole lot of luck so far. Clean install of ubuntu, so I'm not sure why it would be having any problems.

Here's the error that shows up in the debugging console when running the application with logging enabled.

[4260:4260:0623/145658:ERROR:extension_host.cc(367)] Killing renderer for extension mfpgpdablffhbfofnhlpgmokokbahooi for sending an EventAck message with a bad event id.[4260:4260:0623/145658:ERROR:bad_message.cc(16)] Terminating extension renderer for bad IPC message, reason 3

I'm guessing that if it's sending error messages like this on a clean install with no other applications or chrome extensions, there's probably some sort of faulty code in the app, so I figured here would be the best place to post about it. Any solutions or updates would be appreciated.
Photo of Matthew Fisher

Matthew Fisher

  • 1,420 Points 1k badge 2x thumb
Andrew,

First off, the standard disclaimer:  

As far as Linux goes, we only test on, and support, 32-bit Ubuntu 14.04.

That said, make sure all of the updates are installed--except the Chrome browser itself.
There is a known issue with the current version of Google Chrome (logged here: https://code.google.com/p/chromium/issues/detail?id=473821) and the workaround that we're telling people is to revert back to the last version that does not contain the bug--and make sure it doesn't get automatically updated to the broken version.

Previous versions can be downloaded here:

32 bit:  http://mirror.pcbeta.com/google/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_42....

64 bit: http://mirror.pcbeta.com/google/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_42....

These are not Rise Vision links and we cannot guarantee their availability or security.

Thanks,

Matthew
Photo of Andrew Kreger

Andrew Kreger

  • 140 Points 100 badge 2x thumb
If the only version that you support is 14.04, you should really update your website.

http://www.risevision.com/player/

In addition, you should probably post a notice here that the current version of chrome doesn't work correctly, as it explicitly states that the only supported version of chrome is the latest stable build, and highly advises against using anything else. In the original thread that my post was merged from, I was informed that the beta version of chrome contained the fix, and that has been working properly ever since.

If this information was present on the page I linked, rather than incorrect information, it would have saved a lot of headaches and prevented me from having to reach out for support. If you could update that page to save other customers the frustration, it would be appreciated.
Photo of Blake Freeman

Blake Freeman, Official Rep

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

We are in the process of releasing a brand new website, it should be up soon. We have already fully updated our user documentation, where you can find Optimization Guides for all supported operating systems.

Unfortunately, Google did not assign a proper priority to the issue that Matthew logged with them back in April, and the issue made it to the Stable channel. This does not affect all presentations,so we have not posted a community-wide announcement on the subject. Instead we've suggested a move to the Beta channel on a case-by-case basis. Under normal circumstances, Stable is the only channel that is supported. 
Photo of lucashokanson

lucashokanson

  • 142 Points 100 badge 2x thumb
This reply was created from a merged topic originally titled Intermittent Crashing of Rise Player on 3 Identical Ubuntu 14.04 Builds.

Hey all,  I'm looking for some hivemind input on this.  All of my 3 screens will crash intermittently. 

I have 3 desktop based Ubuntu 14.04 fresh builds all using the Rise Player app under Chrome Stable 43.0.2357.130.  All systems are using the latest system updates.  All of them are subject to semi-regular crashes along the lines of a few times an hour or more.

There are 2 unique presentations getting pushed out at any time, and one does crash more than the other.  

Main presentation - Tends to be more stable
http://preview.risevision.com/Viewer.html?type=presentation&id=00334621-704f-4a98-a824-8379fe3d0ee1

Second Presentation - Crashes very often.
http://preview.risevision.com/Viewer.html?type=presentation&id=8077d577-9105-4ff8-ac1f-81ab541dbba9

I've been searching to my wits end and I'm looking for ways I can try to diagnose this issue.  Chrome doesgive me a crash report dialog with some some assembly debug references, but that's not looking too useful (or easy to extract from Ubuntu's dialog window)  From what I can tell, my issues are unrelated to the known chrome beta issues.

If you have any ideas where to go or what to grab just say the word and I'll fetch log samples, files, blood samples, whatever.  I just want to try and get our displays stable.
Photo of Blake Freeman

Blake Freeman, Official Rep

  • 36,116 Points 20k badge 2x thumb
Hi Lucas,

I have merged your new topic into another topic that was created a few weeks ago. At the current time, we know of an issue regarding Rise Player on Chrome Stable Channel in Ubuntu 14.04. This is currently in Google's hands as an issue.

The the current time, there are two different things you can try. Creating a watchdog script (see above), or move to the Chrome Beta channel, which is not having the crashing issue. Let me know if you have any further questions!
Photo of lucashokanson

lucashokanson

  • 142 Points 100 badge 2x thumb
I've been running the Watchdog script since we deployed the displays.  

I've gone and removed chrome stable and rise player from all 3, deployed chrome beta, reinstalled rise and the issue persists for me.
Photo of lucashokanson

lucashokanson

  • 142 Points 100 badge 2x thumb
I'd also like to note that I'm seeing the displays crash all at the same time in most instances.  As if there was some push from RiseVision that ends up crashing them simultaneously. 
Photo of Andrew Shaw

Andrew Shaw

  • 90 Points 75 badge 2x thumb
It took some fiddling but I got it to work. Something's I noted when trying to set this up
  • Any instance of "/home/rise/" I had to change to "/home/*username*/"
  • For the crontab I had to change the first line to be * * * * * sh /home/*username*/Rise_player_watchdog otherwise it wouldn't work.
Apart from that it's working and I'll monitor the display for the next couple of days and see if it's the fix I've been looking for :)
Photo of Andrew Shaw

Andrew Shaw

  • 90 Points 75 badge 2x thumb
The display has been on for the past week or so without issue, it may of crashed during that time but the watchdog script has managed to reopen the software without issue.

Thanks guys
Photo of Dave

Dave

  • 886 Points 500 badge 2x thumb
Quick question about this thread. I have a chrome app player on 32bit Ubuntu (actually mint17).  The browser is the very latest and the rise player app is the very latest. 

The display connects and runs content on launch, no issues. But every time the content is "published" the player browser completely shuts down. Since the watchdog is not yet working for me, it stays down.

Question is: Why is a publish action it knocking down the browser at all?
Photo of Matthew Fisher

Matthew Fisher

  • 1,420 Points 1k badge 2x thumb
Dave,

I'm not aware of any issues that are specifically triggered by the act of publishing in RVA.  I've seen crashes that occur with the latest version of chrome (43.0.2357.132) under linux caused by this bug: https://code.google.com/p/chromium/issues/detail?id=473821 that can appear to be cause by publishing a new presentation, cycling between multiple presentations in a schedule, or frequently/randomly in general.

An easy way to identify whether a crash is cause by this bug is to start it from the command line and if/when the browser crashes, look at the output in the terminal window.  By pulling up the properties of the player icon, you can find the actual launch command (here is an *example*--your's may differ):
/opt/google/chrome/chrome "--profile-directory=Profile 1" --app-id=mfpgpdablffhbfofnhlpgmokokbahooi

If you launch the player by copying and pasting your command into the terminal, pressing enter, and at the time of the crash you see errors similar to this:
[ERROR:extension_host.cc] Killing renderer for extension mfpgpdablffhbfofnhlpgmokokbahooi for sending an EventAck message with a bad event id.
[ERROR:bad_message.cc] Terminating extension renderer for bad IPC message, reason 3
You are being affected by this (known and reported) Google Chrome bug.

Google has said that this will not be fixed until milestone 44 (the 44.x series of Chrome).

A workaround is to either install an earlier version (this bug is not present in 42.0.2311.152) and prevent it from updating to the latest version, or to temporarily switch to the beta version of Chrome (currently 44.0.2403.81).

Thanks,

Matthew
Photo of AdGators AdGators

AdGators AdGators

  • 3,612 Points 3k badge 2x thumb
To Update: I have installed google-chrome-stable 44.x and am experiencing crashing. version 42 is the only version that doesn't crash on me.
Photo of Matthew Fisher

Matthew Fisher

  • 1,420 Points 1k badge 2x thumb
AdGators,

If version 42.x is working for you, then I'd recommend you stick with that for a while.  We have updated our test units to run the new stable version (44.x) and have not seen any of the crashing we saw in 43.x.

One other possibility is that some of the earlier code could be running/conflicting if you updated the browser version while player was running.

Thanks,

Matthew
Do you know where to download an earlier deb version of Google Chrome like 42.0.2311.152. I have crash problems with since Version 43.x and 44.x
tks
Photo of ManifestoDigitale

ManifestoDigitale

  • 462 Points 250 badge 2x thumb
It doesn't work for me:

I already changed "rise" to my username in both watchdog file and crontab lines but if i close rise player it won't start. i changed launch string too...

If i open restart log file i see "player crashed. restarted at......" but the player isn't restarted... why?
Photo of Matthew Fisher

Matthew Fisher

  • 1,420 Points 1k badge 2x thumb
MontiDauni,

Can you verify that the launch path for the browser/player is correct?
Type "ls /opt/google/chrome/chrome"
As long as you don't get anything like "No such file or directory" you should be okay as far as that goes.

Can you also verify the name of the profile directory?  
The default profile name (that we've seen) is "Profile 1" and is specified in the launch string.
Look in ~/.config/google-chrome/  and make sure that whatever is identified as the profile directory in your modified watchdog script exists.

Another thing you can try is to view the contents of the watchdog script and try to execute the launch command yourself, from the command line.  That may give you a bit more information as to why it's not starting.  The line from the default script is (minus the output redirect):
/opt/google/chrome/chrome \"--profile-directory=Profile 1\" --app-id=mfpgpdablffhbfofnhlpgmokokbahooi

Thanks,

Matthew
Photo of ManifestoDigitale

ManifestoDigitale

  • 462 Points 250 badge 2x thumb
Thanks Matthew

1) I tried ls and i get a green line "/opt/google/crhome/chrome", so it's ok.
2) in ~/.config/google-chrome/ i have "default" and not "profile 1" folder, anyways as you can see in point 3 it works even with "profile 1" and i tried with "default" too (changing launch string in watchdog file)
3) I tried to launch from terminal "/opt/google/chrome/chrome \"--profile-directory=Profile 1\" --app-id=mfpgpdablffhbfofnhlpgmokokbahooi" and it works (it launchs rise player).


Another question, if i don't use this script, riseplayer has a function to autorestart? Because i noticed that in 2 days i had in restart log a lot of restart, even every 15 minutes (but i don't really know if it was real or fake). But, if i disable the script in crontab and go to the pc after 48 hours i see rise player still running correctly... so the question is:

Without watchdog script, riseplayer will restart automatically if it crashes (and i see player working after long time) or it doesn't crash and, watchdog restart log (when i activate script) is a fake?


Sorry for my bad english, i hope you understand.
Photo of Matthew Fisher

Matthew Fisher

  • 1,420 Points 1k badge 2x thumb
MontiDauni.com,

The chrome app version of Player does not have the capability to restart itself in the event of a crash or failure.  If the watchdog script has been disabled (by commenting out the line in the user's crontab that runs every minute) and you continue to see the player running for 24-48 hours, then it is simply not crashing as frequently as the log previously indicated.

Thanks,

Matthew
Photo of ManifestoDigitale

ManifestoDigitale

  • 462 Points 250 badge 2x thumb
Ok thanks Matthew,

so, why when i activate the string in crontab i see a lot of lines of "chrome/player crashed etc etc" if, when i deactivate it i don't have no crash for 2-3 days? Maybe there is a bug in script, anyways i don't know if rise really crash with script activated because when i come back to pc player is opened, but it simply should not crash.

And, another question, how can i solve my problem? (i correctly configured script but if i close manually rise player it won't reboot.)Thanks
Photo of Austin Thao

Austin Thao

  • 60 Points
Hello, I am having a problem locating my launch command on Ubuntu (I am a newbie when it comes to Ubuntu). I don't have a desktop application set up but when I try digging around my folders, I find that everything is connected to a "start.sh" script located in "/home/rise/rvplayer/2017.09.11.22.45/installer/script/start.sh" I have tried creating a desktop application but when I followed the steps here, I don't have a file called "rvplayer" to create a desktop application with. Rise Vision has been sporadically crashing and not restarting for some reason. I'm running Ubuntu 14.04.5 LTS with the latest version of rise player. I've tried uninstall/reinstall plenty of times already as well. Any help would be much appreciated!

Sidenote: When i run "./home/rise/rise_player_watchdog.sh"

I get an these errors:

"line 4: unexpected EOF while looking for mathcing  ``' "

"line 10: unexpected end of file"
(Edited)
Photo of Robb

Robb, Official Rep

  • 76,676 Points 50k badge 2x thumb
Austin,

Rather than force the Rise Player to start up at different times, I would suggest emailing support@risevision.com with a link to this forum discussion, as well as the Display ID of the Display that is having this issue. We can investigate on our side to see if there is any indications in the logs as to what this may be occurring.

Thanks!