[CalendarServer-users] calendarserver 3.2 on Debian unstable throwing error "socket.error: [Errno 22] Invalid argument" out of the box?

[Lars N. Cleemann]

Hi (sorry only send to Glyph at first)

On 2012-07-11 19:15, Glyph wrote:
> Le Jul 11, 2012 à 6:40 AM, Tobias Balle-Petersen <tobiasbp at gmail.com>
> a écrit :
>
>>
>>
>> Chris Cleeland-3 wrote:
>>>
>>> Based on the commit message here:
>>>
>>> 
>>> https://trac.calendarserver.org/browser/CalendarServer/trunk/twext/python/sendfd.py
>>>
>>> it sounds like you might be able to disable this feature.
>>>
>>
>> Good spotting Chris!
>>
>> I disabled the feature "UseMetaFD" in this file:
>> /usr/lib/python2.7/dist-packages/twistedcaldav/stdconfig.py
>>
>> The server now responds when connecting at port 8008 and throws no 
>> errors in
>> the log. That is, "It's working".
>>
>> Any idea what feature "UseMetaFD" does (In layman's terms) ? Should 
>> I worry
>> about it now being disabled?
>
> The UseMetaFD option is not to be set by laymen, so there are no
> layman's terms for it :).
>
> What it does is change the way file descriptors are distributed among
> processes.
>
> You should definitely worry about it being disabled.  The option is
> only still present for tuning and development purposes - basically, 
> to
> see if the strategy we currently use ever has problems with new or
> different hardware or operating systems.
>
> Things might work OK for a while with this option disabled, but be
> aware that the developers don't test in that configuration at all and
> the ability to disable it may one day disappear.

It looks quite a lot like Ticket #448 
(https://trac.calendarserver.org/ticket/448), the error is slightly 
different, but the traceback looks the same to me.

That ticket was changes to expected behavior 7 months ago. Based on 
that I thought that disabling MetaFD, was just something that had to be 
done on systems other than OS X, but it sounds like that is not the 
case?

Best regards

Lars N. Cleemann