Hello friends, I'm trying to set up CalendarServer for use at a university, and I have it compiled and running fine on two different MacOSX10.4 machines, one MacBookPro and one G4. However, I can't get either computer to allow external access to port 8008 or 8443. In a browser, localhost:8008 brings up the server database with no problems. And of course, the default port 80 only brings up the "You've installed Apache" page. But any use of my IP: 8008, from the same box or another one, and access is blocked. My firewall in OSX Preferences specifically allows those two ports to be open for CalendarServer, but still they remain mysteriously inaccessible. On a webstat pinging website it came back as "Connection Closed" on that and every other port except the obvious ones (80, 21, 22). I compiled CalendarServer with Subversion 1.4.5, Python 2.4, and basically only worried about getting the client aspects up. I haven't yet been able to get Subversion running with the latest versions of Apache and APR, although I have the latest v's of OpenSSL, libtool, neon, and I assume that the ./run -s took care of any other dependency checkouts. Please excuse me if the answer is pathetically simple, which I'm sure it is. Regardless, I'm stumped. Many thanks, -Doug
The answer is simple but perhaps not obvious (from the Wiki at least :-) The default setup of DCS allows for access through the 'localhost' network interface only. Presuming you are using the default files, you'll want to augment the references to 'localhost' and '127.0.0.1' in <somewhere>/CalendarServer/conf/caldavd-dev.plist like so: <key>ServerHostName</key> <string>your.hostname.here</string> [...] <key>BindAddresses</key> <array> <string>127.0.0.1</string> <string>your.ip.address.here</string> </array> You can also set port numbers and other goodies here. HTH, /Emil P.S. Kudos to the DCS team for the 1.0 release
Hello friends,
I'm trying to set up CalendarServer for use at a university, and I have it compiled and running fine on two different MacOSX10.4 machines, one MacBookPro and one G4.
However, I can't get either computer to allow external access to port 8008 or 8443. In a browser, localhost:8008 brings up the server database with no problems. And of course, the default port 80 only brings up the "You've installed Apache" page. But any use of my IP: 8008, from the same box or another one, and access is blocked.
My firewall in OSX Preferences specifically allows those two ports to be open for CalendarServer, but still they remain mysteriously inaccessible. On a webstat pinging website it came back as "Connection Closed" on that and every other port except the obvious ones (80, 21, 22).
I compiled CalendarServer with Subversion 1.4.5, Python 2.4, and basically only worried about getting the client aspects up. I haven't yet been able to get Subversion running with the latest versions of Apache and APR, although I have the latest v's of OpenSSL, libtool, neon, and I assume that the ./run -s took care of any other dependency checkouts.
Please excuse me if the answer is pathetically simple, which I'm sure it is. Regardless, I'm stumped.
Many thanks,
-Doug
Hello, Thanks to Emil I was able to solve the port issue on the G4. On my MacBook however, after checking out the new 1.0 release, the run script seems to not be listening to the caldavd-dev.plist config file. Anything I change in there seems to make little difference, especially the IP addresses. Sure enough, it won't bind to my actual IP, hostname, or even desired port. Is there anything different about the new release that might cause this? I've tried recompiling all of subversion, removing DCS and starting over from the checkout, and same result. Again, am I missing some simple toggle? This time at least I have the conf files set right. Thanks in advance, Doug On Oct 26, 2007, at 5:15 PM, Emil Lundberg wrote:
The answer is simple but perhaps not obvious (from the Wiki at least :-)
The default setup of DCS allows for access through the 'localhost' network interface only. Presuming you are using the default files, you'll want to augment the references to 'localhost' and '127.0.0.1' in <somewhere>/CalendarServer/conf/caldavd-dev.plist like so:
<key>ServerHostName</key> <string>your.hostname.here</string> [...] <key>BindAddresses</key> <array> <string>127.0.0.1</string> <string>your.ip.address.here</string> </array>
You can also set port numbers and other goodies here.
HTH,
/Emil
P.S. Kudos to the DCS team for the 1.0 release
Hello friends,
I'm trying to set up CalendarServer for use at a university, and I have it compiled and running fine on two different MacOSX10.4 machines, one MacBookPro and one G4.
However, I can't get either computer to allow external access to port 8008 or 8443. In a browser, localhost:8008 brings up the server database with no problems. And of course, the default port 80 only brings up the "You've installed Apache" page. But any use of my IP:8008, from the same box or another one, and access is blocked.
My firewall in OSX Preferences specifically allows those two ports to be open for CalendarServer, but still they remain mysteriously inaccessible. On a webstat pinging website it came back as "Connection Closed" on that and every other port except the obvious ones (80, 21, 22).
I compiled CalendarServer with Subversion 1.4.5, Python 2.4, and basically only worried about getting the client aspects up. I haven't yet been able to get Subversion running with the latest versions of Apache and APR, although I have the latest v's of OpenSSL, libtool, neon, and I assume that the ./run -s took care of any other dependency checkouts.
Please excuse me if the answer is pathetically simple, which I'm sure it is. Regardless, I'm stumped.
Many thanks,
-Doug
calendarserver-users mailing list calendarserver-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/calendarserver-users
Hi again, I've just installed DCS (release 1.0) on Leopard Server (GM), and it runs as expected with the aforementioned setup steps. Double-check your procedure (file names, port numbers etc) and if it still fails, run the server daemonized (./run -d) and check the following: * What setup are you using exactly (OS type/version, python, subversion, etc)? Any firewalls on the MB? * Examine the log files carefully (in logs/ by default) for any signs of misconfiguration * Does DCS work at all (i.e. a browser pointed to http://localhost: 8008 should display a collection listing)? * Does the collection listing provide the users you expect from the accounts file (see http://localhost:8008/principals/)? From the looks of it you are using 10.4 (or you shouldn't have had to install subversion and python), but I don't see why the 1.0 release would break anything. On 10.5, everything DCS needs (svn, python 2.4+) is either preinstalled or downloaded through the setup step (./run -s) HTH, /Emil 27 okt 2007 kl. 13.24 skrev Douglas O'Connor:
Hello,
Thanks to Emil I was able to solve the port issue on the G4. On my MacBook however, after checking out the new 1.0 release, the run script seems to not be listening to the caldavd-dev.plist config file. Anything I change in there seems to make little difference, especially the IP addresses. Sure enough, it won't bind to my actual IP, hostname, or even desired port.
Is there anything different about the new release that might cause this? I've tried recompiling all of subversion, removing DCS and starting over from the checkout, and same result. Again, am I missing some simple toggle? This time at least I have the conf files set right.
Thanks in advance,
Doug
On Oct 26, 2007, at 5:15 PM, Emil Lundberg wrote:
The answer is simple but perhaps not obvious (from the Wiki at least :-)
The default setup of DCS allows for access through the 'localhost' network interface only. Presuming you are using the default files, you'll want to augment the references to 'localhost' and '127.0.0.1' in <somewhere>/CalendarServer/conf/caldavd-dev.plist like so:
<key>ServerHostName</key> <string>your.hostname.here</string> [...] <key>BindAddresses</key> <array> <string>127.0.0.1</string> <string>your.ip.address.here</string> </array>
You can also set port numbers and other goodies here.
HTH,
/Emil
P.S. Kudos to the DCS team for the 1.0 release
Hello friends,
I'm trying to set up CalendarServer for use at a university, and I have it compiled and running fine on two different MacOSX10.4 machines, one MacBookPro and one G4.
However, I can't get either computer to allow external access to port 8008 or 8443. In a browser, localhost:8008 brings up the server database with no problems. And of course, the default port 80 only brings up the "You've installed Apache" page. But any use of my IP:8008, from the same box or another one, and access is blocked.
My firewall in OSX Preferences specifically allows those two ports to be open for CalendarServer, but still they remain mysteriously inaccessible. On a webstat pinging website it came back as "Connection Closed" on that and every other port except the obvious ones (80, 21, 22).
I compiled CalendarServer with Subversion 1.4.5, Python 2.4, and basically only worried about getting the client aspects up. I haven't yet been able to get Subversion running with the latest versions of Apache and APR, although I have the latest v's of OpenSSL, libtool, neon, and I assume that the ./run -s took care of any other dependency checkouts.
Please excuse me if the answer is pathetically simple, which I'm sure it is. Regardless, I'm stumped.
Many thanks,
-Doug
calendarserver-users mailing list calendarserver-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/calendarserver-users
Oh, and while you're at it: The plist/xml parsing seems sensitive to typos and malformed xml, so check that there are no missing brackets or such. The logs should tell you more about this. E 28 okt 2007 kl. 13.42 skrev Emil Lundberg:
Hi again,
I've just installed DCS (release 1.0) on Leopard Server (GM), and it runs as expected with the aforementioned setup steps. Double- check your procedure (file names, port numbers etc) and if it still fails, run the server daemonized (./run -d) and check the following:
* What setup are you using exactly (OS type/version, python, subversion, etc)? Any firewalls on the MB? * Examine the log files carefully (in logs/ by default) for any signs of misconfiguration * Does DCS work at all (i.e. a browser pointed to http://localhost: 8008 should display a collection listing)? * Does the collection listing provide the users you expect from the accounts file (see http://localhost:8008/principals/)?
From the looks of it you are using 10.4 (or you shouldn't have had to install subversion and python), but I don't see why the 1.0 release would break anything. On 10.5, everything DCS needs (svn, python 2.4+) is either preinstalled or downloaded through the setup step (./run -s)
HTH,
/Emil
27 okt 2007 kl. 13.24 skrev Douglas O'Connor:
Hello,
Thanks to Emil I was able to solve the port issue on the G4. On my MacBook however, after checking out the new 1.0 release, the run script seems to not be listening to the caldavd-dev.plist config file. Anything I change in there seems to make little difference, especially the IP addresses. Sure enough, it won't bind to my actual IP, hostname, or even desired port.
Is there anything different about the new release that might cause this? I've tried recompiling all of subversion, removing DCS and starting over from the checkout, and same result. Again, am I missing some simple toggle? This time at least I have the conf files set right.
Thanks in advance,
Doug
On Oct 26, 2007, at 5:15 PM, Emil Lundberg wrote:
The answer is simple but perhaps not obvious (from the Wiki at least :-)
The default setup of DCS allows for access through the 'localhost' network interface only. Presuming you are using the default files, you'll want to augment the references to 'localhost' and '127.0.0.1' in <somewhere>/CalendarServer/conf/ caldavd-dev.plist like so:
<key>ServerHostName</key> <string>your.hostname.here</string> [...] <key>BindAddresses</key> <array> <string>127.0.0.1</string> <string>your.ip.address.here</string> </array>
You can also set port numbers and other goodies here.
HTH,
/Emil
P.S. Kudos to the DCS team for the 1.0 release
Hello friends,
I'm trying to set up CalendarServer for use at a university, and I have it compiled and running fine on two different MacOSX10.4 machines, one MacBookPro and one G4.
However, I can't get either computer to allow external access to port 8008 or 8443. In a browser, localhost:8008 brings up the server database with no problems. And of course, the default port 80 only brings up the "You've installed Apache" page. But any use of my IP:8008, from the same box or another one, and access is blocked.
My firewall in OSX Preferences specifically allows those two ports to be open for CalendarServer, but still they remain mysteriously inaccessible. On a webstat pinging website it came back as "Connection Closed" on that and every other port except the obvious ones (80, 21, 22).
I compiled CalendarServer with Subversion 1.4.5, Python 2.4, and basically only worried about getting the client aspects up. I haven't yet been able to get Subversion running with the latest versions of Apache and APR, although I have the latest v's of OpenSSL, libtool, neon, and I assume that the ./run -s took care of any other dependency checkouts.
Please excuse me if the answer is pathetically simple, which I'm sure it is. Regardless, I'm stumped.
Many thanks,
-Doug
calendarserver-users mailing list calendarserver-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/calendarserver-users
_______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/calendarserver-users
Hi Emil, --On October 28, 2007 4:32:52 PM +0100 Emil Lundberg <Emil.Lundberg@bmc.uu.se> wrote:
Oh, and while you're at it:
The plist/xml parsing seems sensitive to typos and malformed xml, so check that there are no missing brackets or such.
The logs should tell you more about this.
Right, if you are having problems, please attach your error.log file if you want us to help as that should give us a hint as to the root of the problem. -- Cyrus Daboo
Hi Emil, 1.) Double-checked all the file names and port numbers: as far as I can still, it's all good. 2.) I'm using OSX 10.4.10 Tiger, Python 2.4, Subversion 1.4.5, Apache 2.2.6, APR 1.2.11, and APR-UTIL 1.2.10. The firewall is down for the ports that I've configured DCS to listen on (8008 and 8443). 3.) No error logs come through, the only logfiles I can actually open don't contain much (access.log). 4.) DCS works on the localhost, but not on the port that I assign it in the caldavd-dev.plist. In fact, it always assigns to one or two ports higher than what I tell it, and it ignores my serverhostname and IP address that I give to it. (See the verbose run script below to understand more clearly). I don't know why it changes the port, but whichever one it chooses I can access on localhost just fine. 5.) The collection listing is solid, no problems there, it reflects my plist and xml arrangements. Here below is the run script readout: 2007-10-29 02:55:56-0400 [-] Log opened. 2007-10-29 02:55:56-0400 [-] twistd 2.5.0+rUnknown (/Library/ Frameworks/Python.framework/Versions/2.4/Resources/Python.app/ Contents/MacOS/Python 2.4.4) starting up 2007-10-29 02:55:56-0400 [-] reactor class: <class 'twisted.internet.selectreactor.SelectReactor'> 2007-10-29 02:55:56-0400 [-] 2 processors found, configuring 2 processes. 2007-10-29 02:55:56-0400 [-] Adding pydirector service with configuration: /tmp/pydirptkDkU 2007-10-29 02:55:56-0400 [-] twistedcaldav.logging.AMPLoggingFactory starting on "'logs/caldavd.sock'" 2007-10-29 02:55:57-0400 [-] [caldav-8009] [-] Log opened. 2007-10-29 02:55:57-0400 [-] [caldav-8009] [-] twistd 2.5.0+rUnknown (/Library/Frameworks/Python.framework/Versions/2.4/Resources/ Python.app/Contents/MacOS/Python 2.4.4) starting up 2007-10-29 02:55:57-0400 [-] [caldav-8009] [-] reactor class: <class 'twisted.internet.selectreactor.SelectReactor'> 2007-10-29 02:55:57-0400 [-] [caldav-8009] [-] Configuring directory service of type: twistedcaldav.directory.xmlfile.XMLDirectoryService 2007-10-29 02:55:57-0400 [-] [caldav-8009] [-] Configuring SudoDirectoryService with file: conf/sudoers.plist 2007-10-29 02:55:57-0400 [-] [caldav-8009] [-] Setting up document root at: twistedcaldav/test/data/ 2007-10-29 02:55:57-0400 [-] [caldav-8009] [-] Setting up principal collection: <class 'twistedcaldav.directory.principal.DirectoryPrincipalProvisioningResourc e'> 2007-10-29 02:55:57-0400 [-] [caldav-8009] [-] Setting up calendar collection: <class 'twistedcaldav.static.CalendarHomeProvisioningFile'> 2007-10-29 02:55:57-0400 [-] [caldav-8009] [-] Setting up root resource: <class 'twistedcaldav.root.RootResource'> 2007-10-29 02:55:57-0400 [-] [caldav-8009] [-] Setting up default ACEs on root resource 2007-10-29 02:55:57-0400 [-] [caldav-8009] [-] Setting up AdminPrincipals 2007-10-29 02:55:57-0400 [-] [caldav-8009] [-] Added /principals/ __uids__/admin/ as admin principal 2007-10-29 02:55:57-0400 [-] [caldav-8009] [-] Setting root ACL 2007-10-29 02:55:57-0400 [-] [caldav-8009] [-] Configuring authentication for realm: Test Realm 2007-10-29 02:55:57-0400 [-] [caldav-8009] [-] Setting up scheme: kerberos 2007-10-29 02:55:57-0400 [-] [caldav-8009] [KerberosCredentialFactoryBase] getServerPrincipalDetails: ('Cannot get sequence cursor from keytab', 2) 2007-10-29 02:55:57-0400 [-] [caldav-8009] [-] Could not start Kerberos 2007-10-29 02:55:57-0400 [-] [caldav-8009] [-] Setting up scheme: digest 2007-10-29 02:55:57-0400 [-] [caldav-8009] [-] Setting up scheme: basic 2007-10-29 02:55:57-0400 [-] [caldav-8009] [-] Configuring authentication wrapper 2007-10-29 02:55:57-0400 [-] [caldav-8009] [-] Setting up service 2007-10-29 02:55:57-0400 [-] [caldav-8009] [-] Configuring log observer: <twistedcaldav.logging.AMPCommonAccessLoggingObserver object at 0x200ed50> 2007-10-29 02:55:57-0400 [-] [caldav-8009] [-] Adding server at 127.0.0.1:8009 2007-10-29 02:55:57-0400 [-] [caldav-8009] [-] Adding SSL server at 127.0.0.1:8444 2007-10-29 02:55:57-0400 [-] [caldav-8009] [-] twisted.web2.channel.http.HTTPFactory starting on 8009 2007-10-29 02:55:57-0400 [-] [caldav-8009] [-] Starting factory <twisted.web2.channel.http.HTTPFactory instance at 0x17f2d78> 2007-10-29 02:55:57-0400 [-] [caldav-8009] [-] twisted.web2.channel.http.HTTPFactory starting on 8444 2007-10-29 02:55:57-0400 [twistedcaldav.logging.AMPLoggingFactory] AMPLoggingProtocol connection established (HOST:UNIXSocket('logs/ caldavd.sock') PEER:UNIXSocket('')) 2007-10-29 02:55:57-0400 [-] [caldav-8009] [-] AMP connection established (HOST:UNIXSocket(None) PEER:UNIXSocket('logs/caldavd.sock')) 2007-10-29 02:55:57-0400 [-] [caldav-8010] [-] Log opened. 2007-10-29 02:55:57-0400 [-] [caldav-8010] [-] twistd 2.5.0+rUnknown (/Library/Frameworks/Python.framework/Versions/2.4/Resources/ Python.app/Contents/MacOS/Python 2.4.4) starting up 2007-10-29 02:55:57-0400 [-] [caldav-8010] [-] reactor class: <class 'twisted.internet.selectreactor.SelectReactor'> 2007-10-29 02:55:57-0400 [-] [caldav-8010] [-] Configuring directory service of type: twistedcaldav.directory.xmlfile.XMLDirectoryService 2007-10-29 02:55:57-0400 [-] [caldav-8010] [-] Configuring SudoDirectoryService with file: conf/sudoers.plist 2007-10-29 02:55:57-0400 [-] [caldav-8010] [-] Setting up document root at: twistedcaldav/test/data/ 2007-10-29 02:55:57-0400 [-] [caldav-8010] [-] Setting up principal collection: <class 'twistedcaldav.directory.principal.DirectoryPrincipalProvisioningResourc e'> 2007-10-29 02:55:57-0400 [-] [caldav-8010] [-] Setting up calendar collection: <class 'twistedcaldav.static.CalendarHomeProvisioningFile'> 2007-10-29 02:55:57-0400 [-] [caldav-8010] [-] Setting up root resource: <class 'twistedcaldav.root.RootResource'> 2007-10-29 02:55:57-0400 [-] [caldav-8010] [-] Setting up default ACEs on root resource 2007-10-29 02:55:57-0400 [-] [caldav-8010] [-] Setting up AdminPrincipals 2007-10-29 02:55:57-0400 [-] [caldav-8010] [-] Added /principals/ __uids__/admin/ as admin principal 2007-10-29 02:55:57-0400 [-] [caldav-8010] [-] Setting root ACL 2007-10-29 02:55:57-0400 [-] [caldav-8010] [-] Configuring authentication for realm: Test Realm 2007-10-29 02:55:57-0400 [-] [caldav-8010] [-] Setting up scheme: kerberos 2007-10-29 02:55:57-0400 [-] [caldav-8010] [KerberosCredentialFactoryBase] getServerPrincipalDetails: ('Cannot get sequence cursor from keytab', 2) 2007-10-29 02:55:57-0400 [-] [caldav-8010] [-] Could not start Kerberos 2007-10-29 02:55:57-0400 [-] [caldav-8010] [-] Setting up scheme: digest 2007-10-29 02:55:57-0400 [-] [caldav-8010] [-] Setting up scheme: basic 2007-10-29 02:55:57-0400 [-] [caldav-8010] [-] Configuring authentication wrapper 2007-10-29 02:55:57-0400 [-] [caldav-8010] [-] Setting up service 2007-10-29 02:55:57-0400 [-] [caldav-8010] [-] Configuring log observer: <twistedcaldav.logging.AMPCommonAccessLoggingObserver object at 0x200ed50> 2007-10-29 02:55:57-0400 [-] [caldav-8010] [-] Adding server at 127.0.0.1:8010 2007-10-29 02:55:57-0400 [-] [caldav-8010] [-] Adding SSL server at 127.0.0.1:8445 2007-10-29 02:55:57-0400 [-] [caldav-8010] [-] twisted.web2.channel.http.HTTPFactory starting on 8010 2007-10-29 02:55:57-0400 [-] [caldav-8010] [-] Starting factory <twisted.web2.channel.http.HTTPFactory instance at 0x17f2d78> 2007-10-29 02:55:57-0400 [-] [caldav-8010] [-] twisted.web2.channel.http.HTTPFactory starting on 8445 2007-10-29 02:55:57-0400 [twistedcaldav.logging.AMPLoggingFactory] AMPLoggingProtocol connection established (HOST:UNIXSocket('logs/ caldavd.sock') PEER:UNIXSocket('')) 2007-10-29 02:55:57-0400 [-] [caldav-8010] [-] AMP connection established (HOST:UNIXSocket(None) PEER:UNIXSocket('logs/caldavd.sock')) I've attached a copy of my caldavd-dev.plist. Thanks again so much! -Doug On Oct 28, 2007, at 8:42 AM, Emil Lundberg wrote:
Hi again,
I've just installed DCS (release 1.0) on Leopard Server (GM), and it runs as expected with the aforementioned setup steps. Double- check your procedure (file names, port numbers etc) and if it still fails, run the server daemonized (./run -d) and check the following:
* What setup are you using exactly (OS type/version, python, subversion, etc)? Any firewalls on the MB? * Examine the log files carefully (in logs/ by default) for any signs of misconfiguration * Does DCS work at all (i.e. a browser pointed to http://localhost: 8008 should display a collection listing)? * Does the collection listing provide the users you expect from the accounts file (see http://localhost:8008/principals/)?
From the looks of it you are using 10.4 (or you shouldn't have had to install subversion and python), but I don't see why the 1.0 release would break anything. On 10.5, everything DCS needs (svn, python 2.4+) is either preinstalled or downloaded through the setup step (./run -s)
HTH,
/Emil
27 okt 2007 kl. 13.24 skrev Douglas O'Connor:
Hello,
Thanks to Emil I was able to solve the port issue on the G4. On my MacBook however, after checking out the new 1.0 release, the run script seems to not be listening to the caldavd-dev.plist config file. Anything I change in there seems to make little difference, especially the IP addresses. Sure enough, it won't bind to my actual IP, hostname, or even desired port.
Is there anything different about the new release that might cause this? I've tried recompiling all of subversion, removing DCS and starting over from the checkout, and same result. Again, am I missing some simple toggle? This time at least I have the conf files set right.
Thanks in advance,
Doug
On Oct 26, 2007, at 5:15 PM, Emil Lundberg wrote:
The answer is simple but perhaps not obvious (from the Wiki at least :-)
The default setup of DCS allows for access through the 'localhost' network interface only. Presuming you are using the default files, you'll want to augment the references to 'localhost' and '127.0.0.1' in <somewhere>/CalendarServer/conf/ caldavd-dev.plist like so:
<key>ServerHostName</key> <string>your.hostname.here</string> [...] <key>BindAddresses</key> <array> <string>127.0.0.1</string> <string>your.ip.address.here</string> </array>
You can also set port numbers and other goodies here.
HTH,
/Emil
P.S. Kudos to the DCS team for the 1.0 release
Hello friends,
I'm trying to set up CalendarServer for use at a university, and I have it compiled and running fine on two different MacOSX10.4 machines, one MacBookPro and one G4.
However, I can't get either computer to allow external access to port 8008 or 8443. In a browser, localhost:8008 brings up the server database with no problems. And of course, the default port 80 only brings up the "You've installed Apache" page. But any use of my IP:8008, from the same box or another one, and access is blocked.
My firewall in OSX Preferences specifically allows those two ports to be open for CalendarServer, but still they remain mysteriously inaccessible. On a webstat pinging website it came back as "Connection Closed" on that and every other port except the obvious ones (80, 21, 22).
I compiled CalendarServer with Subversion 1.4.5, Python 2.4, and basically only worried about getting the client aspects up. I haven't yet been able to get Subversion running with the latest versions of Apache and APR, although I have the latest v's of OpenSSL, libtool, neon, and I assume that the ./run -s took care of any other dependency checkouts.
Please excuse me if the answer is pathetically simple, which I'm sure it is. Regardless, I'm stumped.
Many thanks,
-Doug
calendarserver-users mailing list calendarserver-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/calendarserver-users
Hi Douglas, --On October 29, 2007 3:04:07 AM -0400 Douglas O'Connor <business@dougoconnor.com> wrote:
1.) Double-checked all the file names and port numbers: as far as I can still, it's all good. 2.) I'm using OSX 10.4.10 Tiger, Python 2.4, Subversion 1.4.5, Apache 2.2.6, APR 1.2.11, and APR-UTIL 1.2.10. The firewall is down for the ports that I've configured DCS to listen on (8008 and 8443). 3.) No error logs come through, the only logfiles I can actually open don't contain much (access.log). 4.) DCS works on the localhost, but not on the port that I assign it in the caldavd-dev.plist. In fact, it always assigns to one or two ports higher than what I tell it, and it ignores my serverhostname and IP address that I give to it. (See the verbose run script below to understand more clearly). I don't know why it changes the port, but whichever one it chooses I can access on localhost just fine. 5.) The collection listing is solid, no problems there, it reflects my plist and xml arrangements.
Here below is the run script readout:
Some things to note: the server architecture we have allows for the "server" to actual spawn multiple server processes for handling requests. By default we spawn one server instance per cpu/core. When we do that, each server instance listens only on 127.0.0.1 and on a port that is different from the main one configured in the .plist (we increase the port numbers by one for each instance). We then also start a load balancer process (pydirector) that should be listening on all the interfaces/ports specified in the .plist, and that will redirect incoming requests to each server instance in an appropriate fashion. The error.log file (or stdout) will show the localhost and instance port numbers, not the interface/port of the load balancer. So you need to ignore those and just attempt to connect on the interfaces/ports in the caldavd.plist. Can you start the server again and look for the 'Adding pydirector service with configuration: XXX' line in the log output, and then in another terminal window cat the XXX file listed there. You should see four services setup in that config file - two of which listen on localhost and two of which listen on the external address on the ports you have specified. Can you double-check that? -- Cyrus Daboo
Hi Cyrus, Emil, et. al, Thank-you for your explanation of how some of the different pieces work together with the server(s)/processors and whatnot. I found the PyDirector service you're looking for, and it cat's the way you would expect: "four services setup in that config file - two of which listen on localhost and two of which listen on the external address on the ports you have specified." Ex: <pdconfig> <service name="http"> <listen ip="127.0.0.1:8008" /> <group name="main" scheduler="leastconns"> <host name="caldav-8009" ip="127.0.0.1:8009" /> <host name="caldav-8010" ip="127.0.0.1:8010" /> </group> <enable group="main" /> </service> <service name="https"> <listen ip="127.0.0.1:8443" /> <group name="main" scheduler="leastconns"> <host name="caldav-8444" ip="127.0.0.1:8444" /> <host name="caldav-8445" ip="127.0.0.1:8445" /> </group> <enable group="main" /> </service> (I've only listed the localhost params for privacy purposes) I assume that what's listed above is quite normal, although I don't quite understand why it assigns hostnames on ports 8009 and 8010 for http, or on 8444 and 8445 for the https, especially when it's listening on 8008 and 8443 respectively. As long as it works, right? :) On the other box, a single-processor G4, I have DCS running with no problems, and it doesn't do this. It doesn't load PyDirector at all, I assume because it doesn't need to balance loads between multiple processors, and perhaps this is the key difference? PyDirector is the problem on my newer duocore machine? If so, still, how do I address this? And on both boxes, I get the lines: 2007-10-29 13:53:18-0400 [-] [caldav-8008] [startup] Setting up scheme: kerberos 2007-10-29 13:53:18-0400 [-] [caldav-8008] [KerberosCredentialFactoryBase] getServerPrincipalDetails: ('Cannot get sequence cursor from keytab', 2) 2007-10-29 13:53:18-0400 [-] [caldav-8008] [startup] Could not start Kerberos I thought this might have been the stumbling block on my MacBookPro, the machine I'm having problems with, but since it happens on the G4 too maybe it doesn't matter. Or perhaps I just haven't gotten to the point on the G4 where it does matter. Anyhow, any advice on this one? Many thanks, -Doug On Oct 29, 2007, at 11:44 AM, Cyrus Daboo wrote:
Hi Douglas,
--On October 29, 2007 3:04:07 AM -0400 Douglas O'Connor <business@dougoconnor.com> wrote:
1.) Double-checked all the file names and port numbers: as far as I can still, it's all good. 2.) I'm using OSX 10.4.10 Tiger, Python 2.4, Subversion 1.4.5, Apache 2.2.6, APR 1.2.11, and APR-UTIL 1.2.10. The firewall is down for the ports that I've configured DCS to listen on (8008 and 8443). 3.) No error logs come through, the only logfiles I can actually open don't contain much (access.log). 4.) DCS works on the localhost, but not on the port that I assign it in the caldavd-dev.plist. In fact, it always assigns to one or two ports higher than what I tell it, and it ignores my serverhostname and IP address that I give to it. (See the verbose run script below to understand more clearly). I don't know why it changes the port, but whichever one it chooses I can access on localhost just fine. 5.) The collection listing is solid, no problems there, it reflects my plist and xml arrangements.
Here below is the run script readout:
Some things to note: the server architecture we have allows for the "server" to actual spawn multiple server processes for handling requests. By default we spawn one server instance per cpu/core. When we do that, each server instance listens only on 127.0.0.1 and on a port that is different from the main one configured in the .plist (we increase the port numbers by one for each instance). We then also start a load balancer process (pydirector) that should be listening on all the interfaces/ports specified in the .plist, and that will redirect incoming requests to each server instance in an appropriate fashion. The error.log file (or stdout) will show the localhost and instance port numbers, not the interface/port of the load balancer. So you need to ignore those and just attempt to connect on the interfaces/ports in the caldavd.plist.
Can you start the server again and look for the 'Adding pydirector service with configuration: XXX' line in the log output, and then in another terminal window cat the XXX file listed there. You should see four services setup in that config file - two of which listen on localhost and two of which listen on the external address on the ports you have specified. Can you double-check that?
-- Cyrus Daboo
(slightly confused as to whether to top- or bottom post. oh well) Thanks Cyrus for the explanation, I was going to ask that question too, although I hadn't run DCS on anything less than a 4-core machine before... :-) Now; you (Douglas) mentioned you opened the firewall for traffic to the 8008 and 8443 ports. Even though ports 8009-8010 and 8444-8445 are only used localhost->localhost (confirmed with netstat on my own machine), perhaps your firewall is locking this traffic out? Simply put; can you deactivate the firewall and see if the service responds? If so, you need to allow for tcp 8008-8010 and 8443-8445 from localhost (or the "any" network). I tried (de)activating tcp/8008 to "any" on the firewall using 10.5.0 server and it was enough to deny/allow communcation with iCal server (as it were), but YMMV. Also, just to be sure: you seem to be using a DHCP address on your MB - hopefully this is the same each boot. Come to think of it I find this statement intriguing:
DCS works on the localhost, but not on the port that I assign it in the caldavd-dev.plist. [...] I don't know why it changes the port, but whichever one it chooses I can access on localhost just fine.
This tells me the PyDirector port(s) are not responding and that you can connect directly to localhost:(port+1) (this not being hindered by the firewall), but not directly to servername:(port+1) (as this is blocked by the firewall). Turn the firewall off and I envision you could connect to servername:(port+1), although it does not tell you why the original ports fail. Small steps... /Emil
Hi Cyrus, Emil, et. al,
Thank-you for your explanation of how some of the different pieces work together with the server(s)/processors and whatnot. I found the PyDirector service you're looking for, and it cat's the way you would expect: "four services setup in that config file - two of which listen on localhost and two of which listen on the external address on the ports you have specified." Ex:
<pdconfig>
<service name="http"> <listen ip="127.0.0.1:8008" /> <group name="main" scheduler="leastconns"> <host name="caldav-8009" ip="127.0.0.1:8009" /> <host name="caldav-8010" ip="127.0.0.1:8010" /> </group> <enable group="main" /> </service>
<service name="https"> <listen ip="127.0.0.1:8443" /> <group name="main" scheduler="leastconns"> <host name="caldav-8444" ip="127.0.0.1:8444" /> <host name="caldav-8445" ip="127.0.0.1:8445" /> </group> <enable group="main" /> </service>
(I've only listed the localhost params for privacy purposes) I assume that what's listed above is quite normal, although I don't quite understand why it assigns hostnames on ports 8009 and 8010 for http, or on 8444 and 8445 for the https, especially when it's listening on 8008 and 8443 respectively. As long as it works, right? :)
On the other box, a single-processor G4, I have DCS running with no problems, and it doesn't do this. It doesn't load PyDirector at all, I assume because it doesn't need to balance loads between multiple processors, and perhaps this is the key difference? PyDirector is the problem on my newer duocore machine? If so, still, how do I address this?
And on both boxes, I get the lines:
2007-10-29 13:53:18-0400 [-] [caldav-8008] [startup] Setting up scheme: kerberos 2007-10-29 13:53:18-0400 [-] [caldav-8008] [KerberosCredentialFactoryBase] getServerPrincipalDetails: ('Cannot get sequence cursor from keytab', 2) 2007-10-29 13:53:18-0400 [-] [caldav-8008] [startup] Could not start Kerberos
I thought this might have been the stumbling block on my MacBookPro, the machine I'm having problems with, but since it happens on the G4 too maybe it doesn't matter. Or perhaps I just haven't gotten to the point on the G4 where it does matter. Anyhow, any advice on this one?
Many thanks,
-Doug
On Oct 29, 2007, at 11:44 AM, Cyrus Daboo wrote:
Hi Douglas,
--On October 29, 2007 3:04:07 AM -0400 Douglas O'Connor <business@dougoconnor.com
wrote:
1.) Double-checked all the file names and port numbers: as far as I can still, it's all good. 2.) I'm using OSX 10.4.10 Tiger, Python 2.4, Subversion 1.4.5, Apache 2.2.6, APR 1.2.11, and APR-UTIL 1.2.10. The firewall is down for the ports that I've configured DCS to listen on (8008 and 8443). 3.) No error logs come through, the only logfiles I can actually open don't contain much (access.log). 4.) DCS works on the localhost, but not on the port that I assign it in the caldavd-dev.plist. In fact, it always assigns to one or two ports higher than what I tell it, and it ignores my serverhostname and IP address that I give to it. (See the verbose run script below to understand more clearly). I don't know why it changes the port, but whichever one it chooses I can access on localhost just fine. 5.) The collection listing is solid, no problems there, it reflects my plist and xml arrangements.
Here below is the run script readout:
Some things to note: the server architecture we have allows for the "server" to actual spawn multiple server processes for handling requests. By default we spawn one server instance per cpu/core. When we do that, each server instance listens only on 127.0.0.1 and on a port that is different from the main one configured in the .plist (we increase the port numbers by one for each instance). We then also start a load balancer process (pydirector) that should be listening on all the interfaces/ports specified in the .plist, and that will redirect incoming requests to each server instance in an appropriate fashion. The error.log file (or stdout) will show the localhost and instance port numbers, not the interface/port of the load balancer. So you need to ignore those and just attempt to connect on the interfaces/ports in the caldavd.plist.
Can you start the server again and look for the 'Adding pydirector service with configuration: XXX' line in the log output, and then in another terminal window cat the XXX file listed there. You should see four services setup in that config file - two of which listen on localhost and two of which listen on the external address on the ports you have specified. Can you double-check that?
-- Cyrus Daboo
participants (3)
-
Cyrus Daboo
-
Douglas O'Connor
-
Emil Lundberg