Bug 5053 - ug 16 11:19:59 Takahe spamd[28688]: Use of uninitialized value in hash element at /sw/lib/perl5/site_perl/5.8.6/Mail/SpamAssassin/Timeout.pm line 144.\n
Summary: ug 16 11:19:59 Takahe spamd[28688]: Use of uninitialized value in hash elemen...
Status: RESOLVED WORKSFORME
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamc/spamd (show other bugs)
Version: SVN Trunk (Latest Devel Version)
Hardware: Other other
: P5 normal
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-16 18:18 UTC by jon stevens
Modified: 2008-03-10 06:37 UTC (History)
1 user (show)



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 jon stevens 2006-08-16 18:18:30 UTC
ug 16 11:19:59 Takahe spamd[28688]: Use of uninitialized value in hash element
at /sw/lib/perl5/site_perl/5.8.6/Mail/SpamAssassin/Timeout.pm line 144.\n
Comment 1 Theo Van Dinter 2006-12-30 19:13:11 UTC
Hrm.  I can't reproduce this, and no one else has reported it.  Line 144 is:

    local $SIG{ALRM} = sub { $timedout++; die "__alarm__ignore__\n" };

%SIG is perl internal (defined), and $timedout is defined a few lines above, so
I don't see how anything can be uninitialized.

Since there's been nothing new since August, I'm closing as WFM.  If this is
still an issue, please provide more information (such as platform, perl version,
etc,) and details about when this issue occurs, if only on certain messages, etc.

Thanks.
Comment 2 Andrew Vasilyev 2007-07-25 15:12:25 UTC
We have the same warnings (a lot of) in our logs:
spamd[78842]: Use of uninitialized value in hash element 
at /usr/local/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Timeout.pm line 144.

FreeBSD 6.2-STABLE
Perl 5.8.8 (as one can see above).

Can you suggest any additional debug measures to elaborate the reason of this 
issue? We'll try to do the best.
Comment 3 Justin Mason 2007-07-26 02:15:04 UTC
(In reply to comment #2)
> Can you suggest any additional debug measures to elaborate the reason of this 
> issue? We'll try to do the best.

you could try adding lines like

  warn "DEBUG $timedout";

before and after the function runs; they'll be logged too.  but to be honest, I
think it's harmless...
Comment 4 Andrew Vasilyev 2007-07-26 08:42:33 UTC
(In reply to comment #3)
> you could try adding lines like
>   warn "DEBUG $timedout";
> before and after the function runs; they'll be logged too.  but to be 
honest, I
> think it's harmless...

  Warnings in logs are about "hash element", is $timedout a hash element?

Comment 5 Dale Blount 2008-03-10 06:37:52 UTC
I get quite a few of these too, looks to be constantly between 8 and 9% of processed messages.

# grep 'Timeout.pm line 144' /var/log/mail | wc -l
4408
# grep 'processing message' /var/log/mail | wc -l
49711

# grep 'Timeout.pm line 144' /var/log/mail.1 | wc -l
10982
# grep 'processing message' /var/log/mail.1 | wc -l
127307

# grep 'Timeout.pm line 144' /var/log/mail.2 | wc -l
12667
# grep 'processing message' /var/log/mail.2 | wc -l
142493

4 spamassassin -V 
SpamAssassin version 3.2.4
  running on Perl version 5.8.8

Arch Linux 2.6.23


I'm also having problems with all spamd children getting hung up every few days or so - not sure if it's related to this message or not.  Andrew, do you have any symptoms along with this warning?