Ubuntu 14.04 Player Installation not working

  • 1
  • Problem
  • Updated 3 years ago
  • Solved
I am testing the player once again...this time on moving back away from the Chrome App Player and onto the custom shell script for Ubuntu that Rise Provides. I execute the file properly, however when at the end I get the message to run Rise Vision Player on OS Startup, regardless of choosing yes or no I get the same error...

no crontab for root
nohup: irnoring input and appending output to 'nohup.out'
Starting Rise Player..
nohup: irnoring input and appending output to 'nohup.out'

I'll stick with the CAP for now, but any assistance on this error would be great.

Thank you!
Joe Kirchner
Lubuntu 14.04, 64-bit, Intel i3, 4GB RAM
Photo of AdGators AdGators

AdGators AdGators

  • 3,612 Points 3k badge 2x thumb

Posted 3 years ago

  • 1
Photo of Blake Freeman

Blake Freeman, Official Rep

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

I'll need to confirm with one of our Linux gurus tomorrow, but I believe the installer has to be run as sudo or root in 64bit Linux.

You may be better off with a 32bit distro if possible.
Photo of Matthew Fisher

Matthew Fisher

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

Sorry about the delay in getting back with you.  I was out of the office for the last several days.  I don't recall whether earlier versions of the script removed the user's crontab, but I just looked at the current version and you're right.  If there is any reference to the Rise Player launching in it, the script will remove the crontab.  I'll talk to the devs about this, but as the player is launched at boot by from the startup group, and a background java process is responsible for monitoring and relaunching the player, I would remove any references to the player from the crontab.  That should prevent it from being removed (which may not be desired if you have other cron jobs scheduled as that user).

Thanks,

Matthew
Photo of AdGators AdGators

AdGators AdGators

  • 3,612 Points 3k badge 2x thumb
Thanks for getting back to me Matthew...I originally was using crontab to check if a process was running (i.e. chrome/google-chrome) and if not re-initializing the Rise Vision player. This is working remarkably well in my current build, utilizing the Chrome App Player. I will do some more testing around this, but since I am still not seeing any crontab entries after installation of rv-installer.sh, then I would guess that it's written somewhere in the java process (outside of crontab)....which, I have no way of controlling....so when/if Rise Player doesn't re-lauch, like I am currently seeing...then I can't fix it one way or the other. I'm not sure how it could be implemented, but if there were an option to hash out that particular line of code in the text rv-installer.sh, I would like to see directions on that. Therefore I can manually disable the removal of current crontabs and continue with my proven re-opening script.

I appreciate your help.
Photo of Matthew Fisher

Matthew Fisher

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

When using the Chrome App version of Player on Linux, a cron job was the recommended way of implementing a watchdog mechanism.  With the new version of Rise Player (installed by the steps mentioned above) a separate java process monitors the lifecycle of the chrome process and handles any necessary restarts, in addition to upgrades, etc.  If the player isn't being restarted within a minute or two of it exiting/crashing (without the reliance on a cron entry), please let us know.  That may be indicative of a problem we do not know about.

There are a few things to check that could contribute to a launch failure:

1.  Make sure that the Chrome App version is not running.  When pulling up a process list (ps aux | grep chrom), make sure you do *not* see something mentioning an app-id like:
/opt/google/chrome/chrome --app-id=mfpgpdablffhbfofnhlpgmokokbahooi

2.  Make sure that no Chrome App version is configured to run in "Startup Applications".  You may have to click "edit" and view the entire command line to ensure that any reference containing app-id=mfpgpdablffhbfofnhlpgmokokbahooi is disabled.

3.  Make sure that there are no cron entries launching the old rise_player_watchdog.sh script (it, or variations thereof, launched the Chrome App version)

4.  Verify that no files or folders in the user's home directory are owned by root.  This can be done by typing the following command from the player's account (and replacing both instances of USERNAME with the appropriate username):
sudo chown -R USERNAME.USERNAME ~

5.  Make sure that none of the player-related processes are running as root.  In a maximized terminal window (for convenience) type:
ps aux
The process owner will be the first column.  Look for items running from the account's home directory.


I've spoken with a developer and this change has been added to the to-do list.  Hopefully this will help in the meantime.

Thanks,

Matthew
Photo of AdGators AdGators

AdGators AdGators

  • 3,612 Points 3k badge 2x thumb
Thanks Matthew, I will get this tested out. I will let you know what I find out.
Photo of AdGators AdGators

AdGators AdGators

  • 3,612 Points 3k badge 2x thumb
Hi Matthew,
Any word on Crontab being re-written?
Thanks,
Joe Kirchner
Photo of AdGators AdGators

AdGators AdGators

  • 3,612 Points 3k badge 2x thumb
Hi Matthew,
I would very much like to begin testing this new shell install on our media players, however the cronjob being re-written when the application starts is removing other customized cronjobs I have running. Is it possible to prevent this from happening? If it means me manually running a cronjob to restart Rise, that is no probelm.
Thanks,
Joe Kirchner
Photo of Matthew Fisher

Matthew Fisher

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

I just spoke with one of our developers and they should be looking into this for you soon.  Because the player checks for updates regularly, if you modify the script yourself it will eventually be overwritten so that's probably not the best option.  As an alternative (until the issue is fixed), what about adding whatever cron jobs you need to the system crontab but specify them to be run as the user (instead of root)?

Thanks,

Matthew
Photo of AdGators AdGators

AdGators AdGators

  • 3,612 Points 3k badge 2x thumb
Thanks for looking into this Matthew,
I will try that out, but if I remember certain applications do not like running as root, and therefore must be ran under the logged in users account.
Photo of Matthew Fisher

Matthew Fisher

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

The syntax for the system cron jobs is a little different from the per-user ones.  The sixth field specifies the user that the job runs as (see /etc/crontab for examples).  This should allow an effect similar to if it was a normal, user cron job.

Thanks,

Matthew