Re: [Assp-test] error: RWL check failed : send: Bad file descriptor

[K Post]

To close this thread and for the sake of those who might see it later.

15261 was released which addresses a bug that incorrectly set dns server
values if NONE responded.  (this points to a problem with my dns servers
which have yet to be determined)

On Wed, Sep 16, 2015 at 9:59 AM, K Post  wrote:

> Thanks Greyhat for chiming in and sorry for so many emails all!
>
> I'm using our 3 internal DNS servers.  The ports are wide open between the
> servers.  There isn't a firewall issue.  Nothing's changed on the DNS
> servers or the firewall (I run them too).
>
> Notes (to summarize my many posts - sorry about that):
>
> 1) Things work just fine for a while after starting ASSP
>
> 2) After a couple of hours, the problem returns.  RWL and RBL "bad file"
> warnings, A and MX records don't resolve.
>
> 3) Using 3 local and fast dns servers.  using persistent connection or
> not, doesn't matter.  I have DNSServerLimit set to 2
>
> 4) *This was never a problem with 15167.  As soon as we went to 15225,
> the problem started*.
>
> 5) *After the problem shows its head*, *Infostats shows "0" for used dns
> servers* instead of showing the 2 servers ASSP has selected to use.  Once
> I restart ASSP,  the used DNS Servers line goes back to showing 2 of my 3
> servers as expected.
>
> Windows 2012 R2, fully patched.
>
>
>
> On Wed, Sep 16, 2015 at 9:50 AM, Grayhat  wrote:
>
>> :: On Wed, 16 Sep 2015 09:04:55 -0400
>> :: 

Re: [Assp-test] error: RWL check failed : send: Bad file descriptor

[K Post]

DNSReuseSocket being unticked didn't help.  Another 4 hours after
restarting and the RWL/RBL errors are back.

On Tue, Sep 15, 2015 at 5:18 PM, K Post <nntp.p...@gmail.com> wrote:

