Bug 2055 - External net checks and mass-check restart having issues ...?
Summary: External net checks and mass-check restart having issues ...?
Status: RESOLVED FIXED
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Libraries (show other bugs)
Version: SVN Trunk (Latest Devel Version)
Hardware: Other other
: P5 normal
Target Milestone: 2.60
Assignee: Theo Van Dinter
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-12 20:05 UTC by Theo Van Dinter
Modified: 2003-06-18 03:11 UTC (History)
1 user (show)


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Theo Van Dinter 2003-06-12 20:05:26 UTC 
mass-check -j 6 --net --restart 3000 ...

status: pre-scanning and sorting. now: 2003-06-12 18:34:11
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
status:  10% ham: 3123   spam: 3123   date: 1999-05-15 now: 2003-06-12 19:04:12
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
status:  20% ham: 6247   spam: 6245   date: 2003-05-08 now: 2003-06-12 19:36:43
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
status:  30% ham: 9369   spam: 9369   date: 2002-06-24 now: 2003-06-12 20:10:55
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
status:  40% ham: 12491  spam: 12493  date: 2003-05-14 now: 2003-06-12 20:43:50
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
status:  50% ham: 15615  spam: 15615  date: 2003-05-17 now: 2003-06-12 21:18:15
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.
Warning: unable to close filehandle DCC properly.


It didn't do this before, but I notice that there are a multiple of 6 messages
between each 10% mark which makes me think it's related to the restarting,
although I'm not sure why since DCC ought to be dead and gone when the restart
happens.
Comment 1 Theo Van Dinter 2003-06-12 20:16:52 UTC 
it seemed to only start after the DCCifd addition, but I can't see anything in
the new code that would make this happen.

The warning seems to come from perl itself.  Will see what I can find about this ...
Comment 2 Rod Begbie 2003-06-12 21:51:55 UTC 
I saw this error, but with PYZOR on Saturday morning.  The job never finished,
and I had to kill it.
Comment 3 Theo Van Dinter 2003-06-17 04:47:34 UTC 
well, the latest CVS seems to be working better:

status: pre-scanning and sorting. now: 2003-06-16 14:30:13
Out of memory!
Got an undef from readline?!?  Restarting all children, probably lost some
results. :(
status:  10% ham: 3357   spam: 3357   date: 1999-06-15 now: 2003-06-16 16:09:28
status:  20% ham: 6714   spam: 6714   date: 2003-05-09 now: 2003-06-16 17:51:50
status:  30% ham: 10071  spam: 10071  date: 2003-05-11 now: 2003-06-16 19:34:17
status:  40% ham: 13428  spam: 13428  date: 2003-05-15 now: 2003-06-16 21:15:09
status:  50% ham: 16785  spam: 16785  date: 2003-04-07 now: 2003-06-16 22:53:41
razor2 check skipped: Bad file descriptor Died at
/home/felicity/SA/spamassassin-corpora/masses/../lib/Mail/SpamAssassin/Dns.pm
line 403, <GEN2710> line 1.
razor2 check skipped: Bad file descriptor Died at
/home/felicity/SA/spamassassin-corpora/masses/../lib/Mail/SpamAssassin/Dns.pm
line 403, <GEN2984> line 1.
razor2 check skipped: Bad file descriptor Died at
/home/felicity/SA/spamassassin-corpora/masses/../lib/Mail/SpamAssassin/Dns.pm
line 403, <GEN2965> line 1.
razor2 check skipped: Bad file descriptor Died at
/home/felicity/SA/spamassassin-corpora/masses/../lib/Mail/SpamAssassin/Dns.pm
line 403, <GEN2611> line 1.
status:  60% ham: 20143  spam: 20141  date: 2003-05-01 now: 2003-06-17 00:33:13
Got an undef from readline?!?  Restarting all children, probably lost some
results. :(
status:  70% ham: 23499  spam: 23499  date: 2003-05-26 now: 2003-06-17 02:12:32
Out of memory!
Got an undef from readline?!?  Restarting all children, probably lost some
results. :(
status:  80% ham: 24854  spam: 28858  date: 2003-06-01 now: 2003-06-17 03:56:03
Got an undef from readline?!?  Restarting all children, probably lost some
results. :(
status:  90% ham: 24854  spam: 35572  date: 2003-06-09 now: 2003-06-17 05:39:59



I don't know what's up with the oom stuff.  I'm guessing that I'm hitting a
limit problem as opposed to actually oom'ing the box.

rOD: are you still having the pyzor issue?
Comment 4 Theo Van Dinter 2003-06-17 04:48:11 UTC 
I guess I'm working on this?
Comment 5 Theo Van Dinter 2003-06-18 11:11:42 UTC 
I think this is working now.  If there are any other issues with it, we can reopen.