Page 1 of 1

unable to share with raspberry pi

Posted: Sat Apr 02, 2022 1:19 pm
by Max_tonetto
Hi,
I'm trying to install ums into a RBpi 4 that runs dietpi (64bit version, so I pulled UMS-10.19.0-arm64.tgz from the github page). I was able to install it and run the service, but then I'm not able to connect, neither using a browser with another pc on port 9001 (it says "The connection was reset") nor using a dlna device.

Since it is a headless device that I only control through ssh is possible (probable) that I've done something wrong during installation/first set up.

Attached you can find the log file, in which it seems to be clear that the default port 9001, or any other port, are not even used

Thanks in advance!

Re: unable to share with raspberry pi

Posted: Sun Apr 03, 2022 2:03 am
by mik_s
I had a quick look at your logs and it looks like UMS is not fully starting, or at least not getting to a point where it can look for renderers on the network. The logs seem to just cut off and nothing else looks out of the ordinary. The last thing in the log is finding the network interface then nothing.

Code: Select all

[main] first network interface: InterfaceAssociation(addr=/192.168.1.10, iface=name:eth0 (eth0), parent=null)
I have no experience with the Pi and very little with Linux so I'm not sure what is going wrong.

It could be something wrong with your configuration, could you post your UMS.conf? There may be 2 locations that could be in, it won't be the one in UMS's installation directory that is being used but I don't know where it will be on the Pi.

Re: unable to share with raspberry pi

Posted: Mon Apr 04, 2022 1:08 pm
by Max_tonetto
the following is the UMS.conf content

Code: Select all

minimized = true
scan_shared_folders_on_startup = true
run_wizard = false
cred.path = /home/dietpi/.config/UMS/UMS.cred
log_level = TRACE

Re: unable to share with raspberry pi

Posted: Mon Apr 04, 2022 2:26 pm
by mik_s
I was expecting a lot more than that. Maybe it never installed correctly.

I don't know about how to use it in headless mode but is there a way to connect the Pi to a screen and run the GUI?

I can't be much more help as I have no idea but I can point you to this post that someone has written a guide on how to install headless in Ubuntu. It might give you an idea on how to get it to work.

I have also seen docker mentioned along with running in headless and I'm sure there is an image setup for that.

Re: unable to share with raspberry pi

Posted: Mon Apr 04, 2022 10:50 pm
by Max_tonetto
starting the service manually simply running ums.sh I obtain the following output

Code: Select all

INFO  11:38:00.432 [main] Language not specified, defaulting to OS language.
INFO  11:38:01.069 [main] Starting Universal Media Server 10.19.0
INFO  11:38:01.070 [main] Based on PS3 Media Server by shagrath, copyright 2008-2014
INFO  11:38:01.072 [main] https://www.universalmediaserver.com
INFO  11:38:01.073 [main] 
INFO  11:38:01.075 [main] Build: 791430c34 (2022-03-14)
INFO  11:38:01.076 [main] Working directory: /opt/ums
INFO  11:38:01.078 [main] Temporary directory: /tmp/UMS-dietpi
INFO  11:38:01.079 [main] Logging configuration file: /opt/ums/logback.headless.xml
INFO  11:38:01.081 [main] Logfile: /home/dietpi/.config/UMS/debug.log
INFO  11:38:01.082 [main] 
INFO  11:38:01.084 [main] Profile directory: /home/dietpi/.config/UMS
INFO  11:38:01.085 [main] Profile directory permissions: drwx
INFO  11:38:01.087 [main] Profile configuration file: /home/dietpi/.config/UMS/UMS.conf
INFO  11:38:01.090 [main] Profile configuration file permissions: -rw-
INFO  11:38:01.092 [main] Profile name: DietPi
INFO  11:38:01.093 [main] 
INFO  11:38:01.096 [main] Web configuration file: /home/dietpi/.config/UMS/WEB.conf
INFO  11:38:01.098 [main] Web configuration file permissions: -rw-
INFO  11:38:01.099 [main] 
INFO  11:38:01.127 [main] Using database engine version 2.1.210
INFO  11:38:01.129 [main] Using "medias" database located at: "/home/dietpi/.config/UMS/database"
INFO  11:38:01.623 [System Information Logger] System information:
  OS: GNU/Linux Debian GNU/Linux 11 (bullseye) build 5.15.30-v8+ 64-bit
  JVM: OpenJDK 64-Bit Server VM 17.0.2 (64-bit) by Debian
  Language: English (United States)
  Encoding: UTF-8
  CPU:  with 4 cores
  Physical Memory: 1.8 GiB
  Free Memory: 1.2 GiB
  Maximum JVM Memory: 1.3 GiB
  Used network interfaces:
  eth0, speed 104 Mb/s

