[SOLVED] Squeezebox Server not installing… file doesn’t exist?

Max2Play Home 2016 (en) Forums Max2Play on Raspberry PI [SOLVED] Squeezebox Server not installing… file doesn’t exist?

Tagged: 

This topic contains 17 replies, has 3 voices, and was last updated by  Heiner Moderator 1 year, 6 months ago.

Viewing 18 posts - 1 through 18 (of 18 total)
  • 28. Februar 2018 at 2:18 #34126

    Ok I need some help!
    I have a Raspberry Pi 3B… set it up about a month ago to replace an old 1B that quit working.
    Everything was working fine… Max2Play 2.45 with Squeezebox Server 7.9… until a few days ago when I could no longer access the Web Administration page. Checked the debug log and it kept saying that the LMS was dying, something like that.
    Last night I reimaged my MicroSD, reinstalled Max2Play, updated to 2.45. But when I tried to install LMS, it would start unpacking and then the yellow box would disappear. I could briefly see an error saying the LMS file did not exist before it disappeared.
    Today I bought a new MicroSD (SanDisk 32G) thinking my old one might have been corrupted. Have not installed Max2Play and updated to 2.45… but the same thing is happening when I try to install LMS. I’ve tried 7.9.0 and the nightly 7.9.
    I can’t figure out what is going wrong… is there something wrong with my Pi?
    Any help is greatly appreciated!
    Brad

    28. Februar 2018 at 2:31 #34127

    For curiosity’s sake I just reimaged the SD card with the Stretch beta version of Max2Play… same problem. „LMS Version does not exist.“
    Anyone else running into this problem???

    28. Februar 2018 at 2:44 #34128

    Hmmmm
    After the failed install, Max2Play does say this:

    Status: Squeezebox Server is running with processID 6115

    But when I try to access the web interface at :9000, there is nothing there.

    The Debug log now says this:

    #### SQUEEZESERVER LOG ####
    2018-02-28 01:39:48 squeezeboxserver_safe started.
    2018-02-28 01:39:53 Logitech Media Server died. Restarting.
    2018-02-28 01:39:58 Logitech Media Server died. Restarting.
    2018-02-28 01:40:03 Logitech Media Server died. Restarting.
    2018-02-28 01:40:08 Logitech Media Server died. Restarting.
    2018-02-28 01:40:13 Logitech Media Server died. Restarting.
    2018-02-28 01:40:18 Logitech Media Server died. Restarting.
    2018-02-28 01:40:23 Logitech Media Server died. Restarting.
    2018-02-28 01:40:28 Logitech Media Server died. Restarting.
    2018-02-28 01:40:33 Logitech Media Server died. Restarting.
    2018-02-28 01:40:38 squeezeboxserver_safe stopped.
    2018-02-28 01:40:39 squeezeboxserver_safe started.
    2018-02-28 01:40:44 Logitech Media Server died. Restarting.
    2018-02-28 01:40:49 Logitech Media Server died. Restarting.
    2018-02-28 01:40:54 squeezeboxserver_safe stopped.
    2018-02-28 01:41:09 squeezeboxserver_safe started.
    2018-02-28 01:41:15 Logitech Media Server died. Restarting.
    2018-02-28 01:41:20 Logitech Media Server died. Restarting.
    2018-02-28 01:41:25 squeezeboxserver_safe stopped.
    2018-02-28 01:41:25 squeezeboxserver_safe started.
    2018-02-28 01:41:30 Logitech Media Server died. Restarting.
    2018-02-28 01:41:35 Logitech Media Server died. Restarting.

    #### PERL VERSION ####
    v5.24.1

    28. Februar 2018 at 2:54 #34129

    Managed to get a couple of screenshots
    When trying to install LMS, the process gets this far:
    Screen_Shot_2018_02_27_at_7_49_17_PM
    then very quickly changes to this before it disappears:
    Screen Shot 2018 02 27

    (sorry for all the edits, took me a while to figure out how to post the pics!)

    • This reply was modified 2 years, 10 months ago by  bigsur78.
    • This reply was modified 2 years, 10 months ago by  bigsur78.
    • This reply was modified 2 years, 10 months ago by  bigsur78.
    • This reply was modified 2 years, 10 months ago by  bigsur78.
    • This reply was modified 2 years, 10 months ago by  bigsur78.
    28. Februar 2018 at 3:09 #34135

    Last post….
    Debug log now saying this over and over:

    [18-02-28 01:48:32.7458] Slim::Schema::forceCommit (2149) Warning: Trying to commit transactions before DB is initialized!
    [18-02-28 01:48:33.0512] main::checkDataSource (1110) Warning: Schema updated or no media found in the database, initiating scan.
    [18-02-28 01:48:37.1679] Slim::Utils::SQLiteHelper::postConnect (374) Optimizing DB because of missing or empty sqlite_stat1 table
    [18-02-28 01:48:37.1874] Slim::Schema::forceCommit (2149) Warning: Trying to commit transactions before DB is initialized!
    2018-02-28 01:49:02 squeezeboxserver_safe stopped.
    2018-02-28 01:49:21 squeezeboxserver_safe started.

    Please help! Much appreciated
    B

    • This reply was modified 2 years, 10 months ago by  bigsur78.
    28. Februar 2018 at 17:08 #34146

    Hi bigsur78,

    The last log should not be a problem at all.

    Did your install show the button to open the web interface after installation in this last instance?

    28. Februar 2018 at 19:15 #34149

    It did show the button but when I click on it it tries to go to :9000 and finds nothing.
    I’m at work now so can’t do anything with it right now. Thanks for your time!

    1. März 2018 at 13:35 #34158

    Hi bigsur,

    Firstly, try running a reboot and clicking the button again. If you still cannot access the interface, something went wrong in the installation.

    Then, please reinstall LMS and select the other version to make sure the issue is not connected to the nightly.

    1. März 2018 at 15:11 #34163

    Hi Heiner
    After many reboots/reimages/reinstalls, I finally got it to work last night.
    Ended up with the Stretch beta of Max2Play and the nightly build.
    Not sure why I had so much trouble!
    Thanks for your help.
    B

    2. März 2018 at 13:01 #34178

    Hi bigsur,

    Sorry for the trouble, it should not be such a hassle.

    Glad you got it working, though 🙂

    17. Juni 2019 at 23:36 #45814

    Hi
    I have the exact same issue – can’t reach LMS on port 9000, tried removing LMS and then re-installing. At the end of install, the log says „LMS version does not exist“.

    Help please.
    Thanks
    Matej

    18. Juni 2019 at 12:27 #45854

    Hello Matej,

    Please make sure the line below the installer has a URL in it when clicking „install“. Please paste the last lines from the installation text afterwards if the server still does not run properly.

    18. Juni 2019 at 23:33 #45866

    Nope, doesn’t work.

    URL was below the installer, and I wanted to attach the picture of last lines, but I can’t for some reason.

    Anyway, last lines are the same as with bigsur, a couple of posts above.

    19. Juni 2019 at 12:18 #45868

    Might be an issue with the availability of the slimdevices servers we get the install files from. I’m pretty sure that was the case in bigsur’s error. Have you tried again today?

    27. Juni 2019 at 0:19 #45944

    Hi Heiner

    I’ve been trying day after day, with all three available LMS versions. It’s not the slimdevices availability, as the install package gets downloaded, installation seems to go all right, but at the end I receive the same message how LMS version does not exist.

    Funnily, max2play interface says that SqueezeBox Server is running with procesID 28408.
    When I run ps command, there seem to be TWO SqueezeBox processes:
    – one I mentioned above – 28408, for which time running is 0
    – another one – 28413, which was running for some time

    See the „ps aux output“ (I trimmed it down obviously)

    squeeze+ 28408 0.0 0.5 6700 2752 ? S 00:02 0:00 /bin/bash /usr/sbin/squeezeboxserver_safe /usr/sbin/squeezeboxserver –prefsdir /var/lib/squeezeboxserver/prefs –logdir /var/log/squeezeboxserver

    squeeze+ 28413 0.6 15.0 84604 76384 ? S 00:02 0:05 /usr/bin/perl /usr/sbin/squeezeboxserver –prefsdir /var/lib/squeezeboxserver/prefs –logdir /var/log/squeezeboxserver/ –cachedir /var/lib/squeez

    There is something really odd going on here I think, it’d be good to hear your thoughts.

    Thanks
    Matej

    27. Juni 2019 at 0:39 #45945

    Additionaly, running „lsof -i -P -n“ shows this (nothing on port 9000):

    [email protected]:~ $ sudo lsof -i -P -n
    COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
    avahi-dae 369 avahi 12u IPv4 10108 0t0 UDP *:5353
    avahi-dae 369 avahi 13u IPv6 10109 0t0 UDP *:5353
    avahi-dae 369 avahi 14u IPv4 10110 0t0 UDP *:44467
    avahi-dae 369 avahi 15u IPv6 10111 0t0 UDP *:48280
    sshd 456 root 3u IPv4 16517 0t0 TCP *:22 (LISTEN)
    sshd 456 root 4u IPv6 16519 0t0 TCP *:22 (LISTEN)
    apache2 487 root 3u IPv4 13426 0t0 TCP *:80 (LISTEN)
    nmbd 492 root 16u IPv4 11875 0t0 UDP *:137
    nmbd 492 root 17u IPv4 11876 0t0 UDP *:138
    nmbd 492 root 18u IPv4 15623 0t0 UDP 192.168.1.5:137
    nmbd 492 root 19u IPv4 15624 0t0 UDP 192.168.1.255:137
    nmbd 492 root 20u IPv4 15625 0t0 UDP 192.168.1.5:138
    nmbd 492 root 21u IPv4 15626 0t0 UDP 192.168.1.255:138
    apache2 547 www-data 3u IPv4 13426 0t0 TCP *:80 (LISTEN)
    apache2 548 www-data 3u IPv4 13426 0t0 TCP *:80 (LISTEN)
    apache2 549 www-data 3u IPv4 13426 0t0 TCP *:80 (LISTEN)
    apache2 550 www-data 3u IPv4 13426 0t0 TCP *:80 (LISTEN)
    apache2 551 www-data 3u IPv4 13426 0t0 TCP *:80 (LISTEN)
    smbd 911 root 33u IPv6 13226 0t0 TCP *:445 (LISTEN)
    smbd 911 root 34u IPv6 13227 0t0 TCP *:139 (LISTEN)
    smbd 911 root 35u IPv4 13228 0t0 TCP *:445 (LISTEN)
    smbd 911 root 36u IPv4 13229 0t0 TCP *:139 (LISTEN)
    dhclient 967 root 9u IPv4 14730 0t0 UDP *:68
    apache2 1274 www-data 3u IPv4 13426 0t0 TCP *:80 (LISTEN)
    apache2 1469 www-data 3u IPv4 13426 0t0 TCP *:80 (LISTEN)
    apache2 1470 www-data 3u IPv4 13426 0t0 TCP *:80 (LISTEN)
    apache2 1471 www-data 3u IPv4 13426 0t0 TCP *:80 (LISTEN)
    apache2 1472 www-data 3u IPv4 13426 0t0 TCP *:80 (LISTEN)
    sshd 1587 root 3u IPv4 19583 0t0 TCP 192.168.1.5:22->192.168.1.2:50445 (ESTABLISHED)
    sshd 1598 pi 3u IPv4 19583 0t0 TCP 192.168.1.5:22->192.168.1.2:50445 (ESTABLISHED)

    27. Juni 2019 at 0:42 #45946

    And then, finally, /var/log/squeezeboxerver/server.log just keeps repeating the same message:

    2019-06-27 00:39:33 Logitech Media Server died. Restarting.
    2019-06-27 00:39:38 Logitech Media Server died. Restarting.
    2019-06-27 00:39:43 Logitech Media Server died. Restarting.
    2019-06-27 00:39:48 Logitech Media Server died. Restarting.
    2019-06-27 00:39:53 Logitech Media Server died. Restarting.
    2019-06-27 00:39:58 Logitech Media Server died. Restarting.
    2019-06-27 00:40:03 Logitech Media Server died. Restarting.
    2019-06-27 00:40:08 Logitech Media Server died. Restarting.

    EDIT: Although, when I re-install, server stops dying, but I still can’t access the 9000 port.

    • This reply was modified 1 year, 6 months ago by  Matej.jurkic.
    27. Juni 2019 at 10:32 #45952

    Hi Matej,

    This is indeed odd. Did you do anything else manually on the system?

    Please burn a new image and see if you can recreate the error. If so, please copy-paste the error you get when first starting the LMS after reboot (wait 1-2 min).

Viewing 18 posts - 1 through 18 (of 18 total)

You must be logged in to reply to this topic.

Register here