Uploaded image for project: 'OpenDNSSEC'
  1. OpenDNSSEC
  2. OPENDNSSEC-725

Signerd should handle AXFR disconnect gracefully

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 2.0.0
    • Fix Version/s: 1.4.10, 2.0.0
    • Component/s: Signer
    • Labels:
      None

      Description

      I'm very satisfied with my setup, but I'm quite frequently getting the
      following error in my system's log:

      ods-signer: [socket] unable to handle outgoing tcp response: write()
      failed (Broken pipe)

      I couldn't find any information on this problem, so I've tried looking
      into it. Here is what I think is happening:

      1. nsd is periodically checking if its zone is up to date by issuing an
      AXFR query to the ods-signerd
      2. The ods-signerd starts delivering the zone
      3. nsd realizes that the SOA has not changed and its zone is already up
      to date. It (half) closes the TCP connection as per RFC 5936, Section
      4.1.1
      4. osd-signerd keeps sending more information on the zone (which to my
      understanding it shouldn't). As a result nsd sends a TCP RST.
      ods-signerd does not handle this gracefully, thus the socket error
      message.

      So as far as I can tell, it's safe for me to ignore the error.

        Attachments

          Activity

            People

            Assignee:
            yuri Yuri Schaeffer
            Reporter:
            yuri Yuri Schaeffer
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: