perl error
I just installed an update for Perl for Fedora 4 and now... Dec 17 11:08:02 mooch spamd[3144]: List::Util object version 1.14 does not match bootstrap parameter 1.18 at /usr/lib/perl5/5.8.6/i386-linux-thread-multi/XSLoader.pm line 92. Dec 17 11:08:02 mooch spamd[3144]: List::Util object version 1.14 does not match bootstrap parameter 1.18 at /usr/lib/perl5/5.8.6/i386-linux-thread-multi/List/Util.pm line 30. Dec 17 11:08:04 mooch spamd[3144]: Undefined subroutine &Scalar::Util::weaken called at /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi/DBI.pm line 279. using CPAN, I updated DBI. Scalar::Util is up to date as is List::Util -- Steve
Spamd/perl error.
I am having trouble running spamd. This started after I installed FuzzyOCR, found errors, upgraded perl to 5.8.8 to resolve those errors and ended up with this: [EMAIL PROTECTED] ~]# /etc/init.d/spamassassin start Starting spamd: Can't locate object method "register_domain" via package "IO::Socket::INET" at /usr/local/lib/perl5/5.8.8/i686-linux/IO/Socket/INET.pm line 22. Compilation failed in require at /usr/bin/spamd line 44. BEGIN failed--compilation aborted at /usr/bin/spamd line 79. [FAILED] The INET installed is: cpan[12]> install IO::Socket::INET IO::Socket::INET is up to date (1.31). I've posted the results of spamassassin -D --lint here: http://avas.cnc.bc.ca/lint.txt If I neglect the warnings at the bottom of lint then spamd should start anyways but it doesn't. I'm pretty sure its a perl problem at this point, but I'm not strong enough yet in perl to get to the bottom of it. Anyone out there that could help out? = Kevin W. Gagel Network Administrator Information Technology Services (250) 562-2131 local 448 My Blog: http://mail.cnc.bc.ca/blogs/gagel --- The College of New Caledonia, Visit us at http://www.cnc.bc.ca Virus scanning is done on all incoming and outgoing email. Anti-spam information for CNC can be found at http://avas.cnc.bc.ca ---
botnet 7 perl error
I only found one reference to this error searching the net
Use of uninitialized value in string eq at /etc/mail/spamassassin/Botnet.pm
line 564, line 7
This appears to be the line of code in Botnet.pm although I could be wrong
Mail::SpamAssassin::Plugin::dbg("Botnet: miss (" . $tests . ")");
can anyone point me to anything else that solves this please?
I have disabled botnet for now
Machine is centos 4.4, perl 5.8.5, sa is 3.1.7
- rh
--
Robert - Abba Communications
Computer & Internet Services
(509) 624-7159 - www.abbacomm.net
Perl Error: CHARSETS_LIKELY_TO_FP_AS_CAPS on SA
Hi, I'm running: #spamassassin --version SpamAssassin version 3.1.9 running on Perl version 5.8.8 and would greatly appreciate a help in troubleshooting this problem. I'm getting the error messages below from spamassaassin --lint, but it seems to be bogus, since CHARSETS_LIKELY_TO_FP_AS_CAPS is defined in /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin: Any ideas? Thanks! Terry / # These are generic constants that may be used across several modules @SA_VARS = qw( HARVEST_DNSBL_PRIORITY MBX_SEPARATOR MAX_BODY_LINE_LENGTH MAX_HEADER_KEY_LENGTH MAX_HEADER_VALUE_LENGTH MAX_HEADER_LENGTH ARITH_EXPRESSION_LEXER AI_TIME_UNKNOWN CHARSETS_LIKELY_TO_FP_AS_CAPS MAX_URI_LENGTH ); / [30813] warn: plugin: failed to parse plugin (from @INC): Bareword "Mail::SpamAssassin::Constants::CHARSETS_LIKELY_TO_FP_AS_CAPS" not allowed while "strict subs" in use at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/Plugin/HeaderEval.pm line 968. [30813] warn: Compilation failed in require at (eval 89) line 1. [30813] warn: plugin: failed to create instance of plugin Mail::SpamAssassin::Plugin::HeaderEval: Can't locate object method "new" via package "Mail::SpamAssassin::Plugin::HeaderEval" at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/Plugin/HeaderEval.pm line 39. [30813] warn: plugin: failed to parse plugin (from @INC): "CHARSETS_LIKELY_TO_FP_AS_CAPS" is not exported by the Mail::SpamAssassin::Constants module [30813] warn: Can't continue after import errors at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/Plugin/MIMEEval.pm line 22 [30813] warn: BEGIN failed--compilation aborted at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/Plugin/MIMEEval.pm line 22. [30813] warn: Compilation failed in require at (eval 91) line 1. [30813] warn: plugin: failed to create instance of plugin Mail::SpamAssassin::Plugin::MIMEEval: Can't locate object method "new" via package "Mail::SpamAssassin::Plugin::MIMEEval" at (eval 92) line 1. [30813] warn: FuzzyOcr: Cannot find executable for tesseract [30813] warn: Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2669. [30813] warn: Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2669. [30813] warn: Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2669. [30813] warn: Number found where operator expected at (eval 266) line 10, near "} [30813] warn: [30813] warn: 1" [30813] warn: (Missing operator before [30813] warn: [30813] warn: 1?) [30813] warn: rules: failed to run header tests, skipping some: syntax error at (eval 266) line 6, at EOF [30813] warn: Global symbol "$plugin" requires explicit package name at (eval 266) line 7. [30813] warn: syntax error at (eval 266) line 11, near "; [30813] warn: }" [30813] warn: Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2669. [30813] warn: Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2669. [30813] warn: Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2669. [30813] warn: Number found where operator expected at (eval 267) line 10, near "} [30813] warn: [30813] warn: 1" [30813] warn: (Missing operator before [30813] warn: [30813] warn: 1?) [30813] warn: rules: failed to run header tests, skipping some: syntax error at (eval 267) line 6, at EOF [30813] warn: Global symbol "$plugin" requires explicit package name at (eval 267) line 7. [30813] warn: syntax error at (eval 267) line 11, near "; [30813] warn: }" [30813] warn: Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2669. [30813] warn: Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2669. [30813] warn: Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2669. [30813] warn: Number found where operator expected at (eval 268) line 10, near "} [30813] warn: [30813] warn: 1" [30813] warn: (Missing operator before [30813] warn: [30813] warn: 1?) [30813] warn: rules: failed to run header tests, skipping some: syntax error at (eval 268) line 6, at EOF [30813] warn: Global symbol "$plugin" requires explicit package name at (eval 268) line 7. [30813] warn: syntax error at (eval 268) line 11, near "; [30813] warn: }" [30813] warn: Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 2669. [
SA3.1 Perl Error Net::Ident
Hello, i have a perl Error from SA3.1 "spamassasin --lint -D" : [8599] warn: Prototype mismatch: sub Net::Ident::_export_hooks vs () at /usr/lib/perl5/site_perl/5.6.1/Net/Ident.pm line 516. [8599] warn: Compression not available at (eval 43) line 1 Is this a "real" problem? Running Perl 5.6.1/ Net::Ident latest Version. Thanks Uwe
Re: botnet 7 perl error
R Lists06 wrote: I have disabled botnet for now You can still use BotNet 0.6, it works fine HTH Oliver -- Oliver Schulze L. | Get my e-mail after a captcha in: Asuncion - Paraguay | http://tinymailto.com/oliver
sa-update / perl error again
Hi, Running CentOS5 with SpamAssassin v3.3.1-2.el5 installed via yum I remember getting this error a while ago, and it was fixed (don't remember how, but I think just by upgrading), but now it's happening again: Subroutine Net::DNS::Resolver::Base::AF_INET6 redefined at /usr/lib/perl5/5.8.8/Exporter.pm line 65. at /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/Net/DNS/Resolver/Base.pm line 65 The results I get from Google regarding this are all circa 2008. The only hints I can find seem to suggest to remove perl-IO-Socket-INET6, but trying to do so using yum (I don't want to start using another method of package management) tells me that spamassassin is a dependency and will also be removed - obviously undesirable. Perl is up to date on the machinge. Am I the only one seeing this? What can I do to fix it?
Perl error after upgrade to 3.2.3
Apologies if I am asking in the wrong place, since I can see that there are several possible reasons. We have just upgraded to SpamAssassin 3.2.3 on an elderly 386 box running Red Hat 9. At the same time I used CPAN to upgrade any out-of-date perl modules. Now, when SA starts, we get the following error: Starting SpamAssassin daemon... [23172] error: Can't locate Sys/Syslog/Win32.pm in @INC (@INC contains: /usr/local/lib/perl5/site_perl/5.8.8/i686-linux /usr/local/lib/perl5/site_perl/5.8.8 /usr/local/lib/perl5/5.8.8/i686-linux /usr/local/lib/perl5/5.8.8 /usr/local/lib/perl5/site_perl) at (eval 11) line 2. [23172] error: BEGIN failed--compilation aborted at (eval 11) line 2. done. The error comes up twice, but SA does in fact start, and appears to be functioning normally. Does anyone know why it suddenly wants to load a Win32 module? Jon Jon Armitage System Administrator, 365 Media Group
Re: Perl Error: CHARSETS_LIKELY_TO_FP_AS_CAPS on SA
On Wed, 8 Jul 2009, Terry Carmen wrote: SpamAssassin version 3.1.9 That's *way* old. Is there any chance you can upgrade to 3.2.5? -- John Hardin KA7OHZhttp://www.impsec.org/~jhardin/ jhar...@impsec.orgFALaholic #11174 pgpk -a jhar...@impsec.org key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 --- A sword is never a killer, it is but a tool in the killer's hands. -- Lucius Annaeus Seneca (Martial) 4BC-65AD --- 12 days until the 40th anniversary of Apollo 11 landing on the Moon
Re: Perl Error: CHARSETS_LIKELY_TO_FP_AS_CAPS on SA
> On Wed, 8 Jul 2009, Terry Carmen wrote: > >> SpamAssassin version 3.1.9 > > That's *way* old. Is there any chance you can upgrade to 3.2.5? I'm actually upgrading the entire server, but wanted to make sure I didn't migrate the problem along with the configuration. Terry > > -- > John Hardin KA7OHZhttp://www.impsec.org/~jhardin/ > jhar...@impsec.orgFALaholic #11174 pgpk -a jhar...@impsec.org > key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 > --- >A sword is never a killer, it is but a tool in the killer's hands. >-- Lucius Annaeus Seneca (Martial) 4BC-65AD > --- > 12 days until the 40th anniversary of Apollo 11 landing on the Moon > -- CNY Support, LLC Web. Database. Business http://www.cnysupport.com
Re: Perl Error: CHARSETS_LIKELY_TO_FP_AS_CAPS on SA
On Wed, 8 Jul 2009, Terry Carmen wrote: On Wed, 8 Jul 2009, Terry Carmen wrote: SpamAssassin version 3.1.9 That's *way* old. Is there any chance you can upgrade to 3.2.5? I'm actually upgrading the entire server, but wanted to make sure I didn't migrate the problem along with the configuration. Well, if the problem _does_ migrate, you're more likely to get help troubleshooting it running 3.2.5 than you are running 3.1.9... :) -- John Hardin KA7OHZhttp://www.impsec.org/~jhardin/ jhar...@impsec.orgFALaholic #11174 pgpk -a jhar...@impsec.org key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 --- A sword is never a killer, it is but a tool in the killer's hands. -- Lucius Annaeus Seneca (Martial) 4BC-65AD --- 12 days until the 40th anniversary of Apollo 11 landing on the Moon
Re: Perl Error: CHARSETS_LIKELY_TO_FP_AS_CAPS on SA
On Wed, 8 Jul 2009, Terry Carmen wrote: I'm running: #spamassassin --version SpamAssassin version 3.1.9 running on Perl version 5.8.8 and would greatly appreciate a help in troubleshooting this problem. I'm getting the error messages below from spamassaassin --lint, but it seems to be bogus, since CHARSETS_LIKELY_TO_FP_AS_CAPS is defined in /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin: Any ideas? [30813] warn: plugin: failed to create instance of plugin Mail::SpamAssassin::Plugin::HeaderEval: Can't locate object method "new" via package "Mail::SpamAssassin::Plugin::HeaderEval" at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/Plugin/HeaderEval.pm line 39. [30813] warn: plugin: failed to parse plugin (from @INC): "CHARSETS_LIKELY_TO_FP_AS_CAPS" is not exported by the Mail::SpamAssassin::Constants module ...etc. It looks like you have multiple different versions partially installed. The HeaderEval plugin does not exist in 3.1.9, and CHARSETS_LIKELY_TO_FP_AS_CAPS is not defined in the 3.1.9 Constants.pm file. I'd suggest completely uninstalling SA and reinstalling 3.2.5 from scratch. Note that you need to install SA upgrades using the same method every time; you can't mix CPAN and distro packages and tarball, things will get confused. I suspect that's what happened here. -- John Hardin KA7OHZhttp://www.impsec.org/~jhardin/ jhar...@impsec.orgFALaholic #11174 pgpk -a jhar...@impsec.org key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 --- A sword is never a killer, it is but a tool in the killer's hands. -- Lucius Annaeus Seneca (Martial) 4BC-65AD --- 12 days until the 40th anniversary of Apollo 11 landing on the Moon
Re: Perl Error: CHARSETS_LIKELY_TO_FP_AS_CAPS on SA
> On Wed, 8 Jul 2009, Terry Carmen wrote: > >> I'm running: >> >> #spamassassin --version >> SpamAssassin version 3.1.9 >> running on Perl version 5.8.8 >> >> and would greatly appreciate a help in troubleshooting this problem. >> >> I'm getting the error messages below from spamassaassin --lint, but it seems >> to be bogus, since CHARSETS_LIKELY_TO_FP_AS_CAPS is defined in >> /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin: >> >> Any ideas? > >> [30813] warn: plugin: failed to create instance of plugin >> Mail::SpamAssassin::Plugin::HeaderEval: Can't locate object method "new" via >> package "Mail::SpamAssassin::Plugin::HeaderEval" at >> /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/Plugin/HeaderEval.pm line >> 39. > >> [30813] warn: plugin: failed to parse plugin (from @INC): >> "CHARSETS_LIKELY_TO_FP_AS_CAPS" is not exported by the >> Mail::SpamAssassin::Constants module > > ...etc. > > It looks like you have multiple different versions partially installed. > The HeaderEval plugin does not exist in 3.1.9, and > CHARSETS_LIKELY_TO_FP_AS_CAPS is not defined in the 3.1.9 Constants.pm > file. > > I'd suggest completely uninstalling SA and reinstalling 3.2.5 from > scratch. > > Note that you need to install SA upgrades using the same method every > time; you can't mix CPAN and distro packages and tarball, things will get > confused. I suspect that's what happened here. That's probably a good guess. There are a ton of SA dependencies and I believe that's exactly what happened. It seems to be running OK, so I'll just wait until the new server is ready, and reinstall it. Thanks for the reply! Terry
Re: Perl Error: CHARSETS_LIKELY_TO_FP_AS_CAPS on SA
On Thu, 9 Jul 2009, Terry Carmen wrote: Note that you need to install SA upgrades using the same method every time; you can't mix CPAN and distro packages and tarball, things will get confused. I suspect that's what happened here. That's probably a good guess. There are a ton of SA dependencies and I believe that's exactly what happened. That comment only applies to SA itself, not the various CPAN libraries (e.g. Net::DNS) that it depends on. I personally have not had problems using CPAN to install non-SA modules with a distro-installed SA package. -- John Hardin KA7OHZhttp://www.impsec.org/~jhardin/ jhar...@impsec.orgFALaholic #11174 pgpk -a jhar...@impsec.org key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 --- 11 days until the 40th anniversary of Apollo 11 landing on the Moon
Re: sa-update / perl error again
On 12/31/11 10:46 PM, email builder wrote: Hi, Running CentOS5 with SpamAssassin v3.3.1-2.el5 installed via yum I remember getting this error a while ago, and it was fixed (don't remember how, but I think just by upgrading), but now it's happening again: Subroutine Net::DNS::Resolver::Base::AF_INET6 redefined at /usr/lib/perl5/5.8.8/Exporter.pm line 65. at /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/Net/DNS/Resolver/Base.pm line 65 are you still running perl 5.8.8? (perl -v) if you have multiple perl sitelibs, you might have a conflict. cd /usr/lib/perl5. ls. how many vendor_perl and site_perl's do you have? or, you could just delete (manually) IO-Socket-INET6 (make a backup first!) on freebsd (with perl 5.10.1): /usr/local/lib/perl5/5.10.1/man/man3/IO::Socket::INET6.3.gz /usr/local/lib/perl5/site_perl/5.10.1/IO/Socket/INET6.pm /usr/local/lib/perl5/site_perl/5.10.1/mach/auto/IO/Socket/INET6 /usr/local/lib/perl5/site_perl/5.10.1/mach/auto/IO/Socket/INET6/.packlist on fedora, try: find /usr/lib/ -name 'INET6*' (back them up) The results I get from Google regarding this are all circa 2008. The only hints I can find seem to suggest to remove perl-IO-Socket-INET6, but trying to do so using yum (I don't want to start using another method of package management) tells me that spamassassin is a dependency and will also be removed - obviously undesirable. Perl is up to date on the machinge. no its not :-) perl is at 5.14.* something now, but don't update it, it might now help. -- Michael Scheidell, CTO o: 561-999-5000 d: 561-948-2259 >*| *SECNAP Network Security Corporation * Best Mobile Solutions Product of 2011 * Best Intrusion Prevention Product * Hot Company Finalist 2011 * Best Email Security Product * Certified SNORT Integrator __ This email has been scanned and certified safe by SpammerTrap(r). For Information please see http://www.spammertrap.com/ __
Re: sa-update / perl error again
>> Running CentOS5 with SpamAssassin v3.3.1-2.el5 installed via yum >> >> I remember getting this error a while ago, and it was fixed (don't >> remember how, but I think just by upgrading), but now it's >> happening again: >> >> Subroutine Net::DNS::Resolver::Base::AF_INET6 redefined at >> /usr/lib/perl5/5.8.8/Exporter.pm line 65. >> at >> > /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/Net/DNS/Resolver/Base.pm >> line 65 > > are you still running perl 5.8.8? > > (perl -v) Yes, "still". I say that because that's the newest Centos 5 provides. > if you have multiple perl sitelibs, you might have a conflict. > > cd /usr/lib/perl5. > > ls. how many vendor_perl and site_perl's do you have? cd /usr/lib/perl5/ ls 5.8.8 site_perl vendor_perl I'm not sure what this tells you, but maybe this is helpful: locate INET6.pm /usr/lib/perl5/vendor_perl/5.8.8/IO/Socket/INET6.pm > or, you could just delete (manually) IO-Socket-INET6 (make a backup first!) > on freebsd (with perl 5.10.1): > > /usr/local/lib/perl5/5.10.1/man/man3/IO::Socket::INET6.3.gz > /usr/local/lib/perl5/site_perl/5.10.1/IO/Socket/INET6.pm > /usr/local/lib/perl5/site_perl/5.10.1/mach/auto/IO/Socket/INET6 > /usr/local/lib/perl5/site_perl/5.10.1/mach/auto/IO/Socket/INET6/.packlist > > on fedora, try: > > find /usr/lib/ -name 'INET6*' > (back them up) Same result as above: /usr/lib/perl5/vendor_perl/5.8.8/IO/Socket/INET6.pm As I stated in my inquiry, I'd prefer to do my package management via yum if at all possible. Yum tells me to uninstall this package, spamassassin depends on it so has to be removed also. So it does not seem like a good idea to remove it out from under SA >> The results I get from Google regarding this are all circa >> 2008. The only hints I can find seem to suggest to remove >> perl-IO-Socket-INET6, but trying to do so using yum (I don't >> want to start using another method of package management) >> tells me that spamassassin is a dependency and will also be >> removed - obviously undesirable. >> >> Perl is up to date on the machinge. > > no its not :-) Yes, it is :-) Centos/RHEL 5 seems to maintain 5.8.8 with its own updates or some such thing. Thank you for your help
Re: sa-update / perl error again
Anyone have any other insights? Thanks! >>> Running CentOS5 with SpamAssassin v3.3.1-2.el5 installed via yum > >>> >>> I remember getting this error a while ago, and it was fixed (don't >>> remember how, but I think just by upgrading), but now it's >>> happening again: >>> >>> Subroutine Net::DNS::Resolver::Base::AF_INET6 redefined at >>> /usr/lib/perl5/5.8.8/Exporter.pm line 65. >>> at >>> >> > /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/Net/DNS/Resolver/Base.pm >>> line 65 >> >> are you still running perl 5.8.8? >> >> (perl -v) > > Yes, "still". I say that because that's the newest Centos 5 > provides. > >> if you have multiple perl sitelibs, you might have a conflict. >> >> cd /usr/lib/perl5. >> >> ls. how many vendor_perl and site_perl's do you have? > > cd /usr/lib/perl5/ > ls > > 5.8.8 site_perl vendor_perl > > I'm not sure what this tells you, but maybe this is helpful: > > locate INET6.pm > > /usr/lib/perl5/vendor_perl/5.8.8/IO/Socket/INET6.pm > >> or, you could just delete (manually) IO-Socket-INET6 (make a backup first!) >> on freebsd (with perl 5.10.1): >> >> /usr/local/lib/perl5/5.10.1/man/man3/IO::Socket::INET6.3.gz >> /usr/local/lib/perl5/site_perl/5.10.1/IO/Socket/INET6.pm >> /usr/local/lib/perl5/site_perl/5.10.1/mach/auto/IO/Socket/INET6 >> /usr/local/lib/perl5/site_perl/5.10.1/mach/auto/IO/Socket/INET6/.packlist >> >> on fedora, try: >> >> find /usr/lib/ -name 'INET6*' >> (back them up) > > Same result as above: > > /usr/lib/perl5/vendor_perl/5.8.8/IO/Socket/INET6.pm > > As I stated in my inquiry, I'd prefer to do my package management > via yum if at all possible. Yum tells me to uninstall this package, > spamassassin depends on it so has to be removed also. So it does > not seem like a good idea to remove it out from under SA > >>> The results I get from Google regarding this are all circa >>> 2008. The only hints I can find seem to suggest to remove >>> perl-IO-Socket-INET6, but trying to do so using yum (I don't >>> want to start using another method of package management) >>> tells me that spamassassin is a dependency and will also be >>> removed - obviously undesirable. >>> >>> Perl is up to date on the machinge. >> >> no its not :-) > > Yes, it is :-) Centos/RHEL 5 seems to maintain 5.8.8 with its own updates or > some such thing. > > Thank you for your help >
Re: sa-update / perl error again
What is the Net::DNS version, are you pure ipv6 and are you 64-bit? Also, have you opened a bug with centos or redhat? Try removing/commenting all your cf files especially anything dealing with ip's. Other than that, I would likely update net dns with cpan at least temporarily to see if it fixes thinks. Regards, KAM email builder wrote: Anyone have any other insights? Thanks! >>> Running CentOS5 with SpamAssassin v3.3.1-2.el5 installed via yum > >>> >>> I remember getting this error a while ago, and it was fixed (don't >>> remember how, but I think just by upgrading), but now it's >>> happening again: >>> >>> Subroutine Net::DNS::Resolver::Base::AF_INET6 redefined at >>> /usr/lib/perl5/5.8.8/Exporter.pm line 65. >>>at >>> >> > /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/Net/DNS/Resolver/Base.pm >>> line 65 >> >> are you still running perl 5.8.8? >> >> (perl -v) > > Yes, "still". I say that because that's the newest Centos 5 > provides. > >> if you have multiple perl sitelibs, you might have a conflict. >> >> cd /usr/lib/perl5. >> >> ls. how many vendor_perl and site_perl's do you have? > > cd /usr/lib/perl5/ > ls > > 5.8.8 site_perl vendor_perl > > I'm not sure what this tells you, but maybe this is helpful: > > locate INET6.pm > > /usr/lib/perl5/vendor_perl/5.8.8/IO/Socket/INET6.pm > >> or, you could just delete (manually) IO-Socket-INET6 (make a backup first!) >> on freebsd (with perl 5.10.1): >> >> /usr/local/lib/perl5/5.10.1/man/man3/IO::Socket::INET6.3.gz >> /usr/local/lib/perl5/site_perl/5.10.1/IO/Socket/INET6.pm >> /usr/local/lib/perl5/site_perl/5.10.1/mach/auto/IO/Socket/INET6 >> /usr/local/lib/perl5/site_perl/5.10.1/mach/auto/IO/Socket/INET6/.packlist >> >> on fedora, try: >> >> find /usr/lib/ -name 'INET6*' >> (back them up) > > Same result as above: > > /usr/lib/perl5/vendor_perl/5.8.8/IO/Socket/INET6.pm > > As I stated in my inquiry, I'd prefer to do my package management > via yum if at all possible. Yum tells me to uninstall this package, > spamassassin depends on it so has to be removed also. So it does > not seem like a good idea to remove it out from under SA > >>> The results I get from Google regarding this are all circa >>> 2008. The only hints I can find seem to suggest to remove >>> perl-IO-Socket-INET6, but trying to do so using yum (I don't >>> want to start using another method of package management) >>> tells me that spamassassin is a dependency and will also be >>> removed - obviously undesirable. >>> >>> Perl is up to date on the machinge. >> >> no its not :-) > > Yes, it is :-) Centos/RHEL 5 seems to maintain 5.8.8 with its own updates or > some such thing. > > Thank you for your help >
Re: sa-update / perl error again
On 04/01/12 07:35, email builder wrote: Anyone have any other insights? Thanks! I have spamassassin-3.3.2-2.el5 installed from rpmforge on el5 - that package, besides being more up to date than the distro version also does not require perl-IO-Socket-INET6. I suspect your version does not really require perl-IO-Socket-INET6 either. Do you actually need perl-IO-Socket-INET6? I assume not as you tried to remove it. What does the following show: rpm -q --requires perl-IO-Socket-INET6 I would update SpamAssassin from rpmforge and then remove perl-IO-Socket-INET6. For reference, here are the perl packages I have installed on my system running SA/Amavisd-new/Clam (.el5 = distro, .rf = rpmforge, .rfx = rpmforge-extras) # rpm -q spamassassin amavisd-new clamav spamassassin-3.3.2-2.el5.rfx.x86_64 amavisd-new-2.6.6-1.el5.rf.x86_64 clamav-0.97.3-1.el5.rf.x86_64 # rpm -qa perl* | sort perl-5.8.8-32.el5_7.6.x86_64 perl-Archive-Tar-1.39.1-1.el5_5.2.noarch perl-Archive-Zip-1.16-1.2.1.noarch perl-Authen-SASL-2.15-1.el5.rf.noarch perl-BerkeleyDB-0.43-1.el5.rf.x86_64 perl-Bit-Vector-6.4-2.2.2.1.x86_64 perl-Carp-Clan-5.3-1.2.1.noarch perl-Compress-Raw-Bzip2-2.037-1.el5.rf.x86_64 perl-Compress-Raw-Zlib-2.037-1.el5.rf.x86_64 perl-Convert-ASN1-0.20-1.1.noarch perl-Convert-BinHex-1.119-2.2.el5.rf.noarch perl-Convert-TNEF-0.17-3.2.el5.rf.noarch perl-Convert-UUlib-1.34-1.el5.rf.x86_64 perl-Crypt-OpenSSL-Random-0.04-1.el5.rf.x86_64 perl-Crypt-OpenSSL-RSA-0.26-1.el5.rf.x86_64 perl-Date-Calc-5.4-1.2.2.1.x86_64 perl-DBI-1.52-2.el5.x86_64 perl-Digest-HMAC-1.01-15.noarch perl-Digest-SHA1-2.11-1.2.1.x86_64 perl-Digest-SHA-5.50-1.el5.rf.x86_64 perl-Email-Date-Format-1.002-1.el5.rf.noarch perl-Encode-Detect-1.01-1.el5.rf.x86_64 perl-Error-0.17016-1.el5.rf.noarch perl-Geography-Countries-2009041301-1.el5.rf.noarch perl-Git-1.7.6.4-1.el5.rf.x86_64 perl-HTML-Parser-3.59-1.el5.x86_64 perl-HTML-Tagset-3.10-2.1.1.noarch perl-IO-Compress-2.037-1.el5.rfx.noarch perl-IO-Multiplex-1.10-1.el5.rf.noarch perl-IO-Socket-SSL-1.01-1.fc6.noarch perl-IO-stringy-2.110-1.2.el5.rf.noarch perl-IO-Zlib-1.04-4.2.1.noarch perl-IP-Country-2.27-1.el5.rf.noarch perl-libwww-perl-5.805-1.1.1.noarch perl-Mail-DKIM-0.39-1.el5.rf.noarch perl-Mail-SPF-2.006-1.el5.rf.noarch perl-MailTools-2.08-1.el5.rf.noarch perl-MIME-Lite-3.027-1.el5.rf.noarch perl-MIME-tools-5.420-2.el5.rf.noarch perl-NetAddr-IP-4.044-1.el5.rf.x86_64 perl-Net-DNS-0.59-3.el5.x86_64 perl-Net-Ident-1.23-1.el5.rf.noarch perl-Net-IP-1.25-2.fc6.noarch perl-Net-Server-0.99-1.el5.rf.noarch perl-Net-SMTP-SSL-1.01-1.el5.rf.noarch perl-Net-SSLeay-1.30-4.fc6.x86_64 perl-Parse-Syslog-1.10-1.el5.rf.noarch perl-Pod-Escapes-1.04-1.2.el5.rf.noarch perl-Pod-Simple-3.16-1.el5.rf.noarch perl-Razor-Agent-2.84-1.el5.rf.x86_64 perl-SGMLSpm-1.03ii-16.2.1.noarch perl-Socket6-0.19-3.fc6.x86_64 perl-String-CRC32-1.4-2.fc6.x86_64 perl-Test-Pod-1.45-1.el5.rf.noarch perl-TimeDate-1.16-5.el5.noarch perl-Unix-Syslog-1.1-1.el5.rf.x86_64 perl-URI-1.35-3.noarch perl-version-0.91-1.el5.rf.x86_64
Re: sa-update / perl error again
On 04/01/12 15:30, Ned Slider wrote: What does the following show: rpm -q --requires perl-IO-Socket-INET6 Oops, I meant: rpm -q --whatrequires perl-IO-Socket-INET6
Re: sa-update / perl error again
On Wed, 04 Jan 2012 08:46:16 -0500, Kevin A. McGrail wrote: What is the Net::DNS version, are you pure ipv6 and are you 64-bit? in gentoo/funtoo its just perl-cleaner all but it does not handle arch changes Also, have you opened a bug with centos or redhat? if more do this centos would be better :-) Try removing/commenting all your cf files especially anything dealing with ips. Other than that, I would likely update net dns with cpan at least temporarily to see if it fixes thinks. bad suggestion !
Re: sa-update / perl error again
>What is the Net::DNS version, are you pure ipv6 and are you 64-bit? perl-Net-DNS-0.63-1.el5.rf I don't use IPv6 that I know of (the errant package is installed whether I like it or not as a dependency of spamassassin). 32 bit. >Also, have you opened a bug with centos or redhat? I've asked for help on the CentOS users mailing list. So far not much to go on except maybe it's a conflict with a package from a non-CentOS repo (rpmforge?). >Try removing/commenting all your cf files especially anything dealing with >ip's. > >Other than that, I would likely update net dns with cpan at least temporarily >to see if it fixes thinks. >Regards, >KAM > > >email builder wrote: >Anyone have any other insights? Thanks! >> >> > Running CentOS5 with SpamAssassin v3.3.1-2.el5 installed via yum >>> > > I remember getting this error a while ago, and it was fixed (don't > remember how, but I think just by upgrading), but now it's > happening again: > > Subroutine Net::DNS::Resolver::Base::AF_INET6 redefined at > /usr/lib/perl5/5.8.8/Exporter.pm line 65. > at > >>> /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/Net/DNS/Resolver/Base.pm > line 65 are you still running perl 5.8.8? (perl -v) >>> >>> ! Yes, "still". I say that because that's the newest Centos 5 >>> provides. >>> if you have multiple perl sitelibs, you might have a conflict. cd /usr/lib/perl5. ls. how many vendor_perl and site_perl's do you have? >>> >>> cd /usr/lib/perl5/ >>> ls >>> >>> 5.8.8 site_perl vendor_perl >>> >>> I'm not sure what this tells you, but maybe this is helpful: >>> >>> locate INET6.pm >>> >>> /usr/lib/perl5/vendor_perl/5.8.8/IO/Socket/INET6.pm >>> or, you could just delete (manually) IO-Socket-INET6 (make a backup first!) on freebsd (with perl 5.10.1): /usr/local/lib/perl5/5.10.1/man/man3/IO::Socket::INET6.3.gz /usr/local/lib/perl5/site_perl/5.10.1/IO/Socket/INET6.pm /usr/local/lib/perl5/site_perl/5.10.1/mach/auto/IO/Socket/INET6 /usr/local/lib/perl5/site_perl/5.10.1/mach/auto/IO/Socket/INET6/.packlist on fedora, try: find /usr/lib/ -name 'INET6*' (back them up) >>> >>> Same result as above: >>> >>> /usr/lib/perl5/vendor_perl/5.8.8/IO/Socket/INET6.pm >>> >>> As I stated in my inquiry, I'd prefer to do my package management >>> via yum if at all possible. Yum tells me to uninstall this package, >>> spamassassin depends on it so has to be removed also. So it does >>> not seem like a good idea to remove it out from under SA >>> > The results I get from Google regarding this are all circa > 2008. The only hints I can find seem to suggest to remove > perl-IO-Socket-INET6, but trying to do so using yum (I don't > want to start using another method of package management) > tells me that spamassassin is a dependency and will also be > removed - obviously undesirable. > > Perl is up to date on the machinge. no its not :-) >>> >>> Yes, it is :-) Centos/RHEL 5 seems to maintain 5.8.8 with its own updates >>> or >>> some such thing. >>> >>> Thank you for your help >>> >> > >
Re: sa-update / perl error again
> I have spamassassin-3.3.2-2.el5 installed from rpmforge on el5 - that > package, > besides being more up to date than the distro version also does not require > perl-IO-Socket-INET6. I suspect your version does not really require > perl-IO-Socket-INET6 either. You may be right. It was suggested that there may be a conflict due to mixing of packages between CentOS and other (rpmforge?) repos, so maybe it'd sure be nice if CentOS had more up to date software and there was no need to resort to using other repos (rpmforge doesn't have such up to date packages either in some cases I've noted). > Do you actually need perl-IO-Socket-INET6? I assume not as you tried to > remove > it. I did not try to remove it, only saw others suggesting to remove it on the 'net. > What does the following show: > > rpm -q --requires perl-IO-Socket-INET6 perl(:MODULE_COMPAT_5.8.8) perl(Carp) perl(Errno) perl(Exporter) perl(IO::Socket) perl(Socket) perl(Socket6) perl(strict) rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(VersionedDependencies) <= 3.0.3-1 > I would update SpamAssassin from rpmforge and then remove > perl-IO-Socket-INET6. Would I lose my current configuration in the process? it's a bit elaborate. IIRC, I'd have to temporarily disable CentOS repo to get the rpmforge one? Your opinion is that there's no fixing it without dumping my current SA package? > For reference, here are the perl packages I have installed on my system > running > SA/Amavisd-new/Clam (.el5 = distro, .rf = rpmforge, .rfx = rpmforge-extras) > > > # rpm -q spamassassin amavisd-new clamav > spamassassin-3.3.2-2.el5.rfx.x86_64 > amavisd-new-2.6.6-1.el5.rf.x86_64 > clamav-0.97.3-1.el5.rf.x86_64 > > > # rpm -qa perl* | sort > perl-5.8.8-32.el5_7.6.x86_64 > perl-Archive-Tar-1.39.1-1.el5_5.2.noarch > perl-Archive-Zip-1.16-1.2.1.noarch > perl-Authen-SASL-2.15-1.el5.rf.noarch > perl-BerkeleyDB-0.43-1.el5.rf.x86_64 > perl-Bit-Vector-6.4-2.2.2.1.x86_64 > perl-Carp-Clan-5.3-1.2.1.noarch > perl-Compress-Raw-Bzip2-2.037-1.el5.rf.x86_64 > perl-Compress-Raw-Zlib-2.037-1.el5.rf.x86_64 > perl-Convert-ASN1-0.20-1.1.noarch > perl-Convert-BinHex-1.119-2.2.el5.rf.noarch > perl-Convert-TNEF-0.17-3.2.el5.rf.noarch > perl-Convert-UUlib-1.34-1.el5.rf.x86_64 > perl-Crypt-OpenSSL-Random-0.04-1.el5.rf.x86_64 > perl-Crypt-OpenSSL-RSA-0.26-1.el5.rf.x86_64 > perl-Date-Calc-5.4-1.2.2.1.x86_64 > perl-DBI-1.52-2.el5.x86_64 > perl-Digest-HMAC-1.01-15.noarch > perl-Digest-SHA1-2.11-1.2.1.x86_64 > perl-Digest-SHA-5.50-1.el5.rf.x86_64 > perl-Email-Date-Format-1.002-1.el5.rf.noarch > perl-Encode-Detect-1.01-1.el5.rf.x86_64 > perl-Error-0.17016-1.el5.rf.noarch > perl-Geography-Countries-2009041301-1.el5.rf.noarch > perl-Git-1.7.6.4-1.el5.rf.x86_64 > perl-HTML-Parser-3.59-1.el5.x86_64 > perl-HTML-Tagset-3.10-2.1.1.noarch > perl-IO-Compress-2.037-1.el5.rfx.noarch > perl-IO-Multiplex-1.10-1.el5.rf.noarch > perl-IO-Socket-SSL-1.01-1.fc6.noarch > perl-IO-stringy-2.110-1.2.el5.rf.noarch > perl-IO-Zlib-1.04-4.2.1.noarch > perl-IP-Country-2.27-1.el5.rf.noarch > perl-libwww-perl-5.805-1.1.1.noarch > perl-Mail-DKIM-0.39-1.el5.rf.noarch > perl-Mail-SPF-2.006-1.el5.rf.noarch > perl-MailTools-2.08-1.el5.rf.noarch > perl-MIME-Lite-3.027-1.el5.rf.noarch > perl-MIME-tools-5.420-2.el5.rf.noarch > perl-NetAddr-IP-4.044-1.el5.rf.x86_64 > perl-Net-DNS-0.59-3.el5.x86_64 > perl-Net-Ident-1.23-1.el5.rf.noarch > perl-Net-IP-1.25-2.fc6.noarch > perl-Net-Server-0.99-1.el5.rf.noarch > perl-Net-SMTP-SSL-1.01-1.el5.rf.noarch > perl-Net-SSLeay-1.30-4.fc6.x86_64 > perl-Parse-Syslog-1.10-1.el5.rf.noarch > perl-Pod-Escapes-1.04-1.2.el5.rf.noarch > perl-Pod-Simple-3.16-1.el5.rf.noarch > perl-Razor-Agent-2.84-1.el5.rf.x86_64 > perl-SGMLSpm-1.03ii-16.2.1.noarch > perl-Socket6-0.19-3.fc6.x86_64 > perl-String-CRC32-1.4-2.fc6.x86_64 > perl-Test-Pod-1.45-1.el5.rf.noarch > perl-TimeDate-1.16-5.el5.noarch > perl-Unix-Syslog-1.1-1.el5.rf.x86_64 > perl-URI-1.35-3.noarch > perl-version-0.91-1.el5.rf.x86_64 >
Re: sa-update / perl error again
>> What does the following show: >> >> rpm -q --requires perl-IO-Socket-INET6 >> > > Oops, I meant: > > rpm -q --whatrequires perl-IO-Socket-INET6 no package requires perl-IO-Socket-INET6 Woa wait a minute! Then why this??? yum remove perl-IO-Socket-INET6 Loaded plugins: fastestmirror Setting up Remove Process Resolving Dependencies --> Running transaction check ---> Package perl-IO-Socket-INET6.noarch 0:2.51-2.fc6 set to be erased --> Processing Dependency: perl(IO::Socket::INET6) for package: spamassassin --> Running transaction check ---> Package spamassassin.i386 0:3.3.1-2.el5 set to be erased --> Processing Dependency: perl(Mail::SpamAssassin) for package: amavisd-new --> Running transaction check ---> Package amavisd-new.i386 0:2.6.6-1.el5.rf set to be erased --> Finished Dependency Resolution Dependencies Resolved == Package Arch Version Repository Size == Removing: perl-IO-Socket-INET6 noarch 2.51-2.fc6 installed 22 k Removing for dependencies: amavisd-new i386 2.6.6-1.el5.rf installed 2.7 M spamassassin i386 3.3.1-2.el5 installed 3.1 M Transaction Summary == Remove 3 Package(s) Reinstall 0 Package(s) Downgrade 0 Package(s) Is this ok [y/N]:
Re: sa-update / perl error again
email builder wrote: What does the following show: rpm -q --requires perl-IO-Socket-INET6 Oops, I meant: rpm -q --whatrequires perl-IO-Socket-INET6 no package requires perl-IO-Socket-INET6 Try rpm -q --whatrequires 'perl(IO::Socket::INET6)' - Perl dependencies in RPM-land are rarely expressed in terms of the package names: --> Running transaction check ---> Package perl-IO-Socket-INET6.noarch 0:2.51-2.fc6 set to be erased --> Processing Dependency: perl(IO::Socket::INET6) for package: spamassassin ^^^ For my own RPM-based systems, I keep my own .spec file around since even the RPMForge package pulls in too many other things that I don't use. It's just an older version of the RPMForge one (the one from SA v3.2.3), lightly updated as necessary to build the current release without build errors. -kgd
Re: sa-update / perl error again
On 04/01/12 21:33, email builder wrote: What is the Net::DNS version, are you pure ipv6 and are you 64-bit? perl-Net-DNS-0.63-1.el5.rf You are in no man's land there - the distro uses perl-Net-DNS-0.59-3.el5 and the latest rpmforge package is perl-Net-DNS-0.66-1.el5.rfx. If you're going to use rpmforge packages, keep them up to date (you'll need to enable the rpmforge-extras repo).
Re: sa-update / perl error again
On 04/01/12 21:41, email builder wrote: I have spamassassin-3.3.2-2.el5 installed from rpmforge on el5 - that package, besides being more up to date than the distro version also does not require perl-IO-Socket-INET6. I suspect your version does not really require perl-IO-Socket-INET6 either. You may be right. It was suggested that there may be a conflict due to mixing of packages between CentOS and other (rpmforge?) repos, so maybe it'd sure be nice if CentOS had more up to date software and there was no need to resort to using other repos (rpmforge doesn't have such up to date packages either in some cases I've noted). Do you actually need perl-IO-Socket-INET6? I assume not as you tried to remove it. I did not try to remove it, only saw others suggesting to remove it on the 'net. What does the following show: rpm -q --requires perl-IO-Socket-INET6 perl(:MODULE_COMPAT_5.8.8) perl(Carp) perl(Errno) perl(Exporter) perl(IO::Socket) perl(Socket) perl(Socket6) perl(strict) rpmlib(CompressedFileNames)<= 3.0.4-1 rpmlib(PayloadFilesHavePrefix)<= 4.0-1 rpmlib(VersionedDependencies)<= 3.0.3-1 I would update SpamAssassin from rpmforge and then remove perl-IO-Socket-INET6. Would I lose my current configuration in the process? it's a bit elaborate. IIRC, I'd have to temporarily disable CentOS repo to get the rpmforge one? Your opinion is that there's no fixing it without dumping my current SA package? You have two choices: 1. Update SA to the rpmforge package that doesn't require perl-IO-Socket-INET6 and then uninstall it. 2. Force uninstall perl-IO-Socket-INET6 with your current SA package: rpm -e --force perl-IO-Socket-INET6 and deal with yum/rpm complaining about missing deps in future.
Re: sa-update / perl error again
On 2012-01-04 23:22, Ned Slider wrote: On 04/01/12 21:41, email builder wrote: I have spamassassin-3.3.2-2.el5 installed from rpmforge on el5 - that package, besides being more up to date than the distro version also does not require perl-IO-Socket-INET6. I suspect your version does not really require perl-IO-Socket-INET6 either. You may be right. It was suggested that there may be a conflict due to mixing of packages between CentOS and other (rpmforge?) repos, so maybe it'd sure be nice if CentOS had more up to date software and there was no need to resort to using other repos (rpmforge doesn't have such up to date packages either in some cases I've noted). Do you actually need perl-IO-Socket-INET6? I assume not as you tried to remove it. I did not try to remove it, only saw others suggesting to remove it on the 'net. What does the following show: rpm -q --requires perl-IO-Socket-INET6 perl(:MODULE_COMPAT_5.8.8) perl(Carp) perl(Errno) perl(Exporter) perl(IO::Socket) perl(Socket) perl(Socket6) perl(strict) rpmlib(CompressedFileNames)<= 3.0.4-1 rpmlib(PayloadFilesHavePrefix)<= 4.0-1 rpmlib(VersionedDependencies)<= 3.0.3-1 I would update SpamAssassin from rpmforge and then remove perl-IO-Socket-INET6. Would I lose my current configuration in the process? it's a bit elaborate. IIRC, I'd have to temporarily disable CentOS repo to get the rpmforge one? Your opinion is that there's no fixing it without dumping my current SA package? You have two choices: 1. Update SA to the rpmforge package that doesn't require perl-IO-Socket-INET6 and then uninstall it. 2. Force uninstall perl-IO-Socket-INET6 with your current SA package: rpm -e --force perl-IO-Socket-INET6 and deal with yum/rpm complaining about missing deps in future. or install SA from source - VERY easy and no dependency party. remove the SA rpm and your /etc/mail/spamassassin will remain untouched (make backup first)
Re: sa-update / perl error again
What does the following show: >> rpm -q --requires perl-IO-Socket-INET6 >>> >>> Oops, I meant: >>> >>> rpm -q --whatrequires perl-IO-Socket-INET6 >> >> no package requires perl-IO-Socket-INET6 > > Try rpm -q --whatrequires 'perl(IO::Socket::INET6)' - Perl dependencies > in RPM-land are rarely expressed in terms of the package names: Yeah: spamassassin-3.3.1-2.el5 >> --> Running transaction check >> ---> Package perl-IO-Socket-INET6.noarch 0:2.51-2.fc6 set to be erased >> --> Processing Dependency: perl(IO::Socket::INET6) for package: > spamassassin > ^^^ > > For my own RPM-based systems, I keep my own .spec file around since even > the RPMForge package pulls in too many other things that I don't use. > It's just an older version of the RPMForge one (the one from SA v3.2.3), > lightly updated as necessary to build the current release without build > errors.
Re: sa-update / perl error again
>>> What is the Net::DNS version, are you pure ipv6 and are you 64-bit? >> >> >> perl-Net-DNS-0.63-1.el5.rf >> > > You are in no man's land there - the distro uses perl-Net-DNS-0.59-3.el5 > and the latest rpmforge package is perl-Net-DNS-0.66-1.el5.rfx. > > If you're going to use rpmforge packages, keep them up to date (you'll > need to enable the rpmforge-extras repo). Hrm, not sure how that could happen, since I don't have rpmforge disabled. How could yum not be seeing the newer package? cat /etc/yum.repos.d/rpmforge.repo ### Name: RPMforge RPM Repository for RHEL 5 - dag ### URL: http://rpmforge.net/ [rpmforge] name = RHEL $releasever - RPMforge.net - dag baseurl = http://apt.sw.be/redhat/el5/en/$basearch/rpmforge mirrorlist = http://apt.sw.be/redhat/el5/en/mirrors-rpmforge #mirrorlist = file:///etc/yum.repos.d/mirrors-rpmforge enabled = 1 protect = 0 gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmforge-dag gpgcheck = 1 [rpmforge-extras] name = RHEL $releasever - RPMforge.net - extras baseurl = http://apt.sw.be/redhat/el5/en/$basearch/extras mirrorlist = http://apt.sw.be/redhat/el5/en/mirrors-rpmforge-extras #mirrorlist = file:///etc/yum.repos.d/mirrors-rpmforge-extras enabled = 0 protect = 0 gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmforge-dag gpgcheck = 1 [rpmforge-testing] name = RHEL $releasever - RPMforge.net - testing baseurl = http://apt.sw.be/redhat/el5/en/$basearch/testing mirrorlist = http://apt.sw.be/redhat/el5/en/mirrors-rpmforge-testing #mirrorlist = file:///etc/yum.repos.d/mirrors-rpmforge-testing enabled = 0 protect = 0 gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmforge-dag gpgcheck = 1
Re: sa-update / perl error again
What is the Net::DNS version, are you pure ipv6 and are you > 64-bit? >>> >>> perl-Net-DNS-0.63-1.el5.rf >>> >> >> You are in no man's land there - the distro uses > perl-Net-DNS-0.59-3.el5 >> and the latest rpmforge package is perl-Net-DNS-0.66-1.el5.rfx. >> >> If you're going to use rpmforge packages, keep them up to date > (you'll >> need to enable the rpmforge-extras repo). > > Hrm, not sure how that could happen, since I don't have rpmforge disabled. > > How could yum not be seeing the newer package? > > cat /etc/yum.repos.d/rpmforge.repo Well, knowing there was a newer package out there, hopefully no matter where yum looked for it, I took a chance and removed it: rpm -e --nodeps perl-Net-DNS Then when I asked yum about it again, it found the new one from the CentOS repo, so I installed it... it also needed to install perl-Net-IP which I didn't have. So now I have perl-Net-DNS-0.59-3.el5.i386.rpm Running sa-update on the command line doesn't produce errors, so I guess that the cron won't either. H... how did it get like that in the first place? (and how'd you know to check perl-Net-DNS?)
Re: sa-update / perl error again
On 1/4/2012 8:41 PM, email builder wrote: H... how did it get like that in the first place? (and how'd you know to check perl-Net-DNS?) The use of packages and extra repositories makes it very difficult to really pinpoint the exact error but the errors you posted pointed more to Net::DNS than anything else. I'm glad it appears you've fixed the issue with an upgraded version. I personally like to use package-based systems to get a base OS and then install the core items that define the purpose of the machine either from source or from custom spec files. It doesn't scale well but it's good for very specific control of versioning and interoperability. Regards, KAM
Re: sa-update / perl error again
On 05/01/12 01:28, email builder wrote: What is the Net::DNS version, are you pure ipv6 and are you 64-bit? perl-Net-DNS-0.63-1.el5.rf You are in no man's land there - the distro uses perl-Net-DNS-0.59-3.el5 and the latest rpmforge package is perl-Net-DNS-0.66-1.el5.rfx. If you're going to use rpmforge packages, keep them up to date (you'll need to enable the rpmforge-extras repo). Hrm, not sure how that could happen, since I don't have rpmforge disabled. But you do have rpmforge-extras disabled... How could yum not be seeing the newer package? and the newer version is in rpmforge-extras, as denoted by the .rfx tab. That is why yum was not seeing the updated version. cat /etc/yum.repos.d/rpmforge.repo ### Name: RPMforge RPM Repository for RHEL 5 - dag ### URL: http://rpmforge.net/ [rpmforge] name = RHEL $releasever - RPMforge.net - dag baseurl = http://apt.sw.be/redhat/el5/en/$basearch/rpmforge mirrorlist = http://apt.sw.be/redhat/el5/en/mirrors-rpmforge #mirrorlist = file:///etc/yum.repos.d/mirrors-rpmforge enabled = 1 protect = 0 gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmforge-dag gpgcheck = 1 [rpmforge-extras] name = RHEL $releasever - RPMforge.net - extras baseurl = http://apt.sw.be/redhat/el5/en/$basearch/extras mirrorlist = http://apt.sw.be/redhat/el5/en/mirrors-rpmforge-extras #mirrorlist = file:///etc/yum.repos.d/mirrors-rpmforge-extras enabled = 0 protect = 0 gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmforge-dag gpgcheck = 1 [rpmforge-testing] name = RHEL $releasever - RPMforge.net - testing baseurl = http://apt.sw.be/redhat/el5/en/$basearch/testing mirrorlist = http://apt.sw.be/redhat/el5/en/mirrors-rpmforge-testing #mirrorlist = file:///etc/yum.repos.d/mirrors-rpmforge-testing enabled = 0 protect = 0 gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmforge-dag gpgcheck = 1
Re: sa-update / perl error again
> What is the Net::DNS version, are you pure ipv6 and are you > 64-bit? perl-Net-DNS-0.63-1.el5.rf >>> >>> You are in no man's land there - the distro uses >>> perl-Net-DNS-0.59-3.el5 >>> and the latest rpmforge package is perl-Net-DNS-0.66-1.el5.rfx. >>> >>> If you're going to use rpmforge packages, keep them up to date >>> (you'll >>> need to enable the rpmforge-extras repo). >> >> Hrm, not sure how that could happen, since I don't have rpmforge >> disabled. >> > > But you do have rpmforge-extras disabled... > >> How could yum not be seeing the newer package? >> > > and the newer version is in rpmforge-extras, as denoted by the .rfx tab. That's really great how they move the package from one repo to the other. I was trying to have as few third party repos enabled as possible. > That is why yum was not seeing the updated version. Makes sense. However, I'm a little confused as to why I want the perl-Net-DNS package from RepoForge? Is not the CentOS one OK? My spamassassin package (and perl-IO-Socket-INET6) is from CentOS so...?
Re: sa-update / perl error again
> What is the Net::DNS version, are you pure ipv6 and are you > 64-bit? perl-Net-DNS-0.63-1.el5.rf >>> >>> You are in no man's land there - the distro uses >> perl-Net-DNS-0.59-3.el5 >>> and the latest rpmforge package is perl-Net-DNS-0.66-1.el5.rfx. >>> >>> If you're going to use rpmforge packages, keep them up to date >> (you'll >>> need to enable the rpmforge-extras repo). >> >> Hrm, not sure how that could happen, since I don't have rpmforge > disabled. >> >> How could yum not be seeing the newer package? >> >> cat /etc/yum.repos.d/rpmforge.repo > > Well, knowing there was a newer package out there, hopefully no matter > where yum looked for it, I took a chance and removed it: > > rpm -e --nodeps perl-Net-DNS > > Then when I asked yum about it again, it found the new one from the > CentOS repo, so I installed it... it also needed to install perl-Net-IP > which I didn't have. So now I have > > perl-Net-DNS-0.59-3.el5.i386.rpm > > Running sa-update on the command line doesn't produce errors, so > I guess that the cron won't either. Bad news - the error happened again when run from cron. It turns out it's not sa-update specifically doing this, but the restart of spamassassin itself: /etc/init.d/spamassassin condrestart Stopping spamd: [ OK ] Starting spamd: Subroutine Net::DNS::Resolver::Base::AF_INET6 redefined at /usr/lib/perl5/5.8.8/Exporter.pm line 65. at /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/Net/DNS/Resolver/Base.pm line 66 [ OK ] With my spamassassin, perl-Net-DNS and per-IO-Socket-INET6 packages all being from CentOS repo, I'm unsure why this would happen. What else can I look at? Recap on my versions: perl-IO-Socket-INET6-2.51-2.fc6 perl-Net-DNS-0.59-3.el5 spamassassin-3.3.1-2.el5
Re: sa-update / perl error again
Starting spamd: Subroutine Net::DNS::Resolver::Base::AF_INET6 redefined at /usr/lib/perl5/5.8.8/Exporter.pm line 65. at /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/Net/DNS/Resolver/Base.pm line 66 [ OK ] With my spamassassin, perl-Net-DNS and per-IO-Socket-INET6 packages all being from CentOS repo, I'm unsure why this would happen. What else can I look at? Recap on my versions: perl-IO-Socket-INET6-2.51-2.fc6 perl-Net-DNS-0.59-3.el5 spamassassin-3.3.1-2.el5 Does spamassassin -D --lint 2>&1 | grep -i Resolver show the same error? regards, KAM
Re: sa-update / perl error again
On 2012-01-05 21:28, email builder wrote: What is the Net::DNS version, are you pure ipv6 and are you 64-bit? perl-Net-DNS-0.63-1.el5.rf You are in no man's land there - the distro uses perl-Net-DNS-0.59-3.el5 and the latest rpmforge package is perl-Net-DNS-0.66-1.el5.rfx. If you're going to use rpmforge packages, keep them up to date (you'll need to enable the rpmforge-extras repo). Hrm, not sure how that could happen, since I don't have rpmforge disabled. How could yum not be seeing the newer package? cat /etc/yum.repos.d/rpmforge.repo Well, knowing there was a newer package out there, hopefully no matter where yum looked for it, I took a chance and removed it: rpm -e --nodeps perl-Net-DNS Then when I asked yum about it again, it found the new one from the CentOS repo, so I installed it... it also needed to install perl-Net-IP which I didn't have. So now I have perl-Net-DNS-0.59-3.el5.i386.rpm Running sa-update on the command line doesn't produce errors, so I guess that the cron won't either. Bad news - the error happened again when run from cron. It turns out it's not sa-update specifically doing this, but the restart of spamassassin itself: /etc/init.d/spamassassin condrestart Stopping spamd: [ OK ] Starting spamd: Subroutine Net::DNS::Resolver::Base::AF_INET6 redefined at /usr/lib/perl5/5.8.8/Exporter.pm line 65. at /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/Net/DNS/Resolver/Base.pm line 66 [ OK ] With my spamassassin, perl-Net-DNS and per-IO-Socket-INET6 packages all being from CentOS repo, I'm unsure why this would happen. What else can I look at? Recap on my versions: perl-IO-Socket-INET6-2.51-2.fc6 perl-Net-DNS-0.59-3.el5 spamassassin-3.3.1-2.el5 Net-DNS-0.59 is ancient and buggy get the latest for your CentOS version from http://pkgs.repoforge.org/perl-Net-DNS/ run a rpm -hUv so yum won't fiddle around with it during next CentOS update that should hopefully solve your problem.
Re: sa-update / perl error again
>> /usr/lib/perl5/5.8.8/Exporter.pm line 65. at >> /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/Net/DNS/Resolver/Base.pm >> >> line 66 [ OK ] >> >> With my spamassassin, perl-Net-DNS and per-IO-Socket-INET6 >> packages all being from CentOS repo, I'm unsure why this would happen. >> What else can I look at? >> >> Recap on my versions: >> perl-IO-Socket-INET6-2.51-2.fc6 >> perl-Net-DNS-0.59-3.el5 spamassassin-3.3.1-2.el5 > > Does spamassassin -D --lint 2>&1 | grep -i Resolver show the same error? Yes
Re: sa-update / perl error again
>>> What is the Net::DNS version, are you pure ipv6 > and are you >> >>> 64-bit? >> >> perl-Net-DNS-0.63-1.el5.rf >> > > You are in no man's land there - the distro uses perl-Net-DNS-0.59-3.el5 > and the latest rpmforge package is > perl-Net-DNS-0.66-1.el5.rfx. > > If you're going to use rpmforge packages, keep them up > to date (you'll > need to enable the rpmforge-extras repo). Hrm, not sure how that could happen, since I don't have > rpmforge >>> disabled. How could yum not be seeing the newer package? cat /etc/yum.repos.d/rpmforge.repo >>> >>> Well, knowing there was a newer package out there, hopefully no matter >>> where yum looked for it, I took a chance and removed it: >>> >>> rpm -e --nodeps perl-Net-DNS >>> >>> Then when I asked yum about it again, it found the new one from the >>> CentOS repo, so I installed it... it also needed to install perl-Net-IP >>> which I didn't have. So now I have >>> >>> perl-Net-DNS-0.59-3.el5.i386.rpm >>> >>> Running sa-update on the command line doesn't produce errors, so >>> I guess that the cron won't either. >> >> Bad news - the error happened again when run from cron. It turns >> out it's not sa-update specifically doing this, but the restart of >> spamassassin itself: >> >> /etc/init.d/spamassassin condrestart >> >> Stopping spamd: [ OK ] >> Starting spamd: Subroutine Net::DNS::Resolver::Base::AF_INET6 redefined at > /usr/lib/perl5/5.8.8/Exporter.pm line 65. >> at > /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/Net/DNS/Resolver/Base.pm > > line 66 >> [ OK ] >> >> With my spamassassin, perl-Net-DNS and per-IO-Socket-INET6 >> packages all being from CentOS repo, I'm unsure why this would >> happen. What else can I look at? >> >> Recap on my versions: >> >> perl-IO-Socket-INET6-2.51-2.fc6 >> perl-Net-DNS-0.59-3.el5 >> spamassassin-3.3.1-2.el5 > > Net-DNS-0.59 is ancient and buggy > > get the latest for your CentOS version from > > http://pkgs.repoforge.org/perl-Net-DNS/ Wow, really? Then why wouldn't RedHat or CentOS have a fixed updated version in their repo? That seems egregious if what you say is indeed the case. Why wouldn't the rest of the world be seeing the same errors I am since I'm running the most up to date version of that and spamassassin both from the CentOS repo??? (and thus someone fix it...) > run a rpm -hUv so yum won't fiddle around with it during next CentOS update > > that should hopefully solve your problem. I'm going to hold out on this a little longer per my questions above, but I'm definitely thinking this is what my next step will be barring any better suggestions, so thank you.
Re: sa-update / perl error again
>Wow, really? Then why wouldn't RedHat or CentOS have a fixed updated >version in their repo? That seems egregious if what you say is indeed the >case. RedHat (and CentOS, since their whole mission is to match RHEL feature-for-feature and bug-for-bug) believes that their Enterprise Linux customers value consistency over currency. They release updates to patch security holes, but their general attitude is that if Red Hat 5.0 shipped with foo_1.1.3 in 2007, then Red Hat 5.7 should also ship with foo_1.1.3 because their customers may have whole workflows built around the way foo_1.1.3 handles a specific command flag and foo_1.2.7 may have changed that. If necessary, they'll backport security patches from later versions of foo back to the current, leading to RPM names like foo_1.1.3-17.el5_7 -- but they won't add feature changes unless absolutely unavoidable. The downside is that when you run yum update on a CentOS system you won't have the newest foo features; the upside is that when you run yum update on a CentOS system you can be confident that your existing foo installation will not break. If you don't like that philosophy, there are a lot of other Linux (and other UNIX) distros out there. (I personally have an irrational affection for OpenIndiana -- all the crunchy goodness of Solaris without the Ellison tax-- but Ubuntu or Fedora might be better options if you're primarily familiar with Linux.) -- Dave Pooser Cat-Herder-in-Chief, Pooserville.com "...Life is not a journey to the grave with the intention of arriving safely in one pretty and well-preserved piece, but to slide across the finish line broadside, thoroughly used up, worn out, leaking oil, and shouting GERONIMO!!!" -- Bill McKenna
Re: sa-update / perl error again
And if you temporarily move all your config files and run the same command, does the error go away? Regards, KAM >> Does spamassassin -D --lint 2>&1 | grep -i Resolver show the same >error? > >Yes
Re: sa-update / perl error again
>> Wow, really? Then why wouldn't RedHat or CentOS have a fixed updated >> version in their repo? That seems egregious if what you say is indeed the >> case. > > RedHat (and CentOS, since their whole mission is to match RHEL > feature-for-feature and bug-for-bug) believes that their Enterprise Linux > customers value consistency over currency. They release updates to patch > security holes, but their general attitude is that if Red Hat 5.0 shipped > with foo_1.1.3 in 2007, then Red Hat 5.7 should also ship with foo_1.1.3 > because their customers may have whole workflows built around the way > foo_1.1.3 handles a specific command flag and foo_1.2.7 may have changed > that. If necessary, they'll backport security patches from later versions > of foo back to the current, leading to RPM names like foo_1.1.3-17.el5_7 > -- but they won't add feature changes unless absolutely unavoidable. Sure, but the point is that my spamassassin and per-Net-DNS (where the error is happening?) are up to date from the CentOS repo so shouldn't they work without an error when spamassassin restarts?
Re: sa-update / perl error again
On 1/6/2012 3:31 PM, email builder wrote: Sure, but the point is that my spamassassin and per-Net-DNS (where the error is happening?) are up to date from the CentOS repo so shouldn't they work without an error when spamassassin restarts? It isn't the job of the SA project to worry about specific distros and repositories. This is a question for a CentOS/RedHat forum Right now, this is most likely: A bug in a Perl module long since fixed or a local configuration error. I've sent you information asking you to test without any cf files to see if the error goes away. And you'll need to work with people familiar with your Distro to update the likely culprits. Net::DNS is where I would focus. regards, KAM
Re: sa-update / perl error again
On 2012-01-06 21:31, email builder wrote: Wow, really? Then why wouldn't RedHat or CentOS have a fixed updated version in their repo? That seems egregious if what you say is indeed the case. RedHat (and CentOS, since their whole mission is to match RHEL feature-for-feature and bug-for-bug) believes that their Enterprise Linux customers value consistency over currency. They release updates to patch security holes, but their general attitude is that if Red Hat 5.0 shipped with foo_1.1.3 in 2007, then Red Hat 5.7 should also ship with foo_1.1.3 because their customers may have whole workflows built around the way foo_1.1.3 handles a specific command flag and foo_1.2.7 may have changed that. If necessary, they'll backport security patches from later versions of foo back to the current, leading to RPM names like foo_1.1.3-17.el5_7 -- but they won't add feature changes unless absolutely unavoidable. Sure, but the point is that my spamassassin and per-Net-DNS (where the error is happening?) are up to date from the CentOS repo so shouldn't they work without an error when spamassassin restarts? insisting and asking the SA list why Centos does something is not going to get you anywhere. You were told why - and if not send your complaints to RedHAt which is responsible for the sources. Centos only repackages the upstream sources. run the update I suggested and tell us what happened.
Re: sa-update / perl error again
>>> Does spamassassin -D --lint 2>&1 | grep -i Resolver show the >>> same error? >> >> Yes > > And if you temporarily move all your config files and run the same command, > does > the error go away? Yikes, I'm reluctant to do this on a production machine. I have only made config changes in local.cf (pretty nominal) and in database_config.cf where I have DBs for user scores, auto whitelist and bayes. Why would my (I'd guess fairly innocuous) config settings trigger a DNS resolver error where it looks like a function has been redefined?
Re: sa-update / perl error again
>> Sure, but the point is that my spamassassin and per-Net-DNS (where the >> error is happening?) are up to date from the CentOS repo so shouldn't >> they work without an error when spamassassin restarts? > > It isn't the job of the SA project to worry about specific distros and > repositories. This is a question for a CentOS/RedHat forum Fair enough > Right now, this is most likely: A bug in a Perl module long since fixed or a > local configuration error. I've sent you information asking you to test > without any cf files to see if the error goes away. I don't see how a configuration problem could cause this, especially when I've been using this configuration on more than one machine without problems for years and it's all basic - change the default required score and rewrite header settings, set up database access for bayes and user scores. So while I *DO* appreciate your suggestion, since I am fairly confident to say I doubt that my config is the problem in a DNS resolver/IPv6 function redefinition, I'm not too interested in proving that point by making those changes on a production machine. Again, thanks anyway. > And you'll need to work > with people familiar with your Distro to update the likely culprits. > Net::DNS > is where I would focus. I am going to look for where to file a bug report.
Re: sa-update / perl error again
Wow, really? Then why wouldn't RedHat or CentOS have a fixed updated version in their repo? That seems egregious if what you say is indeed the case. >>> >>> RedHat (and CentOS, since their whole mission is to match RHEL >>> feature-for-feature and bug-for-bug) believes that their Enterprise >>> Linux >>> customers value consistency over currency. They release updates to >>> patch >>> security holes, but their general attitude is that if Red Hat 5.0 >>> shipped >>> with foo_1.1.3 in 2007, then Red Hat 5.7 should also ship with >>> foo_1.1.3 >>> because their customers may have whole workflows built around the way >>> foo_1.1.3 handles a specific command flag and foo_1.2.7 may have >>> changed >>> that. If necessary, they'll backport security patches from later >>> versions >>> of foo back to the current, leading to RPM names like >>> foo_1.1.3-17.el5_7 >>> -- but they won't add feature changes unless absolutely >>> unavoidable. >> >> Sure, but the point is that my spamassassin and per-Net-DNS (where the >> error is happening?) are up to date from the CentOS repo so >> shouldn't >> they work without an error when spamassassin restarts? > > insisting and asking the SA list why Centos does something is not going > to get you anywhere. You were told why - and if not send your complaints > to RedHAt which is responsible for the sources. Centos only repackages > the upstream sources. > > run the update I suggested and tell us what happened. Please don't misunderstand - I do very much appreciate your help. I'm hesitant to do as suggested and obtain a newer perl-Net-DNS from an external repo because of what seems to be a general opinion that the more you mix external packages the more you risk things like this continuing to happen. So I thought keep as many packages as native CentOS as I can. I'm going to try to figure out where to file a bug I guess, but I have a fear I'll get rebuffed without any help at all.
Re: sa-update / perl error again
On Sat, 7 Jan 2012 11:00:31 -0800 (PST), email builder wrote: many packages as native CentOS as I can. I'm going to try to figure out where to file a bug I guess, but I have a fear I'll get rebuffed without any help at all. build perl rpms from cpan is imho safe and ok, but using cpan direct in shell is asking for problems there is a dist2rpm somewhere that builds rpms, in gentoo i just use g-cpan if i miss something not in core gentoo portage for me rpm based distros is not for me, redhat wanted me to drop redhat 8 with downloading redhat 9 iso, yark, one year later it was dropped support, and all i could do was drop redhat and search for non rpm based distros, first i found was freebsd 4.9 installed from 2 1440kb floppy disks, do any others os do this today ? why is there not just a simple minimal install that setup first time boot that works as much to continue on when its booted without needing gigabytes of storage ? where is clouds now ?, it could be nice with pxe booting :-) (read only filesystem) btw this msg is writed here from my asus eee pc with just 512M mem runing windows xp on the buildt in harddisk at 2048M in size, when microsoft screw that up i just use it for freenas 0.7 and add more usb disks to it sorry for being offtopic
Re: sa-update / perl error again
On 1/7/12 1:56 PM, email builder wrote: while I*DO* appreciate your suggestion, since I am fairly confident to say I doubt that my config is the problem in a DNS resolver/IPv6 function redefinition, I'm not too interested in proving that point by making those changes on a production machine. Again, thanks anyway. I am the ports maintainer for the FreeBSD version of SpamAssassin. used 'it' for YEARS in production, (commercial product,) several platforms, i386, amd64, FreeBSD versions 6.4-7.4. ONE DAY, ONE BRAND NEW CLIENT was having real problems with their mailq. email was backing up. Two days to figure it out, I deleted the INET6 module (on freebsd, its a lot easier, I suppose than on your linux thing). Now, all the email flowed perfectly. SA was trying to do ipv6 lookups, the kernel did NOT have ipv6 compiled in.. NONE OF OUR PRODUCTION SYSTEMS DO, and there is no logical explanation for it. SA does NOT need INET6, unless you have two things: #0, INET6 compiled into your kernel #1, INET6 dns server as the first server in /etc/resolv.conf #2, INET6 firewall, routing, mx records, etc. I updated FreeBSD port so that it did not even try to install INET6 pm unless the system was compiled with INET6 in the kernel. ymmv, Did I mention that we were not able to reproduce this in the lab? and up till then, no other client had a problem? -- Michael Scheidell, CTO o: 561-999-5000 d: 561-948-2259 >*| *SECNAP Network Security Corporation * Best Mobile Solutions Product of 2011 * Best Intrusion Prevention Product * Hot Company Finalist 2011 * Best Email Security Product * Certified SNORT Integrator __ This email has been scanned and certified safe by SpammerTrap(r). For Information please see http://www.spammertrap.com/ __
Re: sa-update / perl error again
>> while I*DO* appreciate your suggestion, since I am fairly confident to say >> I doubt that my config is the problem in a DNS resolver/IPv6 function >> redefinition, I'm not too interested in proving that point by making >> those >> changes on a production machine. Again, thanks anyway. > > I am the ports maintainer for the FreeBSD version of SpamAssassin. > > used 'it' for YEARS in production, (commercial product,) several > platforms, i386, amd64, FreeBSD versions 6.4-7.4. > > ONE DAY, ONE BRAND NEW CLIENT was having real problems with their mailq. > email > was backing up. > Two days to figure it out, I deleted the INET6 module (on freebsd, its a lot > easier, I suppose than on your linux thing). > > Now, all the email flowed perfectly. SA was trying to do ipv6 lookups, the > kernel did NOT have ipv6 compiled in.. NONE OF OUR PRODUCTION SYSTEMS DO, and > there is no logical explanation for it. > > SA does NOT need INET6, unless you have two things: > #0, INET6 compiled into your kernel > #1, INET6 dns server as the first server in /etc/resolv.conf > #2, INET6 firewall, routing, mx records, etc. Strong argument for removing it I guess, I think with: rpm -e --nodeps perl-IO-Socket-INET6 But as others noted, yum supposedly will complain from then on about the missing package. Thanks for the input!
Re: sa-update / perl error again
>> I am the ports maintainer for the FreeBSD version of SpamAssassin.
>>
>> used 'it' for YEARS in production, (commercial product,) several
>> platforms, i386, amd64, FreeBSD versions 6.4-7.4.
>>
>> ONE DAY, ONE BRAND NEW CLIENT was having real problems with their mailq.
> email
>> was backing up.
>> Two days to figure it out, I deleted the INET6 module (on freebsd, its a
> lot
>> easier, I suppose than on your linux thing).
>>
>> Now, all the email flowed perfectly. SA was trying to do ipv6 lookups, the
>
>> kernel did NOT have ipv6 compiled in.. NONE OF OUR PRODUCTION SYSTEMS DO,
> and
>> there is no logical explanation for it.
>>
>> SA does NOT need INET6, unless you have two things:
>> #0, INET6 compiled into your kernel
>> #1, INET6 dns server as the first server in /etc/resolv.conf
>> #2, INET6 firewall, routing, mx records, etc.
>
> Strong argument for removing it I guess, I think with:
>
> rpm -e --nodeps perl-IO-Socket-INET6
By the way, is there a way to grep for the errant code? My
feeble attempt didn't turn up much:
cd /usr/lib/perl5
grep -rin 'af_inet6' *
Only gave 40 lines, which I could post if it would help.
This only gave one result:
grep -rin 'sub af_inet6' *
5.8.8/i386-linux-thread-multi/bits/socket.ph:66: eval 'sub AF_INET6 () {
&PF_INET6;}' unless defined(&AF_INET6);
Is it pointless to try to diagnose in this manner?
Re: sa-update / perl error again
On 1/8/12 9:52 PM, email builder wrote: rpm -e --nodeps perl-IO-Socket-INET6 By the way, is there a way to grep for the errant code? My feeble attempt didn't turn up much: as in one of my previous emails: 'locate IO-Socket-INET6' -- Michael Scheidell, CTO o: 561-999-5000 d: 561-948-2259 >*| *SECNAP Network Security Corporation * Best Mobile Solutions Product of 2011 * Best Intrusion Prevention Product * Hot Company Finalist 2011 * Best Email Security Product * Certified SNORT Integrator __ This email has been scanned and certified safe by SpammerTrap(r). For Information please see http://www.spammertrap.com/ __
Re: sa-update / perl error again
On 1/9/12 6:25 AM, Michael Scheidell wrote:
On 1/8/12 9:52 PM, email builder wrote:
rpm -e --nodeps perl-IO-Socket-INET6
By the way, is there a way to grep for the errant code? My
feeble attempt didn't turn up much:
as in one of my previous emails:
'locate IO-Socket-INET6'
locate INET6
and/or:
(here was previous email)
or, you could just delete (manually) IO-Socket-INET6 (make a backup first!)
on freebsd (with perl 5.10.1):
/usr/local/lib/perl5/5.10.1/man/man3/IO::Socket::INET6.3.gz
/usr/local/lib/perl5/site_perl/5.10.1/IO/Socket/INET6.pm
/usr/local/lib/perl5/site_perl/5.10.1/mach/auto/IO/Socket/INET6
/usr/local/lib/perl5/site_perl/5.10.1/mach/auto/IO/Socket/INET6/.packlist
on fedora, try:
find /usr/lib/ -name 'INET6*'
(back them up) you should see them as above. but, yum won't know they
are gone.
might be in /usr/lib/perl5/{version}
and /usr/lib/perl5{version}|vendor}
ask on linux users group how to get yum to rm a dependency without the
package.
on freebsd, it would be something like 'pkg_delete -f
p5-IO-SOCKET-INET6' (the -f to force it to be removed)
and, pkgdb -F (to FIX the package database and remove the dependency link)
--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
>*| *SECNAP Network Security Corporation
* Best Mobile Solutions Product of 2011
* Best Intrusion Prevention Product
* Hot Company Finalist 2011
* Best Email Security Product
* Certified SNORT Integrator
__
This email has been scanned and certified safe by SpammerTrap(r).
For Information please see http://www.spammertrap.com/
__
Re: sa-update / perl error again
rpm -e --nodeps perl-IO-Socket-INET6
>>> By the way, is there a way to grep for the errant code? My
>>> feeble attempt didn't turn up much:
>>>
>> as in one of my previous emails:
>>
>> 'locate IO-Socket-INET6'
Sorry I missed that!
This gives only docs:
/usr/share/doc/perl-IO-Socket-INET6-2.51
/usr/share/doc/perl-IO-Socket-INET6-2.51/README
> locate INET6
/usr/lib/perl5/vendor_perl/5.8.8/IO/Socket/INET6.pm
/usr/share/doc/perl-IO-Socket-INET6-2.51
/usr/share/doc/perl-IO-Socket-INET6-2.51/README
/usr/share/man/man3/IO::Socket::INET6.3pm.gz
Using the find command from below (for fedora since
this is CentOS) I get
/usr/lib/perl5/vendor_perl/5.8.8/IO/Socket/INET6.pm
This locates that package, but correct me if I'm wrong, I
don't think it finds the OTHER package that is creating
the duplicate subroutine definition for AF_INET6.
> and/or:
>
> (here was previous email)
>
> or, you could just delete (manually) IO-Socket-INET6 (make a backup first!)
> on freebsd (with perl 5.10.1):
>
> /usr/local/lib/perl5/5.10.1/man/man3/IO::Socket::INET6.3.gz
> /usr/local/lib/perl5/site_perl/5.10.1/IO/Socket/INET6.pm
> /usr/local/lib/perl5/site_perl/5.10.1/mach/auto/IO/Socket/INET6
> /usr/local/lib/perl5/site_perl/5.10.1/mach/auto/IO/Socket/INET6/.packlist
>
> on fedora, try:
>
> find /usr/lib/ -name 'INET6*'
> (back them up) you should see them as above. but, yum won't know they are
> gone.
> might be in /usr/lib/perl5/{version}
> and /usr/lib/perl5{version}|vendor}
>
> ask on linux users group how to get yum to rm a dependency without the
> package.
>
> on freebsd, it would be something like 'pkg_delete -f
> p5-IO-SOCKET-INET6' (the -f to force it to be removed)
> and, pkgdb -F (to FIX the package database and remove the dependency link)
Re: sa-update / perl error again
>>> used 'it' for YEARS in production, (commercial product,)
>>> several
>>> platforms, i386, amd64, FreeBSD versions 6.4-7.4.
>>>
>>> ONE DAY, ONE BRAND NEW CLIENT was having real problems with their
>>> mailq. email was backing up.
>>> Two days to figure it out, I deleted the INET6 module (on freebsd, its a
>>> lot easier, I suppose than on your linux thing).
>>>
>>> Now, all the email flowed perfectly. SA was trying to do ipv6
>>> lookups, the
>>>
>>> kernel did NOT have ipv6 compiled in.. NONE OF OUR PRODUCTION SYSTEMS
>>> DO, and there is no logical explanation for it.
>>>
>>> SA does NOT need INET6, unless you have two things:
>>> #0, INET6 compiled into your kernel
>>> #1, INET6 dns server as the first server in /etc/resolv.conf
>>> #2, INET6 firewall, routing, mx records, etc.
>>
>> Strong argument for removing it I guess, I think with:
>>
>> rpm -e --nodeps perl-IO-Socket-INET6
>
> By the way, is there a way to grep for the errant code? My
> feeble attempt didn't turn up much:
>
> cd /usr/lib/perl5
> grep -rin 'af_inet6' *
>
> Only gave 40 lines, which I could post if it would help.
> This only gave one result:
>
> grep -rin 'sub af_inet6' *
>
> 5.8.8/i386-linux-thread-multi/bits/socket.ph:66: eval 'sub AF_INET6 () {
> &PF_INET6;}' unless defined(&AF_INET6);
>
> Is it pointless to try to diagnose in this manner?
After some help on the CentOS list, I may have found the problem:
> perl-NetAddr-IP-4.044-1.el5.rf <=== I think that is the problem package
>
> I don't know if that version is required by the repoforge packages ... but
> base contains perl-NetAddr-IP-4.027-5.el5_6
>
> I would see if I could replace perl-NetAddr-IP-4.044-1.el5.rf from repoforge
> with perl-NetAddr-IP-4.027-5.el5_6 from base.
rpm -e --nodeps perl-NetAddr-IP
vi /etc/yum.repos.d/rpmforge.repo
-- change all enabled = 1 to enabled = 0 temporarily (seems like
yum priorities is going to be a good idea) --
yum install perl-NetAddr-IP
/etc/init.d/spamassassin condrestart
Stopping spamd: [ OK ]
Starting spamd: [ OK ]
That seems to have done it. Does that make sense? Should
I report this to the RepoForge people?
Re: sa-update / perl error again
> After some help on the CentOS list, I may have found the problem: > >> perl-NetAddr-IP-4.044-1.el5.rf <=== I think that is the problem package >> >> I don't know if that version is required by the repoforge packages ... >> but base contains perl-NetAddr-IP-4.027-5.el5_6 >> >> I would see if I could replace perl-NetAddr-IP-4.044-1.el5.rf from >> repoforge with perl-NetAddr-IP-4.027-5.el5_6 from base. > > rpm -e --nodeps perl-NetAddr-IP > > vi /etc/yum.repos.d/rpmforge.repo > -- change all enabled = 1 to enabled = 0 temporarily (seems like > yum priorities is going to be a good idea) -- > > yum install perl-NetAddr-IP > > /etc/init.d/spamassassin condrestart > Stopping spamd: [ OK ] > Starting spamd: [ OK ] > > That seems to have done it. Does that make sense? Should > I report this to the RepoForge people? FYI: I did in fact report it to them, and it was eventually moved to the RepoForge extras repository, which finally fixes everything. Thanks again for the help
Re: Perl error after upgrade to 3.2.3
Hi; I've seen this as well. I did a cpan upgrade and upgraded all perl mods on a BSD, but not SA which was at 3.2.3. I think that may be due to an issue with Sys:Syslog v0.20 SA seems to be working fine, as you say. [96054] error: Can't locate Sys/Syslog/Win32.pm in @INC (@INC contains: /usr/local/lib/perl5/site_perl/5.8.8 /usr/local/lib/perl5/5.8.8/BSDPAN /usr/local/lib/perl5/site_perl/5.8.8/mach /usr/local/lib/perl5/site_perl /usr/local/lib/perl5/5.8.8/mach /usr/local/lib/perl5/5.8.8) at (eval 14) line 2. [96054] error: BEGIN failed--compilation aborted at (eval 14) line 2. rgds n Jonathan Armitage wrote: Apologies if I am asking in the wrong place, since I can see that there are several possible reasons. We have just upgraded to SpamAssassin 3.2.3 on an elderly 386 box running Red Hat 9. At the same time I used CPAN to upgrade any out-of-date perl modules. Now, when SA starts, we get the following error: Starting SpamAssassin daemon... [23172] error: Can't locate Sys/Syslog/Win32.pm in @INC (@INC contains: /usr/local/lib/perl5/site_perl/5.8.8/i686-linux /usr/local/lib/perl5/site_perl/5.8.8 /usr/local/lib/perl5/5.8.8/i686-linux /usr/local/lib/perl5/5.8.8 /usr/local/lib/perl5/site_perl) at (eval 11) line 2. [23172] error: BEGIN failed--compilation aborted at (eval 11) line 2. done. The error comes up twice, but SA does in fact start, and appears to be functioning normally. Does anyone know why it suddenly wants to load a Win32 module? Jon Jon Armitage System Administrator, 365 Media Group
Re: Perl error after upgrade to 3.2.3
It is definately Sys:Syslog causing the problem. If you look in the actual spamd file, it gives some indication of this. I found that if I specified my log file options in the spamassassin options files that the problem is resolved. Add something like -s /var/log/spam.d to the existing options and the error clears. bw - Rank1st Neil-27 wrote: > > Hi; >I've seen this as well. I did a cpan upgrade and upgraded all perl > mods on a BSD, but not SA which was at 3.2.3. I think that may be due to > an issue with Sys:Syslog v0.20 > > SA seems to be working fine, as you say. > > [96054] error: Can't locate Sys/Syslog/Win32.pm in @INC (@INC contains: > /usr/local/lib/perl5/site_perl/5.8.8 /usr/local/lib/perl5/5.8.8/BSDPAN > /usr/local/lib/perl5/site_perl/5.8.8/mach /usr/local/lib/perl5/site_perl > /usr/local/lib/perl5/5.8.8/mach /usr/local/lib/perl5/5.8.8) at (eval 14) > line 2. > [96054] error: BEGIN failed--compilation aborted at (eval 14) line 2. > > > rgds > n > > > Jonathan Armitage wrote: >> Apologies if I am asking in the wrong place, since I can see that >> there are several possible reasons. >> >> We have just upgraded to SpamAssassin 3.2.3 on an elderly 386 box >> running Red Hat 9. At the same time I used CPAN to upgrade any >> out-of-date perl modules. >> >> Now, when SA starts, we get the following error: >> >> Starting SpamAssassin daemon... >> [23172] error: Can't locate Sys/Syslog/Win32.pm in @INC (@INC >> contains: /usr/local/lib/perl5/site_perl/5.8.8/i686-linux >> /usr/local/lib/perl5/site_perl/5.8.8 >> /usr/local/lib/perl5/5.8.8/i686-linux /usr/local/lib/perl5/5.8.8 >> /usr/local/lib/perl5/site_perl) at (eval 11) line 2. >> [23172] error: BEGIN failed--compilation aborted at (eval 11) line 2. >> >> done. >> >> The error comes up twice, but SA does in fact start, and appears to be >> functioning normally. Does anyone know why it suddenly wants to load a >> Win32 module? >> >> Jon >> >> Jon Armitage >> System Administrator, 365 Media Group >> > > > -- View this message in context: http://www.nabble.com/Perl-error-after-upgrade-to-3.2.3-tf4428549.html#a12942940 Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
perl error on TVD_STOCK1 after 3.2.5 update
Is anyone else currently seeing this since 3.2.5 upgrade?
We updated when it came out and have only seen the error a few times
since...
Centos 4.6 and perl 5.8.8 and SA 3.2.5 with sought rules and compiled
Jun 25 09:22:57 mxi spamd[18530]: rules: failed to run TVD_STOCK1 test,
skipping:
Jun 25 09:22:57 mxi spamd[18530]: (Malformed UTF-8 character (fatal) at
/usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Plugin/BodyEval.pm line
243.
Jun 25 09:22:57 mxi spamd[18530]: )
I checked in the rules area and it shows up under 72_active.cf
##{ TVD_STOCK1
ifplugin Mail::SpamAssassin::Plugin::BodyEval
body TVD_STOCK1eval:check_stock_info('2')
endif
##} TVD_STOCK1
Im not sure where to go from here...
What should I be looking for in a fix other than to comment the rule out in
some way or some other option(s) ???
Thanks
- rh
RE: perl error on TVD_STOCK1 after 3.2.5 update
Please forgive me for top post and replying to my own, yet I forgot to add
the code from line 243 in the BodyEval.pm file
foreach ( $rnd =~ /^\s*([^:\s][^:\n]{2,29})\s*:\s*\S/mg ) {
:-)
- rh
>
> Is anyone else currently seeing this since 3.2.5 upgrade?
>
> We updated when it came out and have only seen the error a few times
> since...
>
> Centos 4.6 and perl 5.8.8 and SA 3.2.5 with sought rules and compiled
>
>
> Jun 25 09:22:57 mxi spamd[18530]: rules: failed to run TVD_STOCK1 test,
> skipping:
> Jun 25 09:22:57 mxi spamd[18530]: (Malformed UTF-8 character (fatal) at
> /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Plugin/BodyEval.pm line
> 243.
> Jun 25 09:22:57 mxi spamd[18530]: )
>
> I checked in the rules area and it shows up under 72_active.cf
>
> ##{ TVD_STOCK1
>
> ifplugin Mail::SpamAssassin::Plugin::BodyEval
> body TVD_STOCK1eval:check_stock_info('2')
> endif
> ##} TVD_STOCK1
>
> Im not sure where to go from here...
>
> What should I be looking for in a fix other than to comment the rule out
> in
> some way or some other option(s) ???
>
> Thanks
>
> - rh
