sq_dowrite: 104 ? - DNS

This is a discussion on sq_dowrite: 104 ? - DNS ; Running bind 8.4.6-REL on RH3 and seeing the following in /var/log/messages: Jun 21 08:48:26 ns1 named[32696]: sq_dowrite: 104 What is "sq_dowrite: 104" and what is it indicative of? Thank you, Ali Darab...

+ Reply to Thread
Results 1 to 2 of 2

Thread: sq_dowrite: 104 ?

  1. sq_dowrite: 104 ?

    Running bind 8.4.6-REL on RH3 and seeing the following in /var/log/messages:

    Jun 21 08:48:26 ns1 named[32696]: sq_dowrite: 104

    What is "sq_dowrite: 104" and what is it indicative of?

    Thank you,

    Ali Darab



  2. Re: sq_dowrite: 104 ?

    > Jun 21 08:48:26 ns1 named[32696]: sq_dowrite: 104
    >
    > What is "sq_dowrite: 104" and what is it indicative of?


    in bind8/src/bin/named/ns_main.c we see the following fragment:

    int n = write(qs->s_rfd, qs->s_wbuf_send,
    qs->s_wbuf_free - qs->s_wbuf_send);
    if (n < 0) {
    if (errno != EINTR && errno != EAGAIN
    #if (EWOULDBLOCK != EAGAIN)
    && errno != EWOULDBLOCK
    #endif
    ) {
    ns_notice(ns_log_default, "sq_dowrite: %d\n", errno);
    return (-1);
    }
    }

    what this is telling you is that write() returned -1 with errno==104.
    my /usr/include/errno.h has no "104" in it so you'll have to grep yours.
    all we know for sure is that it wasn't EINTR, EAGAIN, or EWOULDBLOCK (if
    indeed EWOULDBLOCK isn't just an alias for EAGAIN on your system.)

    if we're placing bets, i'd say errno 104 is ENETUNREACH on your system,
    or perhaps ECONNRESET, and that your default route is coming and going
    due to DHCP or IGP problems.
    --
    Paul Vixie



+ Reply to Thread