Home of the Squeezebox™ & Transporter® network music players.
Page 1 of 2 12 LastLast
Results 1 to 10 of 11
  1. #1
    Senior Member
    Join Date
    Jan 2007
    Location
    Stockholm, Sweden
    Posts
    340

    Unhappy Can't listen on port 3483

    Hi,
    Please, what should I do about this error?
    SS crashes on boot. I can then start it manually from SSOTS admin page.
    Port 3483 is busy.
    I also notice 'Error while stopping SqueezeCenter' in the log.

    0006: [08-09-18 11:43:15.4832] Slim::Networking::Slimproto::init (129) Warning: Can't listen on port 3483 for Slim protocol: Adressen upptagen at /share/HDA_DATA/SqueezeCenter/Slim/Networking/Slimproto.pm line 129.
    0005: [08-09-18 11:43:03 ] ssctrl SqueezeCenter started.
    0004: [08-09-18 11:42:24 ] ssctrl Command line = /volume1/SSODS/sbin/start-stop-daemon --start --chuid ssods --nicelevel -5 --exec /volume1/SSODS/bin/perl -- /volume1/SqueezeCenter/slimserver.pl --daemon --pidfile /volume1/SqueezeCenter/Cache/squeezecenter.pid --cachedir /volume1/SqueezeCenter/Cache --logdir /volume1/SqueezeCenter/Logs --prefsdir /volume1/SqueezeCenter/prefs --noupnp --httpport 9001
    0003: [08-09-18 11:42:22 ] ssctrl Starting SqueezeCenter 7.1-22170.
    0002: [08-09-14 22:38:21 ] ssctrl Error while stopping SqueezeCenter.
    0001: [08-09-14 22:37:50 ] ssctrl Stopping SqueezeCenter 7.1-22170.
    2* Squeezebox 3
    1* SB Duet
    1* SB Radio
    1 * ReadyNAS Pro

  2. #2
    Senior Member
    Join Date
    Jan 2007
    Location
    Stockholm, Sweden
    Posts
    340
    The command lines look identical, the first is from booting, the other from SSOTS menu.. only the boot one gives an error..?!

    ------------------------

    0136: [08-09-24 18:08:04.8315] Slim::Networking::SqueezeNetwork::Players::_player s_error (146) Unable to get players from SN: Error on HTTP socket: , retrying in 600 seconds
    0135: [08-09-24 18:08:04.1099] Slim::Networking::SqueezeNetwork::_error (417) Unable to login to SN: Error on HTTP socket:
    0134: [08-09-24 18:06:47.9747] Slim::Networking::SqueezeNetwork::Players::_player s_error (146) Unable to get players from SN: Connect timed out: , retrying in 300 seconds
    0133: [08-09-24 18:06:46.0381] Slim::Networking::SqueezeNetwork::PrefSync::_init_ error (123) Unable to get list of prefs to sync with SqueezeNetwork, sync is disabled: Connect timed out:
    0132: [08-09-24 18:04:15 ] ssctrl SqueezeCenter started.
    0131: [08-09-24 18:03:42 ] ssctrl Command line = /volume1/SSODS/sbin/start-stop-daemon --start --chuid ssods --nicelevel -5 --exec /volume1/SSODS/bin/perl -- /volume1/SqueezeCenter/slimserver.pl --daemon --pidfile /volume1/SqueezeCenter/Cache/squeezecenter.pid --cachedir /volume1/SqueezeCenter/Cache --logdir /volume1/SqueezeCenter/Logs --prefsdir /volume1/SqueezeCenter/prefs --noupnp --httpport 9001
    0130: [08-09-24 18:03:41 ] ssctrl Starting SqueezeCenter 7.2-22900.
    0129: [08-09-24 18:01:26.0340] Slim::Networking::Slimproto::init (135) Warning: Can't listen on port 3483 for Slim protocol: Adressen upptagen at /share/HDA_DATA/SqueezeCenter/Slim/Networking/Slimproto.pm line 135.
    0128: [08-09-24 18:01:14 ] ssctrl SqueezeCenter started.
    0127: [08-09-24 18:00:34 ] ssctrl Command line = /volume1/SSODS/sbin/start-stop-daemon --start --chuid ssods --nicelevel -5 --exec /volume1/SSODS/bin/perl -- /volume1/SqueezeCenter/slimserver.pl --daemon --pidfile /volume1/SqueezeCenter/Cache/squeezecenter.pid --cachedir /volume1/SqueezeCenter/Cache --logdir /volume1/SqueezeCenter/Logs --prefsdir /volume1/SqueezeCenter/prefs --noupnp --httpport 9001
    0126: [08-09-24 18:00:32 ] ssctrl Starting SqueezeCenter 7.2-22900.
    0125: [08-09-22 20:50:08 ] ssctrl SqueezeCenter stopped.
    0124: [08-09-22 20:50:03 ] ssctrl Stopping SqueezeCenter 7.2-22900.
    Last edited by sand; 2008-09-24 at 09:38. Reason: added log rows
    2* Squeezebox 3
    1* SB Duet
    1* SB Radio
    1 * ReadyNAS Pro

  3. #3
    Being unable to listen on a port means that there is another process present that is already listening on that port. To view which processes are running on the Qnap log in using SSH and type ps aux. You will find at least two copies of slimserver.pl running. It is normal for several copies of some processes to be running at the same time - for instance, my NAS (also a TS-109) lists 6 instances of apache. Note that it is possible to get rid of all copies of a given process using the killall command, e.g. killall slimserver.pl

    A couple of troubleshooting ideas:

    Are there some components of SC hanging around from an earlier version that was not fully uninstalled?

    Does the situation happen after rebooting the TS-109? (A reboot might well fix the problem entirely).

    Steve

  4. #4
    Senior Member
    Join Date
    Jan 2007
    Location
    Stockholm, Sweden
    Posts
    340
    Thank you for your comments, sdhubbard!

    I have restarted several times, both from the web and using the power button on the unit. I have also once stopped SC before shutting down, just in case..

    How can I find any earlier versions?
    2* Squeezebox 3
    1* SB Duet
    1* SB Radio
    1 * ReadyNAS Pro

  5. #5
    Quote Originally Posted by sand View Post
    .

    How can I find any earlier versions?
    Earlier versions of SqueezeCenter may be downloaded by pointing your browser to http://downloads.slimdevices.com/

    The version of the file to go for is the .tgz version.

    If you have files from the 'Progressive' installation of Slimserver 6.5.x hanging around, uninstallation instructions can be found at http://ripcaster.co.uk/node/112
    If you get an error about unmounting file systems just run the uninstallation script again. An easy way to see if this older installation is present, is to look for a directory called 'etch', as this is where the subsystem installed by the Progressive version lives.

    Although SSOTS will upgrade SqueezeCenter, it won't downgrade - you have to remove the newer version of SqueezeCenter first.

    Steve

  6. #6
    Senior Member
    Join Date
    Jan 2007
    Location
    Stockholm, Sweden
    Posts
    340

    Red face

    Thanks. The problem seems to have solved itself somehow.. I have now booted three times witohut getting this error anymore..
    2* Squeezebox 3
    1* SB Duet
    1* SB Radio
    1 * ReadyNAS Pro

  7. #7
    Senior Member
    Join Date
    Jan 2007
    Location
    Stockholm, Sweden
    Posts
    340

    Angry

    OMG, the error is back!!

    0841: [08-09-30 08:49:30.1402] Slim::Networking::Slimproto::init (135) Warning: Can't listen on port 3483 for Slim protocol: Adressen upptagen at /share/HDA_DATA/SqueezeCenter/Slim/Networking/Slimproto.pm line 135.
    2* Squeezebox 3
    1* SB Duet
    1* SB Radio
    1 * ReadyNAS Pro

  8. #8
    Senior Member
    Join Date
    Jan 2007
    Location
    Stockholm, Sweden
    Posts
    340
    As suggested by mherger - thank you for the tip - I will use netstat to find what process is using the port.
    This is what I get now, after starting SC manually from SSOTS.

    I notice there are two rows "QNAP:3883", I wonder if that is normal.


    login as: admin
    admin@192.168.1.4's password:
    [~] # man netstat
    -sh: man: command not found
    [~] # netstat
    Active Internet connections (w/o servers)
    Proto Recv-Q Send-Q Local Address Foreign Address State
    tcp 0 0 localhost:1214 localhost:9092 ESTABLISHED
    tcp 0 0 QNAP:3483 192.168.1.5:46602 ESTABLISHED
    tcp 0 52 QNAP:ssh 192.168.1.3:2495 ESTABLISHED
    tcp 0 0 QNAP:9001 192.168.1.3:2462 TIME_WAIT
    tcp 0 0 localhost:9092 localhost:1214 ESTABLISHED
    tcp 0 0 QNAP:3483 192.168.1.2:44900 ESTABLISHED
    udp 0 0 localhost:1024 localhost:syslog ESTABLISHED
    udp 0 0 localhost:1025 localhost:syslog ESTABLISHED
    Active UNIX domain sockets (w/o servers)
    Proto RefCnt Flags Type State I-Node Path
    [~] #
    2* Squeezebox 3
    1* SB Duet
    1* SB Radio
    1 * ReadyNAS Pro

  9. #9
    Senior Member
    Join Date
    Oct 2005
    Location
    Ireland
    Posts
    15,330
    They could be "old" connections to SB not cleared down - I think some TCP connections won't be clear until all data is sent from buffers. I've seen this happen with Softsqueeze.

    Reset one of your SB's and see if one of the 3483 disappears.

  10. #10
    Senior Member
    Join Date
    Jan 2007
    Location
    Stockholm, Sweden
    Posts
    340
    Doh, I didn't read properly.. those are my two SB3's!
    So this probably has nothing to do with the port being busy on boot?
    Or are the SB3's to blaim?

    > tcp 0 0 QNAP:3483 192.168.1.5:46602
    > tcp 0 0 QNAP:3483 192.168.1.2:44900
    2* Squeezebox 3
    1* SB Duet
    1* SB Radio
    1 * ReadyNAS Pro

Posting Permissions

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