Hi, I got these errors (below) for several weeks just after upgrading to ASSP v2, and then they went away after that. It's been 3 months now, and the errors are back again suddenly. I'm guessing it's related to a particular email in the spam corpus, as it likely stopped sending the errors after the offending mail was overwritten or deleted. So far, I haven't noticed anything obviously wrong about any of the spam files though, however, I haven't had a chance to try to track it down any further.
Oct-18-11 10:15:01 /usr/local/assp/spam Oct-18-11 10:15:01 File Count: 14,120 Oct-18-11 10:15:01 Processing... spam with 14120 filesUse of uninitialized value $name in substitution (s///) at /opt/perl-5.10.1/lib/5.10.1/x86_64-linux-thread-multi/Encode.pm line 104. Use of uninitialized value $name in exists at /opt/perl-5.10.1/lib/5.10.1/x86_64-linux-thread-multi/Encode.pm line 107. Use of uninitialized value $find in exists at /opt/perl-5.10.1/lib/5.10.1/x86_64-linux-thread-multi/Encode/Alias.pm line 25. Use of uninitialized value $find in hash element at /opt/perl-5.10.1/lib/5.10.1/x86_64-linux-thread-multi/Encode/Alias.pm line 26. Use of uninitialized value $find in pattern match (m//) at /opt/perl-5.10.1/lib/5.10.1/x86_64-linux-thread-multi/Encode/Alias.pm line 31. (above line repeats 45 times) Use of uninitialized value $find in string eq at /opt/perl-5.10.1/lib/5.10.1/x86_64-linux-thread-multi/Encode/Alias.pm line 44. Use of uninitialized value $find in hash element at /opt/perl-5.10.1/lib/5.10.1/x86_64-linux-thread-multi/Encode/Alias.pm line 57. Use of uninitialized value $find in hash element at /opt/perl-5.10.1/lib/5.10.1/x86_64-linux-thread-multi/Encode/Alias.pm line 77. Use of uninitialized value $name in string ne at /opt/perl-5.10.1/lib/5.10.1/x86_64-linux-thread-multi/Encode.pm line 113. Use of uninitialized value $name in hash element at /opt/perl-5.10.1/lib/5.10.1/x86_64-linux-thread-multi/Encode.pm line 117. Use of uninitialized value $name in concatenation (.) or string at /opt/perl-5.10.1/lib/5.10.1/x86_64-linux-thread-multi/Encode.pm line 174. Use of uninitialized value $name in substitution (s///) at /opt/perl-5.10.1/lib/5.10.1/x86_64-linux-thread-multi/Encode.pm line 104. Use of uninitialized value $name in exists at /opt/perl-5.10.1/lib/5.10.1/x86_64-linux-thread-multi/Encode.pm line 107. Use of uninitialized value $find in exists at /opt/perl-5.10.1/lib/5.10.1/x86_64-linux-thread-multi/Encode/Alias.pm line 25. Use of uninitialized value $find in hash element at /opt/perl-5.10.1/lib/5.10.1/x86_64-linux-thread-multi/Encode/Alias.pm line 77. Use of uninitialized value $name in string ne at /opt/perl-5.10.1/lib/5.10.1/x86_64-linux-thread-multi/Encode.pm line 113. Use of uninitialized value $name in hash element at /opt/perl-5.10.1/lib/5.10.1/x86_64-linux-thread-multi/Encode.pm line 117. Use of uninitialized value $name in concatenation (.) or string at /opt/perl-5.10.1/lib/5.10.1/x86_64-linux-thread-multi/Encode.pm line 174. ASSP v 2.0.1(3.2.15) on CentOS 5, Perl 5.10.1 I'm a main release behind, but I didn't notice anything mentioning the spamdb rebuild in the new changelogs. If you need any further information, just let me know. (I was wondering if turning on debug would output more info during the rebuild process? Or is it just to show the details of the SMTP conversation?) -C ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
