>>>>> 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