INFO  11:38:02.573 [main] FFmpeg web filters "/home/dietpi/.config/UMS/ffmpeg.webfilters" not found, web filters ignored: /home/dietpi/.config/UMS/ffmpeg.webfilters (No such file or directory)
INFO  11:38:02.594 [main] Graphics environment not available or headless mode is forced
INFO  11:38:02.594 [main] Switching to console mode
INFO  11:38:02.737 [main] Loading MediaInfo library
INFO  11:38:02.776 [main] Loaded MediaInfoLib - v20.09
INFO  11:38:02.798 [main] Loading renderer configurations from /opt/ums/renderers
INFO  11:38:04.187 [main] Enabled 199 configurations, listed in order of loading priority:
I...
Apr 04, 2022 11:38:04 AM org.fourthline.cling.UpnpServiceImpl <init>
INFO: >>> Starting UPnP service...
Apr 04, 2022 11:38:04 AM org.fourthline.cling.UpnpServiceImpl <init>
INFO: Using configuration: net.pms.network.mediaserver.cling.UmsUpnpServiceConfiguration
Apr 04, 2022 11:38:04 AM org.fourthline.cling.transport.RouterImpl <init>
INFO: Creating Router: org.fourthline.cling.transport.RouterImpl
Apr 04, 2022 11:38:04 AM org.fourthline.cling.transport.impl.MulticastReceiverImpl init
INFO: Creating wildcard socket (for receiving multicast datagrams) on port: 1900
Apr 04, 2022 11:38:04 AM org.fourthline.cling.transport.impl.MulticastReceiverImpl init
INFO: Joining multicast group: /239.255.255.250:1900 on network interface: eth0
Apr 04, 2022 11:38:04 AM org.fourthline.cling.transport.impl.StreamServerImpl init
INFO: Created server (for receiving TCP streams) on: /192.168.1.10:36131
Apr 04, 2022 11:38:04 AM org.fourthline.cling.transport.impl.DatagramIOImpl init
INFO: Creating bound socket (for datagram input/output) on: /192.168.1.10
Exception in thread "main" java.lang.IllegalAccessError: superclass access check failed: class net.pms.network.mediaserver.cling.transport.impl.JdkHttpURLConnectionStreamClient$UpnpHttpHandler (in unnamed module @0x202e401) cannot access class sun.net.www.protocol.http.Handler (in module java.base) because module java.base does not export sun.net.www.protocol.http to unnamed module @0x202e401
	at java.base/java.lang.ClassLoader.defineClass1(Native Method)
	at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1012)
	at java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:150)
	at java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:862)
	at java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:760)
	at java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:681)
	at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:639)
	at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:520)
	at net.pms.network.mediaserver.cling.UmsUpnpServiceConfiguration.createStreamClient(UmsUpnpServiceConfiguration.java:62)
	at org.fourthline.cling.transport.RouterImpl.enable(RouterImpl.java:142)
	at org.fourthline.cling.UpnpServiceImpl.<init>(UpnpServiceImpl.java:87)
	at net.pms.network.mediaserver.cling.UmsUpnpService.<init>(UmsUpnpService.java:29)
	at net.pms.network.mediaserver.UPNPControl.init(UPNPControl.java:134)
	at net.pms.network.mediaserver.UPNPHelper.init(UPNPHelper.java:55)
	at net.pms.network.mediaserver.MediaServer.init(MediaServer.java:50)
	at net.pms.PMS.init(PMS.java:595)
	at net.pms.PMS.createInstance(PMS.java:914)
	at net.pms.PMS.main(PMS.java:1080)
It seems to fail to create the socket (trying to access 192.168.1.10:36131 doesn't work of course) for a java error. Could it be usefull?

Re: unable to share with raspberry pi

Posted: Mon Apr 04, 2022 11:31 pm
by Max_tonetto
I downgraded from openjdk17 to openjdk11 and now seems to work!