#598 net.adns stops working if it runs into NOFILE limit

Reporter Zash
Owner Zash
Created
Updated
Stars (0)  
Tags
  • Milestone-0.9
  • Status-Fixed
  • Type-Defect
  • Priority-Medium
  1. Zash on

    debug Records for _xmpp-server._tcp.remote.example. not in cache, sending query (thread: 0x18802f0)... error Error sending DNS query: Too many open files debug remote.example has no SRV records, falling back to A/AAAA debug Records for remote.example not in cache, sending query (thread: 0x17eb3e0)... error Error sending DNS query: Too many open files debug Records for remote.example not in cache, sending query (thread: 0x16fbb70)... error Error sending DNS query: Too many open files debug DNS lookup failed to get a response for remote.exampleinfo Out of connection options, can't connect to remote.example debug No other records to try for remote.example - destroying debug Destroying outgoing session example.local->remote.example: DNS resolution failed: Too many open files debug First attempt to connect to remote.example, starting with SRV lookup... debug Records for _xmpp-server._tcp.remote.example. not in cache, sending query (thread: 0x1817df0)... ... then nothing until s2s_timeout

  2. Zash on

    Changes
    • tags Milestone-0.9
  3. Zash on

    This appears to be because net.dns adds an entry into the "waiting for response" set before getting a socket and sending the query, which can fail. The next query sees that it is already waiting for an answer and writes itself up there too. But since the query packet was never sent, no answer is ever received.

    Changes
    • tags Status-Started
    • owner Zash
  4. Zash on

    Fixed in 388281be2bc7

    Changes
    • tags Status-Fixed

New comment