On Jun 7, 2011, at 6:22 PM, Scott Cherf wrote:On Jun 7, 2011, at 5:58 PM, Glyph Lefkowitz wrote:On Jun 7, 2011, at 5:52 PM, Scott Cherf wrote:On Jun 7, 2011, at 3:29 PM, Glyph Lefkowitz wrote:Clearly this release tag should work, but I'm curious: can you reproduce this behavior on trunk, or does trunk start up correctly for you?-glyphYes I can reproduce it on the trunk using the top of tree as of earlier today. It must be some type shared configuration problem.
Are there any other salient details about your configuration?Here's a high level view of the machineSystem Software Overview:System Version: Mac OS X 10.6.2 (10C540)Not that this should make a difference, but: you said 10.6.6 earlier, but this says 10.6.2.Kernel Version: Darwin 10.2.0Boot Volume: AlphonseBoot Mode: NormalComputer Name: AlphonseUser Name: Scott Cherf (cherf)Secure Virtual Memory: Not Enabled64-bit Kernel and Extensions: NoTime since boot: 14:33I'm running Python 2.6 along with a complicated and somewhat handcrafted collection of open source software installed in /opt/local. It would be difficult to characterize all of the versions of utilities installed though I'm happy to answer questions.The only interesting software would be dependencies of calendar server. Do you have a custom version of Twisted? Of Python?Where are you checking out the code?The full paths to the checked out versions are:/Users/cherf/Projects/Source/MacOSForge/CalendarServer/trunk/Users/cherf/Projects/Source/MacOSForge/CalendarServer/tags/release/CalendarServer-2.5Both were checked out this morning using Xcode 3 from:Have you modified anything, either configuration or code?In both examples I performed the recommended copy caldavd-test.plist, which was done by the script on trunk and manually on 2.5. I'm not aware of making any other changes.Good to know.Do other machines experience the same error?I haven't built on any other machines yet since I only have a production environment on this one.
If it also affects trunk, that is good news - it narrows it down a bit, since it must be in code that's common between the two.Fire away with any questions you can think of,What does this Python program do on your system?Does it behave differently inside the directory you mentioned? A few directories down? (In case you're not familiar with socket programming, it should just create a file called 'some.socket', which you can safely remove.)import socketskt = socket.socket(socket.AF_UNIX, socket.SOCK_STREAM)skt.bind("some.socket")skt.listen(5)