More > JRiver Media Center 22 for Linux
Quick Start Guide for Installing JRiver Mediacenter 22 ARM on a Raspberry Pi
akira54:
I am at a loss trying to figure out what I do wrong but I cannot get MC22 to start up after a reboot. It runs fine when I start it from the Pi menu.
I have followed MWillems’ latest instructions for MC23 (using them for MC22) and this is what I have done:
1. I have set up a jriver.service exactly as MWillems suggests (except for entering “mediacenter22 /MediaServer” instead of 23)
2. I have run “sudo systemctl enable jriver.service” and get no error message
When I reboot mediacenter does not turn up in taskmanager and I cannot connect using JRemote. What could be wrong?
mwillems:
--- Quote from: akira54 on September 10, 2017, 08:06:25 am ---I am at a loss trying to figure out what I do wrong but I cannot get MC22 to start up after a reboot. It runs fine when I start it from the Pi menu.
I have followed MWillems’ latest instructions for MC23 (using them for MC22) and this is what I have done:
1. I have set up a jriver.service exactly as MWillems suggests (except for entering “mediacenter22 /MediaServer” instead of 23)
2. I have run “sudo systemctl enable jriver.service” and get no error message
When I reboot mediacenter does not turn up in taskmanager and I cannot connect using JRemote. What could be wrong?
--- End quote ---
Do you see anything relevant when you type "systemctl status jriver.service" or "journalctl -xe" in the terminal? Are you using an alternative VNC method (you mentioned that in the other thread)?
akira54:
Since my system is headless and I cannot really hook it up to a monitor I have been reluctant to use x11vnc even though I setup the service as you suggested. I just have not run it yet, since I did want to loose connectivity between my Mac and the RPi (I have VNC Enabled in Raspberry Configuration and use VNC Viewer on my Mac).
Anyway, this is what I see when I run "systemctl status jriver.service":
pi@raspberrypi:~ $ systemctl status jriver.service
● jriver.service - JRiver
Loaded: loaded (/etc/systemd/system/jriver.service; enabled)
Active: activating (auto-restart) (Result: exit-code) since Sun 2017-09-10 20:09:36 CEST; 3s ago
Process: 10154 ExecStart=/usr/bin/mediacenter23 /MediaServer (code=exited, status=203/EXEC)
Main PID: 10154 (code=exited, status=203/EXEC)
pi@raspberrypi:~ $
I do not understand the reference to mediacenter23 (not installed). So I checked the file again and low and behold it referred to MC23 even though I had changed it explicitly before (perhaps I did not save it properly?). When I now reboot MC does start but with its graphical front end (after reboot JRiver Mediacenter shows up in the Task Bar). When I run the command again I get:
jriver.service - JRiver
Loaded: loaded (/etc/systemd/system/jriver.service; enabled)
Active: active (running) since Sun 2017-09-10 20:15:26 CEST; 5min ago
Main PID: 839 (mediacenter22)
CGroup: /system.slice/jriver.service
└─839 /usr/bin/mediacenter22 /MediaServer
mwillems:
--- Quote from: akira54 on September 10, 2017, 01:22:35 pm ---Since my system is headless and I cannot really hook it up to a monitor I have been reluctant to use x11vnc even though I setup the service as you suggested. I just have not run it yet, since I did want to loose connectivity between my Mac and the RPi (I have VNC Enabled in Raspberry Configuration and use VNC Viewer on my Mac).
Anyway, this is what I see when I run "systemctl status jriver.service":
pi@raspberrypi:~ $ systemctl status jriver.service
● jriver.service - JRiver
Loaded: loaded (/etc/systemd/system/jriver.service; enabled)
Active: activating (auto-restart) (Result: exit-code) since Sun 2017-09-10 20:09:36 CEST; 3s ago
Process: 10154 ExecStart=/usr/bin/mediacenter23 /MediaServer (code=exited, status=203/EXEC)
Main PID: 10154 (code=exited, status=203/EXEC)
pi@raspberrypi:~ $
I do not understand the reference to mediacenter23 (not installed). So I checked the file again and low and behold it referred to MC23 even though I had changed it explicitly before (perhaps I did not save it properly?). When I now reboot MC does start but with its graphical front end (after reboot JRiver Mediacenter shows up in the Task Bar). When I run the command again I get:
jriver.service - JRiver
Loaded: loaded (/etc/systemd/system/jriver.service; enabled)
Active: active (running) since Sun 2017-09-10 20:15:26 CEST; 5min ago
Main PID: 839 (mediacenter22)
CGroup: /system.slice/jriver.service
└─839 /usr/bin/mediacenter22 /MediaServer
--- End quote ---
Mediacenter will start with the graphical frontend, there is no linux tray icon. The mediaserver flag just prevents MC from popping up blocking modal dialogs (that no one will be there to see on a headless system), so it's advisable. Sounds like things are mostly working correctly. If you have instability, as suggested in the other thread, you might want to try x11vnc. Another tip is to make sure thumbnailing priority is set to "low" in options, and then pre-build all thumbnails. Thumbnail generation happens on demand, but can easily trigger an OOM condition on the pi which crashes MC. Pre-building thumbnails solves that problem.
akira54:
Thanks for the sound advice. I am prebuilding all thumbnails and have set the building of thumbnails to low priority. I know this topic about thumbnails has come up before but is it perhaps a good idea to add that to your instructions, since it is something that effects the running of MC on a RPi?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version