Feeding running, but error "broken pipe"

Discussion in 'Feeding' started by foxhunter, Aug 2, 2019.

  1. foxhunter

    foxhunter New Member

    Morning everybody

    i've started feeding this morning.
    From the "myip" test it looks good, but the check ends up with "broken pipe":

    Code:
    2019/08/02 05:59:06 socat[7557] N opening connection to AF=2 127.0.0.1:30005
2019/08/02 05:59:06 socat[7557] N successfully connected from local address AF=2 127.0.0.1:38890
2019/08/02 05:59:06 socat[7557] N opening connection to AF=2 167.114.60.74:30005
2019/08/02 05:59:06 socat[7557] N successfully connected from local address AF=2 192.168.xx.xx:59038
2019/08/02 05:59:06 socat[7557] N starting data transfer loop with FDs [5,5] and [6,6]
2019/08/02 05:59:11 socat[7557] E write(6, 0x41b750, 1006): Broken pipe
2019/08/02 05:59:11 socat[7557] N exit(1)
    In the MLAT statistics my station is listed, but on the map for feeder locations it's missing.

    Any idea on that?
     
    foxhunter, Aug 2, 2019
    #1
  2. MDA

    MDA Administrator Staff Member

    If you use ADSBx image check config file, if PRIVACY is set to yes then your location pin is hidden (change it to no and reboot pi).
    Broken pipe needs more investigations, can you post more details (fe. htop screenshot)?
     
    MDA, Aug 2, 2019
    #2
  3. foxhunter

    foxhunter New Member

    What particular peace of htop are you interested in?

    The pin is meanwhile visible on the map, might have taken a while
    I am not usine the ADSBx image, i am on PiAware Image

    Thanks
     
    foxhunter, Aug 2, 2019
    #3
  4. MDA

    MDA Administrator Staff Member

    Ok, please post content of /home/pi/adsb-exchange/adsbexchange-mlat_maint.sh and /home/pi/adsb-exchange/adsbexchange-netcat_maint.sh
    Htop can wait :)
     
    MDA, Aug 2, 2019
    #4
  5. foxhunter

    foxhunter New Member

    Hm.... i cannot post it.. Whenever i try to do so, i got message that i am blocked
     
    foxhunter, Aug 2, 2019
    #5
  6. MDA

    MDA Administrator Staff Member

    MDA, Aug 2, 2019
    #6
  7. foxhunter

    foxhunter New Member

    Tried reinstalling the scripts, now it seem to be working.
     
    foxhunter, Aug 2, 2019
    #7
  8. James

    James Guest

    2019/08/02 05:59:06 socat[7557] N successfully connected from local address AF=2 192.168.xx.xx:59038
    2019/08/02 05:59:06 socat[7557] N starting data transfer loop with FDs [5,5] and [6,6]
    2019/08/02 05:59:11 socat[7557] E write(6, 0x41b750, 1006): Broken pipe
    2019/08/02 05:59:11 socat[7557] N exit(1)


    I don't know what that is ....

    This must be PiAware with github scripts and not ADSBx custom image.
     
    James, Aug 2, 2019
    #8
  9. wiedehopf

    wiedehopf Administrator Staff Member

    Had some broken pipe at noon today.
    Quoting stackoverflow:
    "A 'Broken pipe' message happens when you write to a stream where the other end has been closed."​

    So that means somehow the TCP connection isn't open anymore.
    Don't know why socat wouldn't be more useful in the error message.

    Code:
    /usr/bin/socat -u TCP:localhost:30005 TCP:feed.adsbexchange.com:30005
    Sample error
    Code:
    Aug 01 12:19:00 pi adsbexchange-feed[7548]: Connected to feed.adsbexchange.com:30005
Aug 01 12:19:04 pi adsbexchange-feed[7548]: 2019/08/01 12:19:04 socat[19302] E write(6, 0x18d48e8, 1015): Broken pipe
Aug 01 12:19:04 pi adsbexchange-feed[7548]: Disconnected
Aug 01 12:19:35 pi adsbexchange-feed[7548]: Connected to feed.adsbexchange.com:30005
    My connection was broken from 1003Z to 1022Z today 2nd of August.
    But i usually don't worry about it.


    Sometimes i also get this:
    2019/07/30 20:40:52 socat[16489] E write(6, 0x10c78e8, 1014): Connection reset by peer
     
    wiedehopf, Aug 2, 2019
    #9
  10. MDA

    MDA Administrator Staff Member

    Broken pipe itself is nothing to be worry about if happens sometimes.
    Default ADSBx scripts are logging only broken pipe
    Code:
    Aug  2 19:53:37 mda-pi1 rc.local[425]: 2019/08/02 19:53:37 socat[26992] E write(6, 0x1c88338, 1000): Broken pipe
Aug  2 19:54:13 mda-pi1 rc.local[425]: 2019/08/02 19:54:13 socat[26996] E write(6, 0x1a45338, 1001): Broken pipe
Aug  2 19:54:48 mda-pi1 rc.local[425]: 2019/08/02 19:54:48 socat[27004] E write(6, 0x10b5338, 1017): Broken pipe
    Suspicious was line I quoted

    2019/08/02 05:59:06 socat[7557] N successfully connected from local address AF=2 192.168.xx.xx:59038

    It is really difficult to help in case of non standard config.
     
    MDA, Aug 2, 2019
    #10
  11. wiedehopf

    wiedehopf Administrator Staff Member

    Not so suspicious, that's actually just a verbose message that the connection to adsbexchange has been opened.
    Above that is the message where socat says that it has successfully connected to the local dump1090.
     
    wiedehopf, Aug 2, 2019
    #11
  12. MDA

    MDA Administrator Staff Member

    It shows local IP of other device = non standard config. Thats why "suspicious" (away from standard). :)
    How can you help if you don't know how it is configured?
     
    MDA, Aug 2, 2019
    #12
  13. wiedehopf

    wiedehopf Administrator Staff Member

    Well you can clearly see the connection is being established.
    And once established it's unlikely that the local TCP connection just drops.

    Anyway the most likely explanation, some temporary connection error to adsbexchange was the culprit.

    But you are correct of course, you can't diagnose it with certainty.
     
    wiedehopf, Aug 2, 2019
    #13
  14. foxhunter

    foxhunter New Member

    After reinstalling the script yesterday because it did not restart after a reboot, MyIP is now not showing any longer errors

    adsbexchange.jpg
     
    foxhunter, Aug 11, 2019
    #14