View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005825||GNUnet||transport service||public||2019-08-10 21:41||2019-08-10 21:41|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Target Version||Fixed in Version|
|Summary||0005825: setsockopt SO_NOSIGPIPE can fail after socket accept|
|Description||I had to modify the network.c code a bit to find that setting the sockopt NOSIGPIPE after accept() often fails in trasport.|
This happens only in macos.
After investigating it seems like this happens when the remote peer closes the socket before we set the option.
The behaviour is thus correct but spams the logs with the below warnings (more general).
The questions is if we can ignore the error at least for transport? At least accept it and log it as DEBUG?
Usually, the handling of this event (error in sockopt after accept) is to try and reconnect.
|Additional Information||Aug 10 21:24:30-522872 transport-34891 ERROR Assertion failed at network.c:452.|
Aug 10 21:24:30-526849 transport-34891 WARNING `accept' failed at service.c:832 with error: Invalid argument
|Tags||No tags attached.|