More > JRiver Media Center 28 for Linux
installJRMC - MC installer for Linux
countryboy:
I did a post on the main forum today about stability problems with jriver running headless. @BryanC suggested using the installJRMC script to install and configure a tigervnc server running an instance of jriver. His clever script sets this up automatically, and I thought it was a clever idea to provide a virtual console for a headless machine. It seemed to work, but I'm a bit clueless on configuration and use.
what I did: used the package manager to remove my existing media center, then used the script:
installJRMC --install repo --service jriver-xvnc
After rebooting as a precaution, I see this, which looks good to me:
ps -ef |grep jriver
jim 3786 1 1 21:35 ? 00:00:00 /usr/bin/perl /usr/bin/vncserver :1 -geometry 1440x900 -alwaysshared -name jriver:1 -SecurityTypes None -autokill -xstartup /usr/bin/mediacenter28
jim 3794 3786 0 21:35 ? 00:00:00 /usr/bin/perl /usr/bin/vncserver :1 -geometry 1440x900 -alwaysshared -name jriver:1 -SecurityTypes None -autokill -xstartup /usr/bin/mediacenter28
jim 3795 3794 3 21:35 ? 00:00:00 /usr/bin/Xtigervnc :1 -rfbport 5901 -localhost=1 -SecurityTypes None -ClientWaitTimeMillis 30000 -NeverShared=0 -AlwaysShared=1 -geometry 1440x900 -desktop jriver:1 -depth 24 -auth /home/jim/.Xauthority
jim 4012 2806 0 21:35 pts/0 00:00:00 grep jriver
I also note that if I try starting another instance of mediacenter from the console, it runs but warns me the library is readonly: makes sense, since another copy of jriver is already running.
Well, but now I need some handholding. I haven't yet tested whether this VNC trick solves my stability problem running headless, but it certainly looks good. However, I need some newbie help in accessing the server: have mercy, I haven't used VNC in decades...
- neither the web interface nor gizmo can access the jriver server running on the VNC display. if I start a read-only media server on the console, both work fine
- on android, I tried using VNC connect to access the server. no luck.
assuming the stability problem is solved with this trick, how do I access mediacenter once I am headless again? probably dumb question, but us old guys have no shame....
BryanC:
It looks like VNC is running on port 5901 so in your VNC client you will want to specify the port manually as the standard port for VNC is 5900. installJRMC does this on purpose to avoid conflicting with other services.
In some clients this can be done with your.host:5901, others may have a separate combobox to specify the custom port separately.
Let me know if that gets you any further along. The underlying reason why this is required is that MC depends on an active X11 session to launch. tigervnc provides an easy way to make this happen with the added benefit of a remote GUI. It is strange that you cannot connect to the Library Server, but once you can access the VNC session then you should be able to confirm the Media Network settings are correct.
countryboy:
thanks for the reply and help. bottom line is that I think things are mostly configured ok but there is some security settings I am missing. Maybe this is all newbie stuff you shouldn't need to help...
here's some info:
ss -tulpn gives:
tcp LISTEN 0 5 [::1]:5901 [::]:* users:(("Xtigervnc",pid=824126,fd=10)
syslog shows:
Feb 18 11:29:40 melody vncserver[839567]: Please be aware that you are exposing your VNC server to all users on the
Feb 18 11:29:40 melody vncserver[839567]: local machine. These users can access your server without authentication!
Feb 18 11:29:40 melody vncserver[839575]: New Xtigervnc server 'jriver:1' on port 5901 for display :1.
Feb 18 11:29:40 melody vncserver[839575]: Use xtigervncviewer -SecurityTypes None :1 to connect to the VNC server.
I've tried several vnc clients, including VNC connect on android, tightvnc on windows, and vncviewer on raspberry pi OS. A typical error message is "no connection could be made because the target machine actively refused it." (This is from vncviewer on the pi, when I try either of port or display ('vncviewer <serverIP>::5901' or 'vncviewer <serverIP>:1)
The ps output seems to show a vnc server running without security. does debian have default additional port security?
All the machines are on a common subnet, direct connect via ethernet (except android tablet wirelessly bridged onto same subnet)
The vnc server started automatically as a result of installrmc seems to have security turned off (but I'm not an expert): some debian 11.2 port security problem (?) here's the ps output again
jim 24798 1 7 12:59 ? 00:00:00 /usr/bin/perl /usr/bin/vncserver :1 -geometry 1440x900 -alwaysshared -name jriver:1 -SecurityTypes None -autokill -xstartup /usr/bin/mediacenter28
jim 24806 24798 0 12:59 ? 00:00:00 /usr/bin/perl /usr/bin/vncserver :1 -geometry 1440x900 -alwaysshared -name jriver:1 -SecurityTypes None -autokill -xstartup /usr/bin/mediacenter28
jim 24807 24806 4 12:59 ? 00:00:00 /usr/bin/Xtigervnc :1 -rfbport 5901 -localhost=1 -SecurityTypes None -ClientWaitTimeMillis 30000 -NeverShared=0 -AlwaysShared=1 -geometry 1440x900 -desktop jriver:1 -depth 24 -auth /home/jim/.Xauthority
Not sure where to go next, I'm not a vnc expert....
BryanC:
I can reproduce this in my Debian VM so I'll do some digging.
BryanC:
OK, this issue should be fixed in 1.0b11, thanks for reporting it!
Before running the new version of installJRMC, stop the existing service first `sudo systemctl stop jriver-xvnc@jim.service` to clear it from memory.
That should fix your connection issue as well (the service was looping).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version