For the list. Sorry about dropping the CC. ---- Hi Glyph - Well I re-installed python, this time version 2.7. I installed once from MacPorts and once using the .dmg distribution from python.org. Unfortunately neither install corrected the problem. Later I read the README file and discovered Twisted isn't supposed to work with Python 2.7 so I re-installed 2.6 from MacPorts. I couldn't find a 2.6 distribution on the python.org site but I didn't really look hard either. Using the fresh python 2.6 installed at /opt/local/bin/python I observed the following: [alphonse:tags/release/Twisted] cherf% python Python 2.6.6 (r266:84292, Jun 8 2011, 18:50:17) [GCC 4.2.1 (Apple Inc. build 5646)] on darwin Type "help", "copyright", "credits" or "license" for more information.
import socket skt = socket.socket(socket.AF_UNIX, socket.SOCK_STREAM) skt.bind("some.socket") Traceback (most recent call last): File "<stdin>", line 1, in <module> File "<string>", line 1, in bind socket.error: [Errno 22] Invalid argument
I've also attached an rtf containing the results of performing a 'run -v' from the CalanderServer 2.5 directory right after re-installing python 2.6. I didn't use run -s before I did it so it shows a stripped down list of warnings, I thought some of them might be pertinent. Not being familiar with python (or Twisted) I'm at a loss. I can say that AFAIK the python 2.6 install is vanilla. I'm a Perl/Objective C guy and I've only started to become acquainted with python as a result of putting up MOD_PYTHON for Trac in Apache. Any clues or suggestions appreciated and I'll just keep banging my head in private otherwise... "three man teams, radio silence, weapons-free rules of engagement"? Indeed! :) Regards, Scott. On Jun 7, 2011, at 7:29 PM, Glyph Lefkowitz wrote:
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?
-glyph
Yes 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 machine
System 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.0 Boot Volume: Alphonse Boot Mode: Normal Computer Name: Alphonse User Name: Scott Cherf (cherf) Secure Virtual Memory: Not Enabled 64-bit Kernel and Extensions: No Time since boot: 14:33
I'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.5
Both were checked out this morning using Xcode 3 from:
http://svn.macosforge.org/repository/calendarserver
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?
import socket skt = socket.socket(socket.AF_UNIX, socket.SOCK_STREAM) skt.bind("some.socket") skt.listen(5)
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.)