Hi, I've just downloaded and compiled DCS on Mac OS 10.5.1. I'm unable to create a service on my node's LAN address, i.e. 192.168.0.101, in spite of making the following changes: $ diff caldavd-test.plist caldavd-dev.plist 35c35 < <string>localhost</string> ---
<string>myhostname.local</string> 54c54,57 < <array></array>
<array> <string>127.0.0.1</string> <string>192.168.0.101</string> </array> $
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 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. Regards, Robert
Hi Robert, --On January 31, 2008 12:08:47 AM +0000 Robert Harris <robert.harris@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
Hi Cyrus, Thanks for offering to help. On 31 Jan 2008, at 02:02, Cyrus Daboo wrote:
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.
I ran 'run -v' and have attached its stdout and the plist file. There was nothing on stderr. Regards, Robert
Hi again, On 31 Jan 2008, at 12:00, Robert Harris wrote:
Hi Cyrus,
Thanks for offering to help.
On 31 Jan 2008, at 02:02, Cyrus Daboo wrote:
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.
I ran 'run -v' and have attached its stdout and the plist file. There was nothing on stderr.
1. As a check, I get the same behaviour on a MacBook with a fresh install of 10.5, the Xcode tools and the upgrade to 10.5.1 (together with the other recommended updates). 2. The problem appears to be in the parsing on the plist (I guess this is evident from the stdout). Hard-coding the appropriate address in tap.py works ok. Could you please give me a pointer to where the parsing takes place and I'll continue to investigate it myself. Regards, Robert
On 31 Jan 2008, at 00:08, Robert Harris wrote:
Hi,
I've just downloaded and compiled DCS on Mac OS 10.5.1.
I'm unable to create a service on my node's LAN address, i.e. 192.168.0.101, in spite of making the following changes:
This now works as expected, after checking out the latest revisions. Robert
participants (2)
-
Cyrus Daboo
-
Robert Harris