[erlang-bugs] Erlang nodes fail to communicate if user has no capability to change SO_PRIORITY socket options.

[Janek Wrobel]

On Tue, Jan 18, 2011 at 5:15 PM,  <pan@REDACTED> wrote:
> On Mon, 17 Jan 2011, Serge Aleynikov wrote:
>
>> At some point I was having a similar issue with SO_PRIORITY and SO_TOS bug
>> in inet_drv when trying to open a unix domain socket and pass the open file
>> descriptor to gen_tcp, which failed to function properly. After discussing
>> this issue with Per Hedeland he sent me the attached patch that worked well
>> to solve the issue.  Perhaps it will also work in your case, and if so, it
>> should be included in distribution.
>
> Seems Per's patch covers more cases - if this solves the problem, it seems
> like the best choice to take this one int dev instead of the smaller fix i
> presented earlier.
>
> Janek - have you tried this one?

Yes, I've tried it. It solves a different problem and does not help in
my case. The Per's patch makes sure that setsockopt(...,SO_PRIORITY)
is not called when SO_PRIORITY is not supported by a socket
(getsockopt(..., SO_PRIORITY) fails).

In my case SO_PRIORITY is supported (getsockopt(.., SO_PRIORITY
succeeds), but it is set to a value that user has no capabilities to
set.

I've sent an email to netdev@REDACTED, maybe those guys will
help to determine if this is a generic problem that can affect other
Erlang users: http://www.spinics.net/lists/netdev/msg153009.html

Cheers,
Janek