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
