Re: Upgrade spamassassin from 4.0.1 to 4.0.2 breaks amavis
Xavier Humbert <[email protected]>
| Newsgroups | gmane.mail.spam.spamassassin.general |
|---|---|
| Message-ID | <[email protected]> |
Le 17/10/2025 15:02, Matija Nalis a écrit : > On Fri, Oct 17, 2025 at 11:03:44AM +0200, Xavier Humbert wrote: >> I just upgraded from 4.0.1 to 4.0.2 on FreebSD 14.3-STABLE, then amavis >> won't start anymore : >> >> root@numenor ~]# amavisd >> fetch_modules: error loading optional module Razor2/Client/Agent.pm: >> Can't locate Getopt/Long.pm: lib/Getopt/Long.pm: Permission denied at >> /usr/local/lib/perl5/site_perl/mach/5.40/Razor2/Client/Agent.pm line 15. >> BEGIN failed--compilation aborted at >> /usr/local/lib/perl5/site_perl/mach/5.40/Razor2/Client/Agent.pm line 15. >> Compilation failed in require at >> /usr/local/lib/perl5/site_perl/Amavis/Boot.pm line 77. >> fetch_modules: error loading optional module Mail/DKIM.pm: >> Can't locate Mail/DKIM.pm: lib/Mail/DKIM.pm: Permission denied at >> /usr/local/lib/perl5/site_perl/Amavis/Boot.pm line 77. > Those sound like permission problem to me. > > I'm not FreeBSD user, but did you upgrade Spamassassin via ports > system or manually (And what commands/instructions did you follow?) > > Did you upgrade any other things too in the period between when it > worked and when it stopped working? > > Perhaps it might've been caused by too restrictive umask before upgrading? > > I would check permissions (i.e. "ls -ld" on files and directories > involved), not only for Razor2/Client/Agent.pm et al. but also things > it complains about (e.g. where is lib/Getopt/Long.pm and what are its > permissions, and permission of all directories leading up to it) > > Fix might likely involve "chmod a+r" on those .pm files (and perhaps > "chmod a+rx" on their parent directories, depending on what broke > exactly. I would not go doing that blindly before assessing the > problem and making extra backups... and ideally finding a root cause) > Hi, Matija, I did "portupgrade spamassassin", that's all. It worked before, and does not work anymore. I don't think it's really a permission issue, since I try to run amavis as root. Regards, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr