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

Chris Cleeland chris.cleeland at gmail.com
Wed Jul 11 12:33:41 PDT 2012


On Wed, Jul 11, 2012 at 12:24 PM, Glyph <glyph at twistedmatrix.com> wrote:

>
> It's possible that this is a bug in calendar server, although I would
> currently rate that possibility as unlikely since I have run calendar
> server in a variety of environments and have not seen that error.  The only
> other thing that comes to mind (if it's not a kernel bug, which seems even
> more unlikely now as it affects such a wide range of versions for you) is
> that it's a result of some peculiar firewall configuration.
>
> Do you have any extra security on this machine?  Custom AppArmor
> configuration, or iptables rules, or LXC containers... anything that would
> change the behavior of basic networking APIs?
>

Interesting idea, but what is happening--passing a file descriptor from one
process to another--happens over a unix domain socket.  I'm not aware of
unix domain sockets being subject to firewalls since they are, by
definition, constrained to the host.

An easy test would be to write a small bit of code in python to open a unix
domain socket, fork, then in one of the two processes open another file and
try to pass the fd for the "another file" to the other process.  See if
that succeeds.  Maybe there is an ACL/privilege that needs to be bestowed
in the latest version of ubuntu in order to pass or accept an fd?

Or maybe there's a unit test from twisted that exercises this bit of code
that Tobias could run independent of the entire calendar server?

-- 
Chris Cleeland
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/calendarserver-users/attachments/20120711/272c1195/attachment.html>


More information about the calendarserver-users mailing list