Socat Logging - Error Message "socat E write: Broken pipe"

Discussion in 'Feeding' started by abcd567, Oct 31, 2019.

  1. abcd567

    abcd567 New Member

    adsbx-socat.png


    Code:
    2019/10/31 13:36:34 socat[1278] E write(6, 0x15be890, 500): Broken pipe
    2019/10/31 13:37:13 socat[1774] E write(6, 0x2de890, 518): Broken pipe
    2019/10/31 13:37:52 socat[2294] E write(6, 0x11bd890, 509): Broken pipe
    2019/10/31 13:38:32 socat[2826] E write(6, 0x75a890, 503): Broken pipe
    2019/10/31 13:39:11 socat[3031] E write(6, 0x1d5b890, 514): Broken pipe
    2019/10/31 13:39:51 socat[3154] E write(6, 0xdd8890, 510): Broken pipe
    2019/10/31 13:40:30 socat[3254] E write(6, 0x19c3890, 514): Broken pipe
    2019/10/31 13:41:08 socat[3449] E write(6, 0x1356890, 500): Broken pipe
    2019/10/31 13:41:46 socat[3597] E write(6, 0xebd890, 516): Broken pipe
    2019/10/31 13:42:30 socat[3665] E write(6, 0x1a99890, 504): Broken pipe
    
    Tried to add following in socat command, but problem persists
    ,ignoreeof
    ,keepalive
    ,forever
     
    Last edited: Oct 31, 2019
  2. wiedehopf

    wiedehopf Administrator Staff Member

    Normal.

    It's a server side error.
    If you can see which of the cons-123 you are connecting to at https://adsbexchange.com/myip/ , then you can write it here and james will restart it.
    Working on a fix but the error is elusive.
     
  3. abcd567

    abcd567 New Member

    As far as I know, the "keepalive" works with socat only when it is implemented at server.

    Is "keepalive" implemented on Adsbexchange servers?
     
  4. wiedehopf

    wiedehopf Administrator Staff Member

    There is no reason a TCP connection should just drop by itself even when idle, so keepalive is not really required.
     
  5. abcd567

    abcd567 New Member

    Thanks for the information