Squeezebox server not reachable port 9000

Max2Play Home 2016 (en) Forums Max2Play as Squeezebox (Player / Server) Squeezebox server not reachable port 9000

Tagged: 

This topic contains 17 replies, has 10 voices, and was last updated by  Udo70 premium 8 months ago.

Viewing 18 posts - 1 through 18 (of 18 total)
  • 12. October 2016 at 10:45 #23380

    Hello
    Max2play last release is working since months on Pi2 & Hifiberry.
    This morning, impossible to launch 9000 port admin web interface
    I tried to reboot the pi, relaunch the service ==> “This site can’t be reached”

    Via the interface, the service is indicating as running

    via SSH, I can see the service running

    netstat -atn or nmap localhost don’t give any open port listining on 9000.

    nmap localhost

    Starting Nmap 6.47 ( http://nmap.org ) at 2016-10-12 10:43 CEST
    Nmap scan report for localhost (127.0.0.1)
    Host is up (0.0032s latency).
    Other addresses for localhost (not scanned): 127.0.0.1
    Not shown: 995 closed ports
    PORT STATE SERVICE
    22/tcp open ssh
    80/tcp open http
    139/tcp open netbios-ssn
    445/tcp open microsoft-ds
    3389/tcp open ms-wbt-server

    I tried to upgrade to last nightly 7.9 build, no effect

    disk/memory seems ok:

    df -h
    Filesystem Size Used Avail Use% Mounted on
    /dev/root 7.1G 2.6G 4.2G 39% /
    devtmpfs 475M 0 475M 0% /dev
    tmpfs 479M 0 479M 0% /dev/shm
    tmpfs 479M 6.7M 473M 2% /run
    tmpfs 5.0M 4.0K 5.0M 1% /run/lock
    tmpfs 479M 0 479M 0% /sys/fs/cgroup
    /dev/mmcblk0p1 60M 20M 41M 34% /boot
    192.168.0.101:/volume1/music 1.8T 1.6T 249G 87% /mnt/music
    tmpfs 96M 4.0K 96M 1% /run/user/1000

    What can I do ? any idea ?

    Thank you

    Thomas

    25. October 2016 at 12:11 #23566

    Just wanted to join in this thread as I am having the same issue. I scan the Pi and can ascertain that it is not listening on port 9000. I cannot figure out how to remove the squeezebox server so I can attempt to reinstall and like the other message above I did attempt to update to the latest nightly build but without success.

    Can anyone help with a resolution to this ?

    Thanks

    Rob

    28. October 2016 at 12:00 #23595

    Hello tparvais and robertcroucher,

    Sorry for the late response.

    Could you both send us the DEBUG information of the Squeezebox Server? The last 50 lines should be enough.

    Best Regards

    3. November 2016 at 23:14 #23659

    Did this get resolved? I have just built a new Pi with Max2Play specifically as a Squeezebox server (I have one as a player already) – I’ve installed the 7.9 nightly build, but when I go to port 9000 I get nothing.

    the DEBUG looks like something is very broken:

    2016-11-03 22:11:25 Logitech Media Server died. Restarting.
    2016-11-03 22:11:30 Logitech Media Server died. Restarting.
    2016-11-03 22:11:35 Logitech Media Server died. Restarting.
    2016-11-03 22:11:40 Logitech Media Server died. Restarting.
    2016-11-03 22:11:45 Logitech Media Server died. Restarting.
    2016-11-03 22:11:50 Logitech Media Server died. Restarting.
    2016-11-03 22:11:55 Logitech Media Server died. Restarting.
    2016-11-03 22:12:00 Logitech Media Server died. Restarting.
    2016-11-03 22:12:05 Logitech Media Server died. Restarting.
    2016-11-03 22:12:10 Logitech Media Server died. Restarting.
    2016-11-03 22:12:15 Logitech Media Server died. Restarting.
    2016-11-03 22:12:20 Logitech Media Server died. Restarting.
    2016-11-03 22:12:25 Logitech Media Server died. Restarting.
    2016-11-03 22:12:30 Logitech Media Server died. Restarting.
    2016-11-03 22:12:35 Logitech Media Server died. Restarting.
    2016-11-03 22:12:40 Logitech Media Server died. Restarting.
    2016-11-03 22:12:45 Logitech Media Server died. Restarting.
    2016-11-03 22:12:50 Logitech Media Server died. Restarting.

    4. November 2016 at 12:09 #23663

    Worked this out and fixed it!

    Although I selected 7.9 nightly, there was a reference to a 7.8 .deb in the box below. The 7.9 wasn’t found, so it installed the 7.8. I found a beta 7.9 on slimdevices website and used that, and all is now working.

    8. November 2016 at 13:18 #23766

    Dear jemhayward,

    Sorry for the late reply
    Nice to hear you could solve the problem on your own. You also can download the Squeezebox Version 7.9 nightly over the Max2Play webinterface. There are 3 different versions of the Squeezebox Server to install on Max2Play.

    Best Regards

    9. November 2016 at 3:50 #23782

    I can confirm that in m2p 2.37 when Nightly 7.9 is selected in the m2p interface, the URL that is shown contains references to 7.8 instead of 7.9. It appears that the URL shown doesn’t change when a build selection is made. Should it?

    Anyway, like jemhayward I found the real URL for 7.9 and pasted it in the box instead and all was well.

    25. November 2016 at 21:46 #24269

    The problem is still there.

    here is the debug

    #### SQUEEZESERVER LOG ####
    [16-11-18 06:25:34.9458] Slim::Web::JSONRPC::requestMethod (443) request not dispatchable!
    [16-11-18 06:25:35.0650] Slim::Web::JSONRPC::requestMethod (443) request not dispatchable!
    [16-11-18 06:26:05.2619] Slim::Web::JSONRPC::requestMethod (443) request not dispatchable!
    [16-11-18 06:26:05.3830] Slim::Web::JSONRPC::requestMethod (443) request not dispatchable!
    [16-11-18 06:26:35.5695] Slim::Web::JSONRPC::requestMethod (443) request not dispatchable!
    [16-11-18 06:26:35.6908] Slim::Web::JSONRPC::requestMethod (443) request not dispatchable!
    
    ............
    2 thosusands similar lines....
    ............
    
    11-18 18:53:13.3375] Slim::Web::JSONRPC::requestMethod (443) request not dispatchable!
    [16-11-18 18:53:43.4440] Slim::Web::JSONRPC::requestMethod (443) request not dispatchable!
    [16-11-18 18:53:43.5671] Slim::Web::JSONRPC::requestMethod (443) request not dispatchable!
    [16-11-18 18:54:13.6680] Slim::Web::JSONRPC::requestMethod (443) request not dispatchable!
    [16-11-18 18:54:13.7958] Slim::Web::JSONRPC::requestMethod (443) request not dispatchable!
    [16-11-18 18:54:43.8933] Slim::Web::JSONRPC::requestMethod (443) request not dispatchable!
    [16-11-18 18:54:44.0115] Slim::Web::JSONRPC::requestMethod (443) request not dispatchable!
    [16-11-18 18:55:14.1111] Slim::Web::JSONRPC::requestMethod (443) request not dispatchable!
    [16-11-18 18:55:14.2292] Slim::Web::JSONRPC::requestMethod (443) request not dispatchable!
    [16-11-18 18:55:44.3328] Slim::Web::JSONRPC::requestMethod (443) request not dispatchable!
    [16-11-18 18:55:44.4547] Slim::Web::JSONRPC::requestMethod (443) request not dispatchable!
    [16-11-18 18:56:14.6558] Slim::Web::JSONRPC::requestMethod (443) request not dispatchable!
    [16-11-18 18:56:14.8036] Slim::Web::JSONRPC::requestMethod (443) request not dispatchable!
    2016-11-18 18:17:12 squeezeboxserver_safe started.
    [16-11-25 20:38:50.3277] main::init (384) Starting Logitech Media Server (v7.9.0, 1475786002, Thu Oct  6 21:13:58 UTC 2016) perl 5.020002 - arm-linux-gnueabihf-thread-multi-64int
    2016-11-25 20:40:39 squeezeboxserver_safe stopped.
    [16-11-25 20:40:40.2192] Slim::Utils::PluginManager::shutdownPlugins (410) Warning: error running Slim::Plugin::UPnP::Plugin->shutdownPlugin: Can't locate object method "shutdown" via package "Slim::Plugin::UPnP::MediaServer" at /usr/share/perl5/Slim/Plugin/UPnP/Plugin.pm line 57.
    2016-11-25 20:40:58 squeezeboxserver_safe started.
    [16-11-25 20:41:30.0065] main::init (384) Starting Logitech Media Server (v7.9.0, 1475786002, Thu Oct  6 21:13:58 UTC 2016) perl 5.020002 - arm-linux-gnueabihf-thread-multi-64int
     
    
    #### PERL VERSION ####
    v5.20.2 
    
    	
    13. January 2017 at 18:03 #25902

    Hi tparvais,
    Sorry about our late response. Please share your setup and the steps you have taken so we can try solve your issue.

    13. January 2017 at 18:17 #25906

    Sorry, I mgigrate to picoreplayer + squeezebox on my synology DS919+, which seems more stable (to be confirmed)

    Maybe I’ll come back to Max2play later on

    tx

    28. January 2017 at 15:33 #26375

    Hi got exactly the same error.

    Thiugh it was linked in new plugin I add. I seems it’s more linked to a restart after a max2playupdate.

    Any leads to solve the issue?

    1. February 2017 at 17:36 #26543

    Hi, all new to M2P and this Forum.

    Just trying to get Squeezebox Server running and this thread looked to be inline to some extent with my problem.

    When I press “Open Squeezebox Server Webadministration” in M2P, i go to ‘http://192.168.1.145:9000/settings/server/wizard.html’,
    trying to feed my e-mail and password I only get error “Invalid mysqueezebox.com username or password.”

    Going to mysqueezebox.com, it works fine logging in with my credientials. Even created a new user at mysqueezebox.com,
    but no change.

    Any clues, help appreciated !

    (( Phi

    1. February 2017 at 17:59 #26544

    Hi Phi et al,
    Please try skipping this step and afterwards heading to the settings of the SBS to enter it manually.

    1. February 2017 at 18:26 #26547

    Hello Heiner,

    Could you be a little bit more specific, please. I am a total beginner here.

    1. SBS = SqueezeBox Server
    2. “Afterwards”? – After what?
    3. How do I enter it manually?

    (( Phi

    2. February 2017 at 9:30 #26553

    Hello Heiner,

    This problem solved. Just did non supported install of SBS 7.8 and then 7.9 again and now it worked !?
    But please answer my questions above, might learn something :o)

    (( Kind regards, Phi

    13. February 2017 at 10:43 #26871

    Hello Heiner and Phil,

    I have the same problem and cannot reach the squeezebox server (nightly 7.9) although it is running. Could you please help me?

    Regards

    Udo70

    13. February 2017 at 16:12 #26898

    @ Udo70

    Could you please give us more details, you cant access the squeezebox server web interface ? and how did you check that its running ?
    what is the port that you are using to access the SBS ?

    Best Regards,
    Mohammad Mbydeen

    16. February 2017 at 19:44 #26996

    Hi Mohammad,

    the max2play webinterface shows the following Status: Squeezebox Server läuft aktuell unter der ProzessID 1266 (SBS is current running under processID 1266)

    The port that I use to access the SBS is 9000 as shown in the url: 192.168.178.30:9000

    Regards

    Udo70

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

You must be logged in to reply to this topic.

Register here