Article delegate-en/1505 of [1-5169] on the server localhost:119
  upper oldest olders older1 this newer1 newers latest
search
[Top/Up] [oldest] - [Older+chunk] - [Newer+chunk] - [newest + Check]

Newsgroups: mail-lists.delegate-en

[DeleGate-En] Re: Delegate 7.8.1 on W2k occasional DNS problems
24 Jan 2002 18:29:13 GMT "Ferenc Toth" <pxqcqbdyi-iievoczqqlzr.ml@ml.delegate.org>


On Thu, 24 Jan 2002 13:40:21 +0100, Ferenc Toth wrote:

>On Thu, 24 Jan 2002 20:47:57 +0900 (JST), Yutaka Sato wrote:
>> |Now I've changed RESOLV to dns,cache,sys (at the time when I've
>> |installed delegate for the first time I had some trouble with the
>> |RESOLV=dns that's why I've dropped it). I'll need a day or two to
>> |verify if this solves the problem. Meanwhile can you suggest anything I
>> |should try? Maybe is there a way to get a little bit more detailed
>> |error message for that FATAL RecvFrom ...?
>>
>>To tell the truth, I'm not sure if it is FATAL or not.  I inserted the
>>"FATAL" message (and sleep() before next recv()) at DeleGate/7.2.0
>>when I noticed that DNS DeleGate falls into infinite loop on failure
>>return (-1) from recvfrom().  I found the situation on my Linux machine
>>(RedHat6.1 which is still working the name server of the DELEGATE.ORG
>>domain) but could not found the reason why recvfrom() rarely returns -1.
>>Although I could escape the infinite loop by making delay (by sleep(10))
>>before continuing to next recvfrom() at that time, the real cause of 
>>the problem is not studied yet.  Anyway no fatal aftereffect has been
>>found after I escaped the problem like above, so far.  But if it is
>>really fatal in your situation, I'll study it more in higher priority.
[...]

One more thing. I've noticed that the RecvFrom errors are logged right
after some busy time. So if delegate services multiple queries in a
very short time, a RecvFrom error will follow. Don't ask me why are
there multiple queries for the same domain name. (192.168.99.5 is an
internal linux machine running bind9.2 servicing internal DNS queries
and forwarding all other requests to delegate).

01/24 13:15:46.35 [332] 0+175: {R} QUERY www.uwsg.iu.edu IN A
01/24 13:15:46.35 [332] 0+175: [0.000s] 192.168.99.5
01/24 13:15:46.35 [332] 0+176: {R} QUERY www.uwsg.iu.edu IN A
01/24 13:15:46.36 [332] 0+176: [0.010s] 192.168.99.5
01/24 13:15:46.36 [332] 0+177: {R} QUERY www.uwsg.iu.edu IN A
01/24 13:15:46.36 [332] 0+177: [0.000s] 192.168.99.5
01/24 13:15:46.36 [332] 0+178: {R} QUERY www.uwsg.iu.edu IN A
01/24 13:15:46.36 [332] 0+178: [0.000s] 192.168.99.5
01/24 13:15:46.36 [332] 0+179: FATAL RecvFrom(9) = -1, errno=0
01/24 13:15:56.37 [332] 0+180: FATAL RecvFrom(9) = -1, errno=0
[...]

or

01/23 21:01:14.58 [752] 0+205: {R} QUERY www.soccer-sites.com IN A
01/23 21:01:14.58 [752] 0+205: [0.000s] 192.168.100.12
01/23 21:01:14.58 [752] 0+206: {R} QUERY www.soccer-sites.com IN A
01/23 21:01:14.58 [752] 0+206: [0.000s] 192.168.100.12
01/23 21:01:14.58 [752] 0+207: {R} QUERY www.soccer-sites.com IN A
01/23 21:01:14.58 [752] 0+207: [0.000s] 192.168.99.5
01/23 21:01:14.58 [752] 0+208: {R} QUERY www.soccer-sites.com IN A
01/23 21:01:14.59 [752] 0+208: [0.010s] 192.168.100.12
01/23 21:01:14.59 [752] 0+209: {R} QUERY www.soccer-sites.com IN A
01/23 21:01:14.59 [752] 0+209: [0.000s] 192.168.99.5
01/23 21:01:14.59 [752] 0+210: {R} QUERY www.soccer-sites.com IN A
01/23 21:01:14.59 [752] 0+210: [0.000s] 192.168.100.12
01/23 21:01:14.59 [752] 0+211: {R} QUERY www.soccer-sites.com IN A
01/23 21:01:14.59 [752] 0+211: [0.000s] 192.168.99.5
01/23 21:01:14.59 [752] 0+212: {R} QUERY www.soccer-sites.com IN A
01/23 21:01:14.60 [752] 0+212: [0.010s] 192.168.100.12
01/23 21:01:14.60 [752] 0+213: FATAL RecvFrom(9) = -1, errno=0
01/23 21:01:24.60 [752] 0+214: FATAL RecvFrom(9) = -1, errno=0
01/23 21:01:34.60 [752] 0+215: FATAL RecvFrom(9) = -1, errno=0
01/23 21:01:44.60 [752] 0+216: FATAL RecvFrom(9) = -1, errno=0
[...]



  admin search upper oldest olders older1 this newer1 newers latest
[Top/Up] [oldest] - [Older+chunk] - [Newer+chunk] - [newest + Check]
@_@V