Page 1 of 1
MX-Linux 23.3 installation doesn't work
Posted: Wed Dec 11, 2024 2:36 pm
by Max91
Hi. I'm not sure how to word this, so please bear with me. I run MX Linux Wildflower, 21.3, kernel 5.10, as a persistent live usb. I have installed UMS, and it works great, no problems. So, the way I've done this, is, I download the tarball, move it to the directory of my choice, right click the tarball, choose "extract here", and the output is the folder, with whatever contents are supposed to be in it. Then I usually will right click "UMS.sh", and scroll down to "send to", then choose "desktop(create link)". My system is set up for single click. I left click the desktop icon, and UMS starts up, I follow the wizard, to set up shared folder, choose renderer, which is a WDTV live, etc... My WDTV Live, picks up UMS, as a media server, no problem, plays content, no problem. Now, when I follow the exact same steps on my MX 23.3 installation, kernel 6. something. The renderer,(WDTV Live), will no longer let me choose UMS, as a media server, even when UMS picks up the renderer, I'm trying to use. I just keep getting an error. I'm using UMS 14.7.0. Everything regarding my internet connection, is the same, for both instances. I'm stumped. When I was running the MX 23.3, and tried to run UMS, my WDTV Live box, would spit out an "incorrect DNS server address. Please check your network setting, and try again", error. I have never set a DNS address. Sorry this is so long winded. Thank you. I wanted to add, when I try to connect, the WDTV Live box, gives me a "No content source available", error.
Re: MX-Linux 23.3 installation doesn't work
Posted: Wed Dec 11, 2024 3:26 pm
by mik_s
I have very little knowledge of Linux so I can give you any specific help if it is something related to the OS preventing UMS being shown on the WDTV box.
Usually if UMS can see the renderer but the renderer cannot see UMS then something is blocking the communication like a firewall.
None of this should have anything to do with your internet connection, just the local network setup.
Maybe your router got an update and changed something off like messing up the DNS. There should be a default setting for this.
If you post your logs (see the red section above) I might be able to see what is happening.
Re: MX-Linux 23.3 installation doesn't work
Posted: Thu Dec 12, 2024 12:15 pm
by Max91
Hi. First, there is no firewall set up.
Code: Select all
16:50:12 INFO Getting gui configuration file : /home/Cruzer1/.config/UMS/GUI.conf
16:50:14 INFO Starting Universal Media Server 14.7.0
16:50:14 INFO Based on PS3 Media Server by shagrath, copyright 2008-2014
16:50:14 INFO https://www.universalmediaserver.com
16:50:14 INFO
16:50:14 INFO Build: 6759ae32d (2024-10-29)
16:50:14 INFO Working directory: /home/Cruzer1/Downloads/ums-14.7.0
16:50:14 INFO Temporary directory: /tmp/UMS-Cruzer1
16:50:14 INFO Logging configuration file: /home/Cruzer1/Downloads/ums-14.7.0/logback.xml
16:50:14 INFO Logfile: /home/Cruzer1/.config/UMS/debug.log
16:50:14 INFO
16:50:14 INFO Profile directory: /home/Cruzer1/.config/UMS
16:50:14 INFO Profile directory permissions: drwx
16:50:14 INFO Profile configuration file: /home/Cruzer1/.config/UMS/UMS.conf
16:50:14 INFO Profile configuration file permissions: -rw-
16:50:14 INFO Profile name: mx
16:50:14 INFO
16:50:14 INFO Using database engine version 2.3.232
16:50:14 INFO Database may use 248 MB for caching
16:50:14 INFO Using "medias" database located at: "/home/Cruzer1/.config/UMS/database"
16:50:14 INFO HikariPool-1 - Starting...
16:50:14 INFO HikariPool-1 - Added connection conn0: url=jdbc:h2:/home/Cruzer1/.config/UMS/database/medias user=SA
16:50:14 INFO HikariPool-1 - Start completed.
16:50:14 INFO Using database engine version 2.3.232
16:50:14 INFO Database may use 248 MB for caching
16:50:14 INFO Using "USERS" database located at: "/home/Cruzer1/.config/UMS/database"
16:50:14 INFO HikariPool-2 - Starting...
16:50:14 INFO HikariPool-2 - Added connection conn3: url=jdbc:h2:/home/Cruzer1/.config/UMS/database/USERS user=SA
16:50:14 INFO HikariPool-2 - Start completed.
16:50:14 INFO Loading MediaInfo library
16:50:15 WARN Error loading libzen: Unable to load library 'zen':
libzen.so: cannot open shared object file: No such file or directory
libzen.so: cannot open shared object file: No such file or directory
Native library (linux-x86-64/libzen.so) not found in resource path (/home/Cruzer1/Downloads/ums-14.7.0/ums.jar)
16:50:15 ERROR Error loading MediaInfo library: Unable to load library 'mediainfo':
libmediainfo.so: cannot open shared object file: No such file or directory
libmediainfo.so: cannot open shared object file: No such file or directory
Native library (linux-x86-64/libmediainfo.so) not found in resource path (/home/Cruzer1/Downloads/ums-14.7.0/ums.jar)
16:50:15 INFO Make sure you have libmediainfo and libzen installed
16:50:15 INFO The server will now use the less accurate FFmpeg parsing method
16:50:15 INFO Finding user id: -1
16:50:15 INFO Getting shared content from configuration file : /home/Cruzer1/.config/UMS/SHARED.conf
16:50:17 INFO Starting Jetty server 12.0.14
16:50:17 INFO GUI is available at: http://localhost:9001
16:50:17 INFO Starting Jetty server 12.0.14
16:50:17 INFO Finding user id: -1
16:50:17 INFO Loading renderer and device configurations from /home/Cruzer1/Downloads/ums-14.7.0/renderers
16:50:18 INFO Enabled 1 configurations, listed in order of loading priority:
16:50:18 INFO : WD TV Live
16:50:18 INFO Checking the fontconfig cache in the background, this can take two minutes or so.
16:50:18 INFO Configuration saved to "/home/Cruzer1/.config/UMS/UMS.conf"
16:50:18 INFO Transcoding engine "FFmpeg Audio" is available
16:50:19 INFO Transcoding engine "MEncoder Video" is available
16:50:19 INFO Transcoding engine "FFmpeg Video" is available
16:50:19 INFO Transcoding engine "VLC Video" is available
16:50:19 INFO Transcoding engine "FFmpeg HLS Video" is available
16:50:19 INFO Transcoding engine "FFmpeg Web Video" is available
16:50:19 INFO Transcoding engine "MEncoder Web Video" is available
16:50:19 INFO Transcoding engine "VLC Web Video" is available
16:50:19 WARN Transcoding engine "tsMuxeR Video" is not available
16:50:19 WARN Transcoding engine "tsMuxeR Audio" is not available
16:50:19 INFO Transcoding engine "VLC Web Audio (Legacy)" is available
16:50:19 INFO Transcoding engine "VLC Web Video (Legacy)" is available
16:50:19 WARN Transcoding engine "DCRaw" is not available
16:50:19 INFO Transcoding engine "youtube-dl" is available
16:50:19 INFO Using the following UUID configured in UMS.conf: 7b337ffc-824f-4ef0-9df7-1d0b2aba19c4
16:50:19 INFO Registering UPnP servlet under context path:
16:50:19 INFO Starting Jetty server 12.0.14
16:50:19 INFO Starting Jetty HTTP client v12.0.14 connection manager/pool
16:50:19 INFO IP Filter: Access allowed to 10.0.0.130
16:50:20 INFO Web player is available at: http://10.0.0.130:9002
16:50:20 INFO Launching the graphical interface on a browser
16:50:20 INFO Universal Media Server is now available for renderers to find
16:50:27 INFO Checking user table have admin
16:51:14 INFO Setting default renderer to "WD TV Live"
16:51:19 INFO Stopping Jetty server...
16:51:19 INFO Finding user id: -1
16:51:19 INFO Loading renderer and device configurations from /home/Cruzer1/Downloads/ums-14.7.0/renderers
16:51:20 INFO Enabled 1 configurations, listed in order of loading priority:
16:51:20 INFO : WD TV Live
16:51:21 INFO Registering UPnP servlet under context path:
16:51:21 INFO Starting Jetty server 12.0.14
16:51:21 INFO Starting Jetty HTTP client v12.0.14 connection manager/pool
16:52:50 INFO IP Filter: Access allowed to _gateway
16:52:57 INFO IP Filter: Access allowed to 10.0.0.125
16:52:57 INFO Finding user id: -1
16:52:57 INFO Checking IP: 10.0.0.125 for WDTVLive
16:52:57 INFO Renderer WDTVLive found on address: 10.0.0.125
16:53:12 INFO Renderer WDTVLive has an estimated network speed of 6.923764596199314 Mb/s
17:08:24 INFO Changed debug level to TRACE
This is the log. Thanks.
Re: MX-Linux 23.3 installation doesn't work
Posted: Thu Dec 12, 2024 12:43 pm
by mik_s
That part you posted is not helpful. Please follow the instructions in the red section and post the full trace logs.