UMS Unable To Start
Forum rules
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
Re: UMS Unable To Start
I might have given you the wrong start command. I haven't used Debian Linux (perhaps others with Debian experience could help), but it looks as though your system uses systemctl.
I think the start command might be:
systemctl start /opt/ums/UMS.sh
and
systemctl stop /opt/ums/UMS.sh
But maybe you were already doing that.
I don't think your issues is a UMS issues as such and you will have better luck posting in a forum specific to Raspbian Jessie/Debian.
Hopefully you will get there in the end and I am sure you will be happy with UMS.
I think the start command might be:
systemctl start /opt/ums/UMS.sh
and
systemctl stop /opt/ums/UMS.sh
But maybe you were already doing that.
I don't think your issues is a UMS issues as such and you will have better luck posting in a forum specific to Raspbian Jessie/Debian.
Hopefully you will get there in the end and I am sure you will be happy with UMS.
Re: UMS Unable To Start
I believe this configuration of UMS came from this forum.
I am sorry the proper person is not sited.
I use a 2 server system,
1) File server
2) UMS server
I’ve used both Ubuntu 15, 16 and Debian 8. Ubuntu works best with my Sony BLU-RAY player.
I use UFW for a firewall, ports are listed below.
File server set up on the UMS system.
Check fstab
Ubuntu setup
Note Java 7 does not work with Ubuntu 16.04 Xenial
Debian Jessie 8 setup
Both systems.
Change the wget to reflect UMS version.
These are my personal setting for the Sony and multiple drives.
Firewall ports
tcp 9001
tcp 5001
udp 1900
Remove WEB from menu
Good Luck!
I am sorry the proper person is not sited.
I use a 2 server system,
1) File server
2) UMS server
I’ve used both Ubuntu 15, 16 and Debian 8. Ubuntu works best with my Sony BLU-RAY player.
I use UFW for a firewall, ports are listed below.
File server set up on the UMS system.
Code: Select all
mkdir /home/Video
mkdir /home/Cinema
nano /etc/fstab
//10.0.69.34/Video /home/Video cifs username=user,password=passwd,iocharset=utf8,sec=ntlm 0 0
//10.0.69.34/Cinema /home/Cinema cifs username=user,password=passwd,iocharset=utf8,sec=ntlm 0 0
Code: Select all
mount -a
df -h
ls -la /home
Note Java 7 does not work with Ubuntu 16.04 Xenial
Code: Select all
apt-get install software-properties-common
add-apt-repository ppa:webupd8team/java
apt-get update
apt-get install oracle-java7-installer
apt-get install oracle-java8-set-default
Code: Select all
sh -c 'echo "deb http://ppa.launchpad.net/webupd8team/java/ubuntu xenial main" >> /etc/apt/sources.list'
sh -c 'echo "deb-src http://ppa.launchpad.net/webupd8team/java/ubuntu xenial main" >> /etc/apt/sources.list'
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys EEA14886
apt-get update
apt-get install oracle-java8-installer
Code: Select all
apt-get install mediainfo dcraw vlc-nox mplayer2
Code: Select all
cd ~
wget https://sourceforge.net/projects/unimediaserver/files/Official%20Releases/Linux/UMS-6.4.0-Java8.tgz
tar xvzf UMS-6.4.0-Java8.tgz
ls -la
mv ums-6.4.0 /etc/ums
ls -la
rm UMS-6.0.0-b2.tgz
nano /etc/init.d/ums
ums_init.d
chmod +x /etc/init.d/ums
update-rc.d ums defaults
service ums start
nano /etc/ums/UMS.cred
nano /etc/ums/UMS.conf
Code: Select all
prettify_filenames =true
folders =""
Change Virtual Folders File
virtual_folders_file =VirtualFolders.conf
nano /etc/ums/VirtualFolders.conf
VirtualFolders.conf
tcp 9001
tcp 5001
udp 1900
Remove WEB from menu
Code: Select all
mv /etc/ums/WEB.conf /etc/ums/WEB.conf.bak
service ums restart
- Attachments
-
VirtualFolders_conf.txt
- (516 Bytes) Downloaded 777 times
-
ums_initd.txt
- (4.48 KiB) Downloaded 794 times
Re: UMS Unable To Start
Thanks for the replies.
I think I've managed to get the systemd setup though I'm still running into the initialization error. The first time I try and run it I get this:
Which doesn't occur the second time I run it though in both cases it generates the same errors in the debug log file.
I'm not sure what to do without knowing what the error is that UMS is throwing
I think I've managed to get the systemd setup though I'm still running into the initialization error. The first time I try and run it I get this:
Code: Select all
sudo systemctl status ums
? ums.service - Universal Media Server
Loaded: loaded (/etc/systemd/system/ums.service; enabled)
Active: inactive (dead) since Fri 2016-07-29 12:03:16 BST; 34s ago
Process: 369 ExecStart=/opt/ums/UMS.sh (code=exited, status=0/SUCCESS)
Main PID: 369 (code=exited, status=0/SUCCESS)
Jul 29 12:03:15 flirc-pi UMS.sh[369]: 12:03:15,679 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.apache] to WARN
Jul 29 12:03:15 flirc-pi UMS.sh[369]: 12:03:15,681 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [httpclient.wire] to WARN
Jul 29 12:03:15 flirc-pi UMS.sh[369]: 12:03:15,683 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [fm.last.musicbrainz.coverart] to WARN
Jul 29 12:03:15 flirc-pi UMS.sh[369]: 12:03:15,684 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to DEBUG
Jul 29 12:03:15 flirc-pi UMS.sh[369]: 12:03:15,686 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [console] to Logger[ROOT]
Jul 29 12:03:15 flirc-pi UMS.sh[369]: 12:03:15,688 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [default.log] to Logger[ROOT]
Jul 29 12:03:15 flirc-pi UMS.sh[369]: 12:03:15,688 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration.
Jul 29 12:03:15 flirc-pi UMS.sh[369]: 12:03:15,690 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@6fa38a - Registering current configuration as safe fallback point
Jul 29 12:03:15 flirc-pi UMS.sh[369]: INFO 12:03:12.109 [main] Language not specified, defaulting to OS language.
Jul 29 12:03:16 flirc-pi UMS.sh[369]: ERROR 12:03:16.241 [main] A serious error occurred during Universal Media Server initialization: null
Code: Select all
DEBUG 2016-07-29 12:05:25.820 [main] Base path set to file:///etc/ums/UMS.conf
DEBUG 2016-07-29 12:05:26.524 [main] FileName set to UMS.conf
DEBUG 2016-07-29 12:05:26.525 [main] Base path set to /etc/ums
INFO 2016-07-29 12:05:26.655 [main] Language not specified, defaulting to OS language.
DEBUG 2016-07-29 12:05:27.545 [main] Default logfile folder set to: /var/log/UMS/root
DEBUG 2016-07-29 12:05:29.778 [main] LogBack started with configuration file: /opt/ums-6.4.0/logback.headless.xml
DEBUG 2016-07-29 12:05:29.967 [main] Fri Jul 29 12:05:29 BST 2016
DEBUG 2016-07-29 12:05:29.972 [main] Reading cred.path: "/etc/ums/UMS.cred" (default: "")
DEBUG 2016-07-29 12:05:29.975 [main] PID file not found, cannot check for running process
DEBUG 2016-07-29 12:05:29.989 [main] Writing PID: 681
ERROR 2016-07-29 12:05:30.234 [main] A serious error occurred during Universal Media Server initialization: null
Re: UMS Unable To Start
Are all your paths set right?
This one seems different because UMS ver. number.
Shared folders
no quotes, the path should end with foward slash, and I skip the space after =
If this does not work can you post the set-up you used with with the os ver?
This one seems different because UMS ver. number.
your ums.conf file needs helpDEBUG 2016-07-29 12:05:29.778 [main] LogBack started with configuration file: /opt/ums-6.4.0/logback.headless.xml
Shared folders
no quotes, the path should end with foward slash, and I skip the space after =
Code: Select all
folders = "/media/Ultra/Audio\"
Code: Select all
folders =/media/Ultra/Audio/
Re: UMS Unable To Start
Thanks changed the conf file but no change and I checked the path but I've set it to /etc/ums which is linked to ums-6.4.0 so not sure, I've attached my set-up files.
- Attachments
-
- setup.zip
- (14.38 KiB) Downloaded 796 times
Re: UMS Unable To Start
Could you post a link or set-up you used as reference to build your server.
Thank nyou
Thank nyou
Re: UMS Unable To Start
As I said in my first post it's a Raspberry Pi 2 running Raspbian Jessie in headless mode
Re: UMS Unable To Start
I'm sorry,
The question is not the os build which comes headless or desktop, but most any linux system can run headless.
Did you roll your own UMS sever or follow someones example on setting this up?
The question is not the os build which comes headless or desktop, but most any linux system can run headless.
Did you roll your own UMS sever or follow someones example on setting this up?
Re: UMS Unable To Start
Sure I know but just being clear. I followed a guide online first then the guide posted on here which was basically download, move and set link. I then replaced the init setup with a systemd setup but I can't get either working which I guess since I can't get the script to run manually anyway isn't that surprising (though you provide extra configuration information in running the script with both startup methods so not too sure on that).
Re: UMS Unable To Start
If the system is just a media server, start over. Rebuild Debian use one of the UMS guides on this site.
If not, Remove UMS from the system, then use one of the guides.
If not, Remove UMS from the system, then use one of the guides.