Bug 4295 - DnsResolver.pm line 338 loops
Summary: DnsResolver.pm line 338 loops
Status: RESOLVED DUPLICATE of bug 4278
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Libraries (show other bugs)
Version: SVN Trunk (Latest Devel Version)
Hardware: PC FreeBSD
: P5 normal
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL: http://ezri.ijs.si/~mark/tmp/sa-bt.txt
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-30 15:55 UTC by Mark Martinec
Modified: 2005-04-30 09:17 UTC (History)
0 users



Attachment Type Modified Status Actions Submitter/CLA Status

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Martinec 2005-04-30 15:55:46 UTC
I've been running recent SA 3.1 CVS code for a couple of days now  
under amavisd-new without problems. Today I found two processes stuck  
in a loop. In both cases the Perl traceback reported same line numbers:  
.../5.8.6/Mail/SpamAssassin/DnsResolver.pm line 270 and line 338,  
which seems to indicate the loop (lasting for several hours) occurs in:  
  
sub search {  
...   
   while (!defined($answerpkt)) {  
    $self->poll_responses(-1);     # -1 = as long as it takes  
  }  
  
The full traceback (as much as a timeout signal could collect and log)  
is in the ref URL. Just a word of explanation: the amavisd timeout  
went off after 30 seconds, reported a traceback, but the process  
was left looping until manually killed several hours later.  
  
  Mark
Comment 1 Sidney Markowitz 2005-04-30 17:17:51 UTC
This is the same as bug 4278 which I fixed in rev 16149 just a few days ago.

The summary in that bug says Win32 and Cygwin, but the problem turned out not to
be platform specific.

I'm closing this as a duplicate. Please open another bug if you still see a
problem. That shouldn't be possible, because the infinite loop code you found
now has a timeout associated with it.


*** This bug has been marked as a duplicate of 4278 ***