if each dig request needs over 4 seconds , also NET::DNS used by ASSP
have the same big delay ; this delay was showing near to 100% cpu on 
info stat page
plus seconds of timeout sending email .Don't ask me why , but it's so.

I do not know what technique uses Frtiz to show cpu usage on "info stat" 
page however
using NET::DNS filters "info stat page" was reporting near 100% cpu.

However note that using
ps aux | grep assp.pl
was returning  a cpu usage of about 5% !!! .

On linux I never seen the same value between  "ps aux | grep assp.pl"  
and info stat page , never.
However the near to 100% signal on info stat page (with few smtp 
connections) and the time out problems
sending email , told me that there was a problem . I tried to disable 
all filtesr and then enable one by one .
I noticed that the problem (100% cpu and time out problems) was stopping 
turning to 0 all assp filters which were using  NET::DNS .

I tried to downgrade and upgrade NET::DNS .Nothing . Then Fritz wrote 
that was a DNS iussue ,so  I executed several

dig domain.com

on this server , and I found that the answer query time was really big 
(over 4 seconds for each query while on another
server with the same "dig domain" was returning queries under 0.5 sec) . 
So I agree that it's DNS iusse .

Bye
Graziano


> On Thu, 2007-10-04 at 11:36 -0600, Graziano wrote:
>   
>> DNS, correct ! Thank you.
>>
>> Infact any
>> dig anydomain.com
>> was resulting in a wait of over 4 seconds !
>>     
>
> Please excuse my ignorance by why should a DNS issue cause 100% CPU
> usage? Really seems like a bug needs to be filed against what ever is
> effected by that. Should their be a delay or etc, because of the DNS
> issues sure. But not 100% CPU usage. That's a bit insane and seems like
> horrible design.
>
> I don't commonly ever see DNS issues myself, but did have some with a
> recent BIND update with some of my split/dual zones. Not a single
> application's CPU usage increased with those DNS issues. So I see no
> reason why ASSP or a library it's using should cause that.
>
> Also if it is a library like NET::DNS shouldn't past versions of ASSP be
> effected. Or is this a new dependency of 1.3.x series? If it's always
> been using it, I have never seen the 100% CPU usage with <=1.2.6. I did
> see it with 1.3.3.1 when large emails/attachments were sent.
>
> http://bugs.gentoo.org/show_bug.cgi?id=191727
>
>   
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Assp-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/assp-user
>   

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user

Reply via email to