> Seems like if I let ASSP 15255 run long enough, the RWL/RBL errors also
> come back.  This was never a problem with 15167.  I haven't tried rolling
> back yet, but suspect that the problem would go away with that older
> version.
>
> I will try turning off DNSReuseSocket.  I seem to remember that being a
> problem with previous versions.
>
> Any other ideas?
>
>
> On Tue, Sep 15, 2015 at 1:01 PM, K Post <nntp.p...@gmail.com> wrote:
>
>> I've restarted several more times.  I haven't changed any settings, but
>> the RWL/RBL errors seem to have gone away.  Bad cache or something?  I am
>> getting occasional warnings in the log that Name Server x.x.x.x does not
>> respond or timed out.
>>
>> I can't imagine that it's suddenly the name servers.  It's all three of
>> them throwing this warning from time to time.  Looking at that compare (
>> http://assp.cvs.sourceforge.net/viewvc/assp/assp2/assp.pl?view=diff=text=1.24=text=1.36_format=h)
>> it looks like some of the logic has changed / code added right around that
>> warning message.   Maybe the DNS servers have always been operating the
>> same but now ASSP is more picky?  Or could something have changed where DNS
>> is queried differently?  I've got DNStimeout set to 3 seconds.  I've never
>> seen my dns servers take that long!  I also have DNSReuseSocket checked.
>>
>>
>>
>> On Mon, Sep 14, 2015 at 5:52 PM, K Post <nntp.p...@gmail.com> wrote:
>>
>>> I can't seem to figure out what's going on.  Upon restarting ASSP, the
>>> system will be good for around 2 hours, and then POW! I start getting
>>> error: RWL check failed : send: Bad file descriptor or error: RBL check
>>> failed : send: Bad file descriptor every couple of minutes.
>>>
>>> I'm also seeing no MX record found - (NXDOMAIN), missing A record, etc
>>> sporadically.
>>>
>>> This only started happening after upgrading yesterday from 15162 to
>>>  15225.  The 3 dns servers are internal and operating without issue.  ASSP
>>> is showing 1 and 2ms response times when looking to sourceforge.net
>>>
>>> I went through the changes between 15162 and 15225.  It does seem like
>>> there are some dns changes, but I don't know if any of them could be
>>> causing this problem.
>>>
>>> http://assp.cvs.sourceforge.net/viewvc/assp/assp2/assp.pl?view=diff=text=1.24=text=1.36_format=h
>>>
>>> Any thoughts as to what could be allowing ASSP to run seemingly fine for
>>> a while, and then start throwing these errors?  Is there some kind of cache
>>> that could be getting full or corrupted?
>>>
>>> thanks
>>>
>>> On Mon, Sep 14, 2015 at 11:23 AM, K Post <nntp.p...@gmail.com> wrote:
>>>
>>>> I need to dig deeper.  There are 3 fast local dns servers that seem to
>>>> be working fine.
>>>>
>>>> I'll get back with you (thanks for being so responsive).
>>>>
>>>> On Mon, Sep 14, 2015 at 11:20 AM, Thomas Eckardt <
>>>> thomas.ecka...@thockar.com> wrote:
>>>>
>>>>> The DNS server has closed the socket (connection) - or no DNS-server is
>>>>> available.
>>>>>
>>>>> Thomas
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Von:K Post <nntp.p...@gmail.com>
>>>>> An: ASSP development mailing list <assp-test@lists.sourceforge.net
>>>>> >
>>>>> Datum:  14.09.2015 17:12
>>>>> Betreff:[Assp-test] error: RWL check failed : send: Bad file
>>>>> descriptor
>>>>>
>>>>>
>>>>>
>>>>> I'm suddenly getting a lot of these lines:
>>>>>
>>>>> error: RWL check failed : send: Bad file descriptor
>>>>>
>>>>> Tried restarting ASSP, also tried restarting the machine.
>>>>>
>>>>> Goes away for a bit, but comes back after a short while.
>>>>>
>>>>> --
>>>>> ___
>>>>> Assp-test mailing list
>>>>> Assp-test@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/assp-test

Re: [Assp-test] error: RWL check failed : send: Bad file descriptor

[K Post]

Also in the logs:
can't get DNS-server answer for MX - (NO_NAME_SERVER_GIVEN)

But I see no messages about unresponsive DNS servers, the periodic tests of
the 3 show 0-3ms responses for sourceforge.net


On Wed, Sep 16, 2015 at 9:04 AM, K Post <nntp.p...@gmail.com> wrote:

> DNSReuseSocket being unticked didn't help.  Another 4 hours after
> restarting and the RWL/RBL errors are back.
>
> On Tue, Sep 15, 2015 at 5:18 PM, K Post <nntp.p...@gmail.com> wrote:
>
>> Seems like if I let ASSP 15255 run long enough, the RWL/RBL errors also
>> come back.  This was never a problem with 15167.  I haven't tried rolling
>> back yet, but suspect that the problem would go away with that older
>> version.
>>
>> I will try turning off DNSReuseSocket.  I seem to remember that being a
>> problem with previous versions.
>>
>> Any other ideas?
>>
>>
>> On Tue, Sep 15, 2015 at 1:01 PM, K Post <nntp.p...@gmail.com> wrote:
>>
>>> I've restarted several more times.  I haven't changed any settings, but
>>> the RWL/RBL errors seem to have gone away.  Bad cache or something?  I am
>>> getting occasional warnings in the log that Name Server x.x.x.x does not
>>> respond or timed out.
>>>
>>> I can't imagine that it's suddenly the name servers.  It's all three of
>>> them throwing this warning from time to time.  Looking at that compare (
>>> http://assp.cvs.sourceforge.net/viewvc/assp/assp2/assp.pl?view=diff=text=1.24=text=1.36_format=h)
>>> it looks like some of the logic has changed / code added right around that
>>> warning message.   Maybe the DNS servers have always been operating the
>>> same but now ASSP is more picky?  Or could something have changed where DNS
>>> is queried differently?  I've got DNStimeout set to 3 seconds.  I've never
>>> seen my dns servers take that long!  I also have DNSReuseSocket checked.
>>>
>>>
>>>
>>> On Mon, Sep 14, 2015 at 5:52 PM, K Post <nntp.p...@gmail.com> wrote:
>>>
>>>> I can't seem to figure out what's going on.  Upon restarting ASSP, the
>>>> system will be good for around 2 hours, and then POW! I start getting
>>>> error: RWL check failed : send: Bad file descriptor or error: RBL check
>>>> failed : send: Bad file descriptor every couple of minutes.
>>>>
>>>> I'm also seeing no MX record found - (NXDOMAIN), missing A record, etc
>>>> sporadically.
>>>>
>>>> This only started happening after upgrading yesterday from 15162 to
>>>>  15225.  The 3 dns servers are internal and operating without issue.  ASSP
>>>> is showing 1 and 2ms response times when looking to sourceforge.net
>>>>
>>>> I went through the changes between 15162 and 15225.  It does seem like
>>>> there are some dns changes, but I don't know if any of them could be
>>>> causing this problem.
>>>>
>>>> http://assp.cvs.sourceforge.net/viewvc/assp/assp2/assp.pl?view=diff=text=1.24=text=1.36_format=h
>>>>
>>>> Any thoughts as to what could be allowing ASSP to run seemingly fine
>>>> for a while, and then start throwing these errors?  Is there some kind of
>>>> cache that could be getting full or corrupted?
>>>>
>>>> thanks
>>>>
>>>> On Mon, Sep 14, 2015 at 11:23 AM, K Post <nntp.p...@gmail.com> wrote:
>>>>
>>>>> I need to dig deeper.  There are 3 fast local dns servers that seem to
>>>>> be working fine.
>>>>>
>>>>> I'll get back with you (thanks for being so responsive).
>>>>>
>>>>> On Mon, Sep 14, 2015 at 11:20 AM, Thomas Eckardt <
>>>>> thomas.ecka...@thockar.com> wrote:
>>>>>
>>>>>> The DNS server has closed the socket (connection) - or no DNS-server
>>>>>> is
>>>>>> available.
>>>>>>
>>>>>> Thomas
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Von:K Post <nntp.p...@gmail.com>
>>>>>> An: ASSP development mailing list <
>>>>>> assp-test@lists.sourceforge.net>
>>>>>> Datum:  14.09.2015 17:12
>>>>>> Betreff:[Assp-test] error: RWL check failed : send: Bad file
>>>>>> descrip

Re: [Assp-test] error: RWL check failed : send: Bad file descriptor

[K Post]

Thanks Greyhat for chiming in and sorry for so many emails all!

I'm using our 3 internal DNS servers.  The ports are wide open between the
servers.  There isn't a firewall issue.  Nothing's changed on the DNS
servers or the firewall (I run them too).

Notes (to summarize my many posts - sorry about that):

1) Things work just fine for a while after starting ASSP

2) After a couple of hours, the problem returns.  RWL and RBL "bad file"
warnings, A and MX records don't resolve.

3) Using 3 local and fast dns servers.  using persistent connection or not,
doesn't matter.  I have DNSServerLimit set to 2

4) *This was never a problem with 15167.  As soon as we went to 15225, the
problem started*.

5) *After the problem shows its head*, *Infostats shows "0" for used dns
servers* instead of showing the 2 servers ASSP has selected to use.  Once I
restart ASSP,  the used DNS Servers line goes back to showing 2 of my 3
servers as expected.

Windows 2012 R2, fully patched.



On Wed, Sep 16, 2015 at 9:50 AM, Grayhat  wrote:

> :: On Wed, 16 Sep 2015 09:04:55 -0400
> :: 

Re: [Assp-test] error: RWL check failed : send: Bad file descriptor

[K Post]

More information:
In the gui, under infostats, I see

used DNS Servers: 0 *<--- ZERO!?! *
defined DNS Servers: x.x.x.51 x.x.x.52 x.x.x.53  (there's my 3)
DNS Servers query time: min: 0.000 , avg: 0.062 , max: 3.014 (good response
times)

On Wed, Sep 16, 2015 at 9:22 AM, K Post <nntp.p...@gmail.com> wrote:

> Also in the logs:
> can't get DNS-server answer for MX - (NO_NAME_SERVER_GIVEN)
>
> But I see no messages about unresponsive DNS servers, the periodic tests
> of the 3 show 0-3ms responses for sourceforge.net
>
>
> On Wed, Sep 16, 2015 at 9:04 AM, K Post <nntp.p...@gmail.com> wrote:
>
>> DNSReuseSocket being unticked didn't help.  Another 4 hours after
>> restarting and the RWL/RBL errors are back.
>>
>> On Tue, Sep 15, 2015 at 5:18 PM, K Post <nntp.p...@gmail.com> wrote:
>>
>>> Seems like if I let ASSP 15255 run long enough, the RWL/RBL errors also
>>> come back.  This was never a problem with 15167.  I haven't tried rolling
>>> back yet, but suspect that the problem would go away with that older
>>> version.
>>>
>>> I will try turning off DNSReuseSocket.  I seem to remember that being a
>>> problem with previous versions.
>>>
>>> Any other ideas?
>>>
>>>
>>> On Tue, Sep 15, 2015 at 1:01 PM, K Post <nntp.p...@gmail.com> wrote:
>>>
>>>> I've restarted several more times.  I haven't changed any settings, but
>>>> the RWL/RBL errors seem to have gone away.  Bad cache or something?  I am
>>>> getting occasional warnings in the log that Name Server x.x.x.x does not
>>>> respond or timed out.
>>>>
>>>> I can't imagine that it's suddenly the name servers.  It's all three of
>>>> them throwing this warning from time to time.  Looking at that compare (
>>>> http://assp.cvs.sourceforge.net/viewvc/assp/assp2/assp.pl?view=diff=text=1.24=text=1.36_format=h)
>>>> it looks like some of the logic has changed / code added right around that
>>>> warning message.   Maybe the DNS servers have always been operating the
>>>> same but now ASSP is more picky?  Or could something have changed where DNS
>>>> is queried differently?  I've got DNStimeout set to 3 seconds.  I've never
>>>> seen my dns servers take that long!  I also have DNSReuseSocket checked.
>>>>
>>>>
>>>>
>>>> On Mon, Sep 14, 2015 at 5:52 PM, K Post <nntp.p...@gmail.com> wrote:
>>>>
>>>>> I can't seem to figure out what's going on.  Upon restarting ASSP, the
>>>>> system will be good for around 2 hours, and then POW! I start getting
>>>>> error: RWL check failed : send: Bad file descriptor or error: RBL check
>>>>> failed : send: Bad file descriptor every couple of minutes.
>>>>>
>>>>> I'm also seeing no MX record found - (NXDOMAIN), missing A record, etc
>>>>> sporadically.
>>>>>
>>>>> This only started happening after upgrading yesterday from 15162 to
>>>>>  15225.  The 3 dns servers are internal and operating without issue.  ASSP
>>>>> is showing 1 and 2ms response times when looking to sourceforge.net
>>>>>
>>>>> I went through the changes between 15162 and 15225.  It does seem like
>>>>> there are some dns changes, but I don't know if any of them could be
>>>>> causing this problem.
>>>>>
>>>>> http://assp.cvs.sourceforge.net/viewvc/assp/assp2/assp.pl?view=diff=text=1.24=text=1.36_format=h
>>>>>
>>>>> Any thoughts as to what could be allowing ASSP to run seemingly fine
>>>>> for a while, and then start throwing these errors?  Is there some kind of
>>>>> cache that could be getting full or corrupted?
>>>>>
>>>>> thanks
>>>>>
>>>>> On Mon, Sep 14, 2015 at 11:23 AM, K Post <nntp.p...@gmail.com> wrote:
>>>>>
>>>>>> I need to dig deeper.  There are 3 fast local dns servers that seem
>>>>>> to be working fine.
>>>>>>
>>>>>> I'll get back with you (thanks for being so responsive).
>>>>>>
>>>>>> On Mon, Sep 14, 2015 at 11:20 AM, Thomas Eckardt <
>>>>>> thomas.ecka...@thockar.com> wrote:
>>>>>>
>>>>>>> The DNS server has closed the socket (connection) - or no DNS-server
>>>>>>> is
>>>>>>> available.
>>>>>>>
>>>>

Re: [Assp-test] error: RWL check failed : send: Bad file descriptor

[Grayhat]

:: On Wed, 16 Sep 2015 09:04:55 -0400
:: 

Re: [Assp-test] error: RWL check failed : send: Bad file descriptor

[K Post]

I've restarted several more times.  I haven't changed any settings, but the
RWL/RBL errors seem to have gone away.  Bad cache or something?  I am
getting occasional warnings in the log that Name Server x.x.x.x does not
respond or timed out.

I can't imagine that it's suddenly the name servers.  It's all three of
them throwing this warning from time to time.  Looking at that compare (
http://assp.cvs.sourceforge.net/viewvc/assp/assp2/assp.pl?view=diff=text=1.24=text=1.36_format=h)
it looks like some of the logic has changed / code added right around that
warning message.   Maybe the DNS servers have always been operating the
same but now ASSP is more picky?  Or could something have changed where DNS
is queried differently?  I've got DNStimeout set to 3 seconds.  I've never
seen my dns servers take that long!  I also have DNSReuseSocket checked.



On Mon, Sep 14, 2015 at 5:52 PM, K Post <nntp.p...@gmail.com> wrote:

> I can't seem to figure out what's going on.  Upon restarting ASSP, the
> system will be good for around 2 hours, and then POW! I start getting
> error: RWL check failed : send: Bad file descriptor or error: RBL check
> failed : send: Bad file descriptor every couple of minutes.
>
> I'm also seeing no MX record found - (NXDOMAIN), missing A record, etc
> sporadically.
>
> This only started happening after upgrading yesterday from 15162 to
>  15225.  The 3 dns servers are internal and operating without issue.  ASSP
> is showing 1 and 2ms response times when looking to sourceforge.net
>
> I went through the changes between 15162 and 15225.  It does seem like
> there are some dns changes, but I don't know if any of them could be
> causing this problem.
>
> http://assp.cvs.sourceforge.net/viewvc/assp/assp2/assp.pl?view=diff=text=1.24=text=1.36_format=h
>
> Any thoughts as to what could be allowing ASSP to run seemingly fine for a
> while, and then start throwing these errors?  Is there some kind of cache
> that could be getting full or corrupted?
>
> thanks
>
> On Mon, Sep 14, 2015 at 11:23 AM, K Post <nntp.p...@gmail.com> wrote:
>
>> I need to dig deeper.  There are 3 fast local dns servers that seem to be
>> working fine.
>>
>> I'll get back with you (thanks for being so responsive).
>>
>> On Mon, Sep 14, 2015 at 11:20 AM, Thomas Eckardt <
>> thomas.ecka...@thockar.com> wrote:
>>
>>> The DNS server has closed the socket (connection) - or no DNS-server is
>>> available.
>>>
>>> Thomas
>>>
>>>
>>>
>>>
>>>
>>> Von:K Post <nntp.p...@gmail.com>
>>> An: ASSP development mailing list <assp-test@lists.sourceforge.net>
>>> Datum:  14.09.2015 17:12
>>> Betreff:[Assp-test] error: RWL check failed : send: Bad file
>>> descriptor
>>>
>>>
>>>
>>> I'm suddenly getting a lot of these lines:
>>>
>>> error: RWL check failed : send: Bad file descriptor
>>>
>>> Tried restarting ASSP, also tried restarting the machine.
>>>
>>> Goes away for a bit, but comes back after a short while.
>>>
>>> --
>>> ___
>>> Assp-test mailing list
>>> Assp-test@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/assp-test
>>>
>>>
>>>
>>>
>>>
>>>
>>> DISCLAIMER:
>>> ***
>>> This email and any files transmitted with it may be confidential, legally
>>> privileged and protected in law and are intended solely for the use of
>>> the
>>>
>>> individual to whom it is addressed.
>>> This email was multiple times scanned for viruses. There should be no
>>> known virus in this email!
>>> ***
>>>
>>>
>>> --
>>> ___
>>> Assp-test mailing list
>>> Assp-test@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/assp-test
>>>
>>
>>
>
--
___
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test

Re: [Assp-test] error: RWL check failed : send: Bad file descriptor

[K Post]

Seems like if I let ASSP 15255 run long enough, the RWL/RBL errors also
come back.  This was never a problem with 15167.  I haven't tried rolling
back yet, but suspect that the problem would go away with that older
version.

I will try turning off DNSReuseSocket.  I seem to remember that being a
problem with previous versions.

Any other ideas?


On Tue, Sep 15, 2015 at 1:01 PM, K Post <nntp.p...@gmail.com> wrote:

> I've restarted several more times.  I haven't changed any settings, but
> the RWL/RBL errors seem to have gone away.  Bad cache or something?  I am
> getting occasional warnings in the log that Name Server x.x.x.x does not
> respond or timed out.
>
> I can't imagine that it's suddenly the name servers.  It's all three of
> them throwing this warning from time to time.  Looking at that compare (
> http://assp.cvs.sourceforge.net/viewvc/assp/assp2/assp.pl?view=diff=text=1.24=text=1.36_format=h)
> it looks like some of the logic has changed / code added right around that
> warning message.   Maybe the DNS servers have always been operating the
> same but now ASSP is more picky?  Or could something have changed where DNS
> is queried differently?  I've got DNStimeout set to 3 seconds.  I've never
> seen my dns servers take that long!  I also have DNSReuseSocket checked.
>
>
>
> On Mon, Sep 14, 2015 at 5:52 PM, K Post <nntp.p...@gmail.com> wrote:
>
>> I can't seem to figure out what's going on.  Upon restarting ASSP, the
>> system will be good for around 2 hours, and then POW! I start getting
>> error: RWL check failed : send: Bad file descriptor or error: RBL check
>> failed : send: Bad file descriptor every couple of minutes.
>>
>> I'm also seeing no MX record found - (NXDOMAIN), missing A record, etc
>> sporadically.
>>
>> This only started happening after upgrading yesterday from 15162 to
>>  15225.  The 3 dns servers are internal and operating without issue.  ASSP
>> is showing 1 and 2ms response times when looking to sourceforge.net
>>
>> I went through the changes between 15162 and 15225.  It does seem like
>> there are some dns changes, but I don't know if any of them could be
>> causing this problem.
>>
>> http://assp.cvs.sourceforge.net/viewvc/assp/assp2/assp.pl?view=diff=text=1.24=text=1.36_format=h
>>
>> Any thoughts as to what could be allowing ASSP to run seemingly fine for
>> a while, and then start throwing these errors?  Is there some kind of cache
>> that could be getting full or corrupted?
>>
>> thanks
>>
>> On Mon, Sep 14, 2015 at 11:23 AM, K Post <nntp.p...@gmail.com> wrote:
>>
>>> I need to dig deeper.  There are 3 fast local dns servers that seem to
>>> be working fine.
>>>
>>> I'll get back with you (thanks for being so responsive).
>>>
>>> On Mon, Sep 14, 2015 at 11:20 AM, Thomas Eckardt <
>>> thomas.ecka...@thockar.com> wrote:
>>>
>>>> The DNS server has closed the socket (connection) - or no DNS-server is
>>>> available.
>>>>
>>>> Thomas
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Von:K Post <nntp.p...@gmail.com>
>>>> An: ASSP development mailing list <assp-test@lists.sourceforge.net>
>>>> Datum:  14.09.2015 17:12
>>>> Betreff:[Assp-test] error: RWL check failed : send: Bad file
>>>> descriptor
>>>>
>>>>
>>>>
>>>> I'm suddenly getting a lot of these lines:
>>>>
>>>> error: RWL check failed : send: Bad file descriptor
>>>>
>>>> Tried restarting ASSP, also tried restarting the machine.
>>>>
>>>> Goes away for a bit, but comes back after a short while.
>>>>
>>>> --
>>>> ___
>>>> Assp-test mailing list
>>>> Assp-test@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/assp-test
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> DISCLAIMER:
>>>> ***
>>>> This email and any files transmitted with it may be confidential,
>>>> legally
>>>> privileged and protected in law and are intended solely for the use of
>>>> the
>>>>
>>>> individual to whom it is addressed.
>>>> This email was multiple times scanned for viruses. There should be no
>>>> known virus in this email!
>>>> ***
>>>>
>>>>
>>>> --
>>>> ___
>>>> Assp-test mailing list
>>>> Assp-test@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/assp-test
>>>>
>>>
>>>
>>
>
--
___
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test

Re: [Assp-test] error: RWL check failed : send: Bad file descriptor

[K Post]

I need to dig deeper.  There are 3 fast local dns servers that seem to be
working fine.

I'll get back with you (thanks for being so responsive).

On Mon, Sep 14, 2015 at 11:20 AM, Thomas Eckardt <thomas.ecka...@thockar.com
> wrote:

> The DNS server has closed the socket (connection) - or no DNS-server is
> available.
>
> Thomas
>
>
>
>
>
> Von:K Post <nntp.p...@gmail.com>
> An: ASSP development mailing list <assp-test@lists.sourceforge.net>
> Datum:  14.09.2015 17:12
> Betreff:        [Assp-test] error: RWL check failed : send: Bad file
> descriptor
>
>
>
> I'm suddenly getting a lot of these lines:
>
> error: RWL check failed : send: Bad file descriptor
>
> Tried restarting ASSP, also tried restarting the machine.
>
> Goes away for a bit, but comes back after a short while.
>
> --
> ___
> Assp-test mailing list
> Assp-test@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/assp-test
>
>
>
>
>
>
> DISCLAIMER:
> ***
> This email and any files transmitted with it may be confidential, legally
> privileged and protected in law and are intended solely for the use of the
>
> individual to whom it is addressed.
> This email was multiple times scanned for viruses. There should be no
> known virus in this email!
> ***
>
>
> --
> ___
> Assp-test mailing list
> Assp-test@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/assp-test
>
--
___
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test

[Assp-test] error: RWL check failed : send: Bad file descriptor

[K Post]

I'm suddenly getting a lot of these lines:

error: RWL check failed : send: Bad file descriptor

Tried restarting ASSP, also tried restarting the machine.

Goes away for a bit, but comes back after a short while.
--
___
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test

Re: [Assp-test] error: RWL check failed : send: Bad file descriptor

[Thomas Eckardt]

The DNS server has closed the socket (connection) - or no DNS-server is 
available.

Thomas





Von:K Post <nntp.p...@gmail.com>
An: ASSP development mailing list <assp-test@lists.sourceforge.net>
Datum:  14.09.2015 17:12
Betreff:    [Assp-test] error: RWL check failed : send: Bad file 
descriptor



I'm suddenly getting a lot of these lines:

error: RWL check failed : send: Bad file descriptor

Tried restarting ASSP, also tried restarting the machine.

Goes away for a bit, but comes back after a short while.
--
___
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test






DISCLAIMER:
***
This email and any files transmitted with it may be confidential, legally 
privileged and protected in law and are intended solely for the use of the 

individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no 
known virus in this email!
***

--
___
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test

Re: [Assp-test] error: RWL check failed : send: Bad file descriptor

[K Post]

I can't seem to figure out what's going on.  Upon restarting ASSP, the
system will be good for around 2 hours, and then POW! I start getting
error: RWL check failed : send: Bad file descriptor or error: RBL check
failed : send: Bad file descriptor every couple of minutes.

I'm also seeing no MX record found - (NXDOMAIN), missing A record, etc
sporadically.

This only started happening after upgrading yesterday from 15162 to
 15225.  The 3 dns servers are internal and operating without issue.  ASSP
is showing 1 and 2ms response times when looking to sourceforge.net

I went through the changes between 15162 and 15225.  It does seem like
there are some dns changes, but I don't know if any of them could be
causing this problem.
http://assp.cvs.sourceforge.net/viewvc/assp/assp2/assp.pl?view=diff=text=1.24=text=1.36_format=h

Any thoughts as to what could be allowing ASSP to run seemingly fine for a
while, and then start throwing these errors?  Is there some kind of cache
that could be getting full or corrupted?

thanks

On Mon, Sep 14, 2015 at 11:23 AM, K Post <nntp.p...@gmail.com> wrote:

> I need to dig deeper.  There are 3 fast local dns servers that seem to be
> working fine.
>
> I'll get back with you (thanks for being so responsive).
>
> On Mon, Sep 14, 2015 at 11:20 AM, Thomas Eckardt <
> thomas.ecka...@thockar.com> wrote:
>
>> The DNS server has closed the socket (connection) - or no DNS-server is
>> available.
>>
>> Thomas
>>
>>
>>
>>
>>
>> Von:K Post <nntp.p...@gmail.com>
>> An: ASSP development mailing list <assp-test@lists.sourceforge.net>
>> Datum:  14.09.2015 17:12
>> Betreff:[Assp-test] error: RWL check failed : send: Bad file
>> descriptor
>>
>>
>>
>> I'm suddenly getting a lot of these lines:
>>
>> error: RWL check failed : send: Bad file descriptor
>>
>> Tried restarting ASSP, also tried restarting the machine.
>>
>> Goes away for a bit, but comes back after a short while.
>>
>> --
>> ___
>> Assp-test mailing list
>> Assp-test@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/assp-test
>>
>>
>>
>>
>>
>>
>> DISCLAIMER:
>> ***
>> This email and any files transmitted with it may be confidential, legally
>> privileged and protected in law and are intended solely for the use of the
>>
>> individual to whom it is addressed.
>> This email was multiple times scanned for viruses. There should be no
>> known virus in this email!
>> ***
>>
>>
>> --
>> ___
>> Assp-test mailing list
>> Assp-test@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/assp-test
>>
>
>
--
___
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test