Home of the Squeezebox™ & Transporter® network music players.
Page 1 of 2 12 LastLast
Results 1 to 10 of 20
  1. #1
    Junior Member
    Join Date
    Nov 2017
    Posts
    9

    LMS problem on debian jessie

    Hey there

    I having a problem with the logitech media server on my debian jessie/openmediavault 3.0.90 installation.

    I set up a few systems and never had a problem with LMS. But this time it doesen't want to run.

    I installed LMS like described on this page wiki.slimdevices.com/index.php/DebianPackage
    I tried all versions. Everytime, the installation succeds, the server starts correctly.

    Code:
    ~# sudo service logitechmediaserver status
    ● logitechmediaserver.service - LSB: Startup script for the Logitech Media Server
       Loaded: loaded (/etc/init.d/logitechmediaserver)
       Active: active (exited) since Do 2017-11-02 17:43:03 CET; 3s ago
      Process: 15052 ExecStop=/etc/init.d/logitechmediaserver stop (code=exited, status=0/SUCCESS)
      Process: 15088 ExecStart=/etc/init.d/logitechmediaserver start (code=exited, status=0/SUCCESS)
    
    Nov 02 17:43:03 DMW-NAS logitechmediaserver[15088]: Making sure that Logitech Media Server is not running first: Starting Logitech Media Server.
    Nov 02 17:43:03 DMW-NAS systemd[1]: Started LSB: Startup script for the Logitech Media Server.
    Hint: Some lines were ellipsized, use -l to show in full.
    But i can't find the server. There is nothing on the port 9000.
    Code:
    netstat -a
    Netstat also gives me no entry. There is no logitech media server uses any port.

    Do you have any ideas, what the problem could be?
    Is there a permission failure?

    Any help would be nice

    Thanks in advance

  2. #2
    Senior Member
    Join Date
    Feb 2013
    Posts
    368
    Any one of netstat, ps, top, htop at the CLI should confirm if LMS is running and on what ports on your system. Jessie/OMV uses systemd so it's better to use systemctl commands, e.g. systemctl status logitechmediaserver, systemctl restart logitechmediaserver, etc. Assuming you have enabled ssh access to Jessie/OMV command line.

    In OMV you could also use the webui to look at the running process, I would expect perl to be in the list. Using "netstat -plant" as root should show a perl program is listening on 127.0.0.1:9000 in a default LMS setup, but you say it is not. Use something like "ps aux | grep squeeze" to show if slimserver.pl is actually running.

    Generally I just tend to grab the latest 64-bit deb package from http://downloads.slimdevices.com and install using "dpkg -i". What does "dpkg -l" show?
    Last edited by Krisbee; 2017-11-02 at 12:04.

  3. #3
    Junior Member
    Join Date
    Nov 2017
    Posts
    9
    I installed it via dpgk -i. The newest version they published.7.9
    dpgk -l listet it correctly:
    Code:
    ii  logitechmediaserver            7.9.1~1509357021     all                  Streaming Audio Server
    When I enter systemctl logitech media server is listet as active:
    Code:
    systemctl status logitechmediaserver
    ● logitechmediaserver.service - LSB: Startup script for the Logitech Media Server
       Loaded: loaded (/etc/init.d/logitechmediaserver)
       Active: active (exited) since Sa 2017-11-04 16:20:34 CET; 10min ago
    
    Nov 04 16:20:29 DMW-NAS logitechmediaserver[1198]: Making sure that Logitech Media Server is not running first: Starting Logitech Media Server.
    Nov 04 16:20:34 DMW-NAS systemd[1]: Started LSB: Startup script for the Logitech Media Server.
    Hint: Some lines were ellipsized, use -l to show in full.
    Netstat -plant shows no perl or lms entry:
    Code:
    Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
    tcp        0      0 127.0.0.1:40233         0.0.0.0:*               LISTEN      2112/Plex Plug-in [
    tcp        0      0 127.0.0.1:3306          0.0.0.0:*               LISTEN      1809/mysqld     
    tcp        0      0 127.0.0.1:6379          0.0.0.0:*               LISTEN      1279/redis-server 1
    tcp        0      0 0.0.0.0:32400           0.0.0.0:*               LISTEN      1317/Plex Media Ser
    tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      1356/nginx -g daemo
    tcp        0      0 127.0.0.1:32401         0.0.0.0:*               LISTEN      1317/Plex Media Ser
    tcp        0      0 0.0.0.0:30033           0.0.0.0:*               LISTEN      1273/ts3server  
    tcp        0      0 0.0.0.0:32469           0.0.0.0:*               LISTEN      2109/Plex DLNA Serv
    tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1181/sshd       
    tcp        0      0 0.0.0.0:33400           0.0.0.0:*               LISTEN      2112/Plex Plug-in [
    tcp        0      0 127.0.0.1:32600         0.0.0.0:*               LISTEN      2110/Plex Tuner Ser
    tcp        0      0 0.0.0.0:10011           0.0.0.0:*               LISTEN      1273/ts3server  
    tcp        0      0 0.0.0.0:91              0.0.0.0:*               LISTEN      1356/nginx -g daemo
    tcp        0      0 127.0.0.1:4700          0.0.0.0:*               LISTEN      1351/cnid_metad 
    tcp        0      0 127.0.0.1:33757         0.0.0.0:*               LISTEN      2184/Plex Plug-in [
    tcp        0      0 127.0.0.1:40669         0.0.0.0:*               LISTEN      2057/Plex Plug-in [
    tcp        0      0 0.0.0.0:1406            0.0.0.0:*               LISTEN      2109/Plex DLNA Serv
    tcp        0      0 0.0.0.0:33443           0.0.0.0:*               LISTEN      2112/Plex Plug-in [
    tcp        0      0 127.0.0.1:46252         127.0.0.1:6379          TIME_WAIT   -               
    tcp        0      0 192.168.178.100:80      192.168.178.47:60008    TIME_WAIT   -               
    tcp        0      0 192.168.178.100:91      192.168.178.47:59972    VERBUNDEN   1359/nginx: worker 
    tcp        1      0 127.0.0.1:50922         127.0.0.1:40669         CLOSE_WAIT  2109/Plex DLNA Serv
    tcp        0    196 192.168.178.100:22      192.168.178.47:59971    VERBUNDEN   2176/0          
    tcp        0      0 192.168.178.100:80      192.168.178.47:60024    VERBUNDEN   1360/nginx: worker 
    tcp        0      0 192.168.178.100:80      192.168.178.47:60051    TIME_WAIT   -               
    tcp        0      0 192.168.178.100:80      192.168.178.47:60050    TIME_WAIT   -               
    tcp6       0      0 :::22                   :::*                    LISTEN      1181/sshd       
    tcp6       0      0 :::91                   :::*                    LISTEN      1356/nginx -g daemo
    tcp6       0      0 :::548                  :::*                    LISTEN      1350/afpd
    Finally the ps aux line:
    Code:
    s aux | grep squeeze
    root      4873  0.0  0.0  12748  2048 pts/0    R+   16:31   0:00 grep squeeze
    Reinstalling the package doesen't change anything.

    Maybe a permisson problem? Maybe the script is not allowed to allocate the socket? Is there a way to change in script, so he choose a diffrent port?

  4. #4
    Senior Member
    Join Date
    Feb 2013
    Posts
    368
    I have OMV running in Vbox as a test, but cannot reproduce your error.

    I downloaded LMS directly

    Code:
    root@omv-vm:/# wget -c http://downloads.slimdevices.com/nightly/7.9/sc/c558cb2/logitechmediaserver_7.9.1~1509357021_amd64.deb
    last step of script you used is just a "dpkg -i":

    Code:
    root@omv-vm:~# dpkg -i logitechmediaserver_7.9.1~1509357021_amd64.deb
    LMS seems to install and start normally

    Code:
    root@omv-vm:~# systemctl status logitechmediaserver
    ● logitechmediaserver.service - LSB: Startup script for the Logitech Media Server
       Loaded: loaded (/etc/init.d/logitechmediaserver; generated; vendor preset: enabled)
       Active: active (running) since Sat 2017-11-04 19:51:09 GMT; 48s ago
         Docs: man:systemd-sysv-generator(8)
          CPU: 3ms
       CGroup: /system.slice/logitechmediaserver.service
               ├─4205 /bin/bash /usr/sbin/squeezeboxserver_safe /usr/sbin/squeezeboxserver --prefsdir /var/lib/squeezeboxserver/prefs --logdir /var/log/squeezebo
               └─4207 /usr/bin/perl /usr/sbin/squeezeboxserver --prefsdir /var/lib/squeezeboxserver/prefs --logdir /var/log/squeezeboxserver/ --cachedir /var/lib
    
    Nov 04 19:51:09 omv-vm systemd[1]: Starting LSB: Startup script for the Logitech Media Server...
    Nov 04 19:51:09 omv-vm logitechmediaserver[4199]: Making sure that Logitech Media Server is not running first: No process in pidfile '/var/run/logitechmedias
    Nov 04 19:51:09 omv-vm logitechmediaserver[4199]: Starting Logitech Media Server.
    Nov 04 19:51:09 omv-vm systemd[1]: Started LSB: Startup script for the Logitech Media Server
    Code:
    root@omv-vm:~# netstat -plant | grep perl
    tcp        0      0 0.0.0.0:3483            0.0.0.0:*               LISTEN      4207/perl           
    tcp        0      0 0.0.0.0:9090            0.0.0.0:*               LISTEN      4207/perl           
    tcp        0      0 0.0.0.0:9000            0.0.0.0:*               LISTEN      4207/perl           
    tcp        0      0 0.0.0.0:36521           0.0.0.0:*               LISTEN      4207/perl
    I see you have plex running, but I'm not aware that should stop LMS from working. I assume you've looked at /var/log/apt/history.log and /var/log/apt/term.log for anything odd. What about starting slimserver.pl in debug mode as a non root user? Apart from that I don't have any other ideas right now.

    It shouldn't be necessary, but you can run LMS using docker on OMV with https://github.com/snoopy86/logitechmediaserver for example.
    Last edited by Krisbee; 2017-11-04 at 13:17.

  5. #5
    Senior Member
    Join Date
    Apr 2008
    Location
    Paris, France
    Posts
    2,109
    Maybe have a look at "journalctl -xl"?
    Or see what that logitechmediaserver service unit launches and try it on the command-line.

    BTW, on my debian jessie machine, I have a systemV init file, at /etc/init.d/logitechmediaserver
    I think a systemd unit gets automatically generated from that.
    Last edited by epoch1970; 2017-11-04 at 13:21.
    3 SB 3 • Libratone Loop, Zipp Mini • iPeng (iPhone + iPad) • LMS 7.9 (linux) with plugins: CD Player, WaveInput, Triode's BBC iPlayer by bpa • IRBlaster by Gwendesign (Felix) • Server Power Control by Gordon Harris • Smart Mix, Music Walk With Me, What Was That Tune? by Michael Herger • PowerSave by Jason Holtzapple • Song Info, Song Lyrics by Erland Isaksson • AirPlay Bridge by philippe_44 • WeatherTime by Martin Rehfeld • Auto Dim Display, SaverSwitcher, ContextMenu by Peter Watkins.

  6. #6
    Senior Member DJanGo's Avatar
    Join Date
    Sep 2005
    Location
    Germany
    Posts
    2,371
    Quote Originally Posted by phanter View Post
    Hey there

    I having a problem with the logitech media server on my debian jessie/openmediavault 3.0.90 installation.
    What exact ISO did you install ?
    Debian Jessie or openmediavault 3.0.90 ?

    What are the contents of the server.log

    Which Perl is installed?

    What Architekture ?

  7. #7
    Junior Member
    Join Date
    Nov 2017
    Posts
    9
    I also dont knwo where er failure comes from. I installed the machine a couple of times and two times and i had this strange behaviour. The other times everything ran smooth without problems.

    @ DJanGo
    ISO: Fresh install Openmediavault 3.0.86 and then updated to 3.0.90
    Perl: v5.20.2 x86_64-linux-gnu-thread-multi
    Architecture: x86 machine Pentium G4560 Quadcore 64bit system

    Sqeeueboxserver has no log in his folder (/var/log/squeezeboxserver).
    You mean the syslog file in /var/log? Should i upload the complete file?
    I found several entrys with lms. Most of the time i restarted the process.
    Code:
    Nov  5 12:52:35 DMW-NAS systemd[1]: Starting LSB: Startup script for the Logitech Media Server...
    Nov  5 12:52:35 DMW-NAS logitechmediaserver[15736]: Making sure that Logitech Media Server is not running first: Starting Logitech Media Server.
    Nov  5 12:52:35 DMW-NAS systemd[1]: Started LSB: Startup script for the Logitech Media Server.
    My thoughts so far: I think the process does not start perl. Perl keeps silent. I just reinstalled perl, but no change.

    @krisbee

    My status output seems a little bit diffrent, but i do not know, if it is important
    Code:
    systemctl status logitechmediaserver
    ● logitechmediaserver.service - LSB: Startup script for the Logitech Media Server
       Loaded: loaded (/etc/init.d/logitechmediaserver)
       Active: active (exited) since So 2017-11-05 12:53:00 CET; 7s ago
      Process: 15777 ExecStop=/etc/init.d/logitechmediaserver stop (code=exited, status=0/SUCCESS)
      Process: 15783 ExecStart=/etc/init.d/logitechmediaserver start (code=exited, status=0/SUCCESS)
    
    Nov 05 12:53:00 DMW-NAS logitechmediaserver[15783]: Making sure that Logitech Media Server is not running first:...ver.
    Nov 05 12:53:00 DMW-NAS systemd[1]: Started LSB: Startup script for the Logitech Media Server.
    Hint: Some lines were ellipsized, use -l to show in full.
    Maybe i try it with docker.

  8. #8
    Senior Member DJanGo's Avatar
    Join Date
    Sep 2005
    Location
    Germany
    Posts
    2,371
    Quote Originally Posted by phanter View Post
    Sqeeueboxserver has no log in his folder (/var/log/squeezeboxserver).

    Aaaahh - now we knew what to do....


    Code:
    sudo mkdir /var/log/squeezeboxserver
    sudo chown squeezeboxserver:nogroup /var/log/squeezeboxserver
    \edit
    and of course...

    Code:
    sudo systemctl start logitechmediaserver.service
    /edit
    Last edited by DJanGo; 2017-11-05 at 09:28.

  9. #9
    Senior Member DJanGo's Avatar
    Join Date
    Sep 2005
    Location
    Germany
    Posts
    2,371
    just a Moment...

    Quote Originally Posted by phanter View Post
    Sqeeueboxserver has no log in his folder (/var/log/squeezeboxserver).
    Has no log - means folder is there but empty or folder not there?

    If there is no folder - see my other comment.

    If there is a folder - i would ask you to check the permissions
    Code:
    ls -l /var/log/squeezeboxserver
    If that doesnt match squeezeboxserver nogroup /var/log/squeezeboxserver
    then you need only the 2.nd command...

    Code:
    sudo chown squeezeboxserver:nogroup /var/log/squeezeboxserver

  10. #10
    Junior Member
    Join Date
    Nov 2017
    Posts
    9
    @ DJanGo

    I set the permisson manually like you described.

    Code:
    sudo chown squeezeboxserver:nogroup /var/log/squeezeboxserver
    But the process does not write anything in the log.

    For now it is very annoying to deal with this strange error. I'm thinking about to do a clean install. I do not where this failure come from. In a row of six diffrent installs, two times i got this strange errors. Four times everything runs without problems. Same system and same settings.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •