[CalendarServer-users] Service exists at only 127.0.0.1

Cyrus Daboo cdaboo at apple.com
Wed Jan 30 18:02:54 PST 2008


Hi Robert,

--On January 31, 2008 12:08:47 AM +0000 Robert Harris 
<robert.harris at manville-harris.co.uk> wrote:

> Pointing my browser to 127.0.0.1:8009 appears to work. Port 8008
> doesn't work:
>
> $ telnet 127.0.0.1 8008
> Trying 127.0.0.1...
> telnet: connect to address 127.0.0.1: Connection refused
> telnet: Unable to connect to remote host
> $
>
> Similarly, a connection to 192.168.0.101:8009 is refused.
> However, a connection to 192.168.0.101:8008 succeeds

That is expected in some cases. Specifically on a multi core system, the 
server will run several processes listening on localhost at ports 8009, 
8010, 8011 etc. It will then run a load balancer on the "normal" port 8008 
which will redirect to the local ones as appropriate.

> but is dropped. E.g.
>
> $ telnet 192.168.0.101 8008
> Trying 192.168.0.101...
> Connected to 192.168.0.101.
> Escape character is '^]'.
> GET /
>
>
> Connection closed by foreign host.
> $
>
> After shutting down the server (i.e. sending 'run' a ctrl-C), connections
> are refused to all of the above connections/ports.
>
> There is no error file in logs/ , and there seems to be nothing
> appropriate on stdout/stderr .
>
> Any pointers would be gratefully received.

Can you include the stdout/stderr result? There ought to be something in 
there when the server starts up that shows what processes are being started 
and on what ports etc.

-- 
Cyrus Daboo



More information about the calendarserver-users mailing list