More > JRiver Media Center 21 for Linux
Quick start guide for installing JRiver Mediacenter 21 ARM for Raspberry Pi
mwillems:
--- Quote from: phillil on November 30, 2015, 04:52:03 pm ---OK I've figured it out!
The command was correct, it wasn't mounting however because there was no network connection
So I changed the Pi2 config to wait for network at boot, now it works!!
Thanks, and sorry for clogging up this thread
--- End quote ---
No worries, glad you got it sorted!
phillil:
Hi there,
it's been a few weeks now MC seems to still be running OK on my RPi2 to the point I'm almost considering packing the PC away!!
However there is one small niggle...
I leave my RPi2 on all the time, and fire-up JRemote to start playing music. However on occasion MC won't respond, and although it is still running when I check using my laptop (TigerVNC) it seems to have locked up.
I'm not sure what causes this - I know if I try and play a track before the amp (USB DAC) is switched on it can get upset. Also when I clear a playlist??
Either way it's very frustrating as I have to login using Tiger and reboot the RPi manually, which is OK for me but not very wife friendly. I was hoping the RPi / MC would be ultra stable as it's on Linux, but it doesn't seem to be the case
I have setup a cron task as per the setup guide which is supposed to restart MC if it stops running, but this doesn't seem to rectify the issue. Once MC stops responding, it won't close, restart etc. if i try manually and the only thing I can do is to reboot the RPi which 100%n cures the problem
Is it possible to setup a cron that reboots the RPi if MC stops responding, rather than restarting MC??
Many thanks
mwillems:
--- Quote from: phillil on December 10, 2015, 05:06:43 pm ---Hi there,
it's been a few weeks now MC seems to still be running OK on my RPi2 to the point I'm almost considering packing the PC away!!
However there is one small niggle...
I leave my RPi2 on all the time, and fire-up JRemote to start playing music. However on occasion MC won't respond, and although it is still running when I check using my laptop (TigerVNC) it seems to have locked up.
I'm not sure what causes this - I know if I try and play a track before the amp (USB DAC) is switched on it can get upset. Also when I clear a playlist??
Either way it's very frustrating as I have to login using Tiger and reboot the RPi manually, which is OK for me but not very wife friendly. I was hoping the RPi / MC would be ultra stable as it's on Linux, but it doesn't seem to be the case
I have setup a cron task as per the setup guide which is supposed to restart MC if it stops running, but this doesn't seem to rectify the issue. Once MC stops responding, it won't close, restart etc. if i try manually and the only thing I can do is to reboot the RPi which 100%n cures the problem
Is it possible to setup a cron that reboots the RPi if MC stops responding, rather than restarting MC??
Many thanks
--- End quote ---
The hard part would be knowing when mc stopped responding programmatically. I'm not sure how to know that that's the case if you see what I mean. Bob may have some thoughts.
For your reference, you don't need to reboot the pi, you should be able to terminate the MC process and restart using one of the "kill" family of commands. I.e. typing "killall mediacenter21" into a terminal should terminate MC, and then the cron script would restart it about a minute later. You might be able to script something that kills and restarts MC on command, which would speed up the restarts if things have gone sideways.
phillil:
It's a real shame because it's a bit of a show-stopper to be honest...
I tend to check each morning just to see if MC is still responding, and this morning it had crashed again. It was still running, but just wouldn't respond to anything
I suppose the other option is powering the RPi2 from my amp, so it cold booted each time the amp started. I suppose this is really risky because the RPi2 would frequently experience the power being pulled (each time the amp is switched off) which may corrupt the SD card??
mwillems:
--- Quote from: phillil on December 11, 2015, 02:14:11 am ---I suppose the other option is powering the RPi2 from my amp, so it cold booted each time the amp started. I suppose this is really risky because the RPi2 would frequently experience the power being pulled (each time the amp is switched off) which may corrupt the SD card??
--- End quote ---
I haven't experienced the kind of instability you're seeing, but if I were trying to work around this problem, I would probably leave the pi on, but write a script that kills and restarts JRiver. I would then either bind the script to a remote control button or an ssh android app. Honestly if you really want it to be "easy" for an end user (but not necessarily for you who has to set it up), the Pi has many input output pins that can be used to trigger scripts. You also could buy a physical button that would restart JRiver: https://www.raspberrypi.org/documentation/usage/gpio/ . Or it may be possible rig up your amp (if it has a signalling relay, which many amps do) to send a signal to one of the pins triggering a JRiver restart based on the amp turning on.
None of that is as hard as it sounds, but honestly you would do better to figure out what's triggering the crash and fix it. I have a pi with 47 days of uptime right now and I've only restarted JRiver once in that time (during an upgrade). I use it most days. If it's just a matter of not trying to start playback with the amp off that seems easy enough to work around, but if I were you I would try to reproduce the lockup until I figured it out.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version