On Apr 17, 2007, at 9:27 PM, [EMAIL PROTECTED] wrote:
On 17/apr/07, at 18:35, David Reid wrote:
Since it is a ConnectionError it looks like it's probably one of
the ControlSockets ... eithers logs/caldavd.sock or logs/caldavd-
pydir.sock. If one of these doesn't exist then there should be
another exception near the top, or printed when you ^C the server.
- -David
Only caldavd.sock is present in logs, caldavd-pydir.sock is not
there, here's the full output from starting the server to trying
to access 192.168.200.6:8008 in a browser.
-Gianni
It's possible I'm not handling the single server case correctly and
that it is trying to connect to the caldavd-pydir.sock (which isn't
there because pydir isn't running.) You might try editing the
config file to launch 2 processes and see if the problem still
occurs. Could you please file a bug and assign it to me? I'll try
to reproduce and hopefully fix the problem this afternoon.
- -David
Hi David
It seems that is indeed the case, when I configure the server to
launch 2 processes it works fine.
I've created an account on the site and tried to submit a bug ticket
but it I don't have permission.
-Gianni
_______________________________________________
calendarserver-users mailing list
calendarserver-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/calendarserver-users
