Bug 417 - can't setup the listening port 9000 for the HTTP server: Address already in use
: can't setup the listening port 9000 for the HTTP server: Address already in use
Status: RESOLVED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Web Interface
: 5.x or older
: Other RedHat Linux
: P3 normal (vote)
: ---
Assigned To: Blackketter Dean
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2004-06-27 12:20 UTC by Carsten Bormann
Modified: 2009-09-08 09:18 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Carsten Bormann 2004-06-27 12:20:12 UTC
can't setup the listening port 9000 for the HTTP server: Address already in use at /usr/local/slimserver/
Slim/Web/HTTP.pm line 146.

With Perl 5.6.0, the necessary argument to IO::Socket->new is "Reuse", not "ReuseAddr".
Simple Hack:

        $http_server_socket = HTTP::Daemon->new(
                LocalPort => $listenerport,
                LocalAddr => $listeneraddr,
                Listen    => SOMAXCONN,
                Reuse => 1,       ########## Hack for 5.6.0
                ReuseAddr => 1,

(This has been a bug for a while, I just was too lazy to find it.)
Comment 1 KDF 2004-07-26 22:55:03 UTC
is there any reason not to merge this in?
Comment 2 Carsten Bormann 2004-07-27 02:07:36 UTC
I have used this for a month, with no problems.
Of course, this should receive some testing on other systems, but this is what the development version 
is for, no?
There *should* be no problems on other systems, anyway.
Comment 3 Blackketter Dean 2004-07-27 09:44:10 UTC
I'd like Sean's opinion on this.  I'm concerned that in some cases we'd see success in opening the 
socket, but we wouldn't see any incoming connections.  Sean?
Comment 4 Blackketter Dean 2004-08-12 09:17:53 UTC
Fix should appear in the next nightly build.
Comment 5 Chris Owens 2006-06-16 14:40:23 UTC
There are 536 bugs in the database with targets of '---' that were fixed prior to new year 2006.  I am setting them to targets of 6.2.1 to keep them from showing up in my queries.
Comment 6 Chris Owens 2008-12-18 11:54:01 UTC
Routine bug db maintenance; removing old versions which cause confusion.  I apologize for the inconvenience.