Bug 1214182

Summary: Problem with starting amavis after update of Tumbleweed to 20230809
Product: [openSUSE] openSUSE Tumbleweed Reporter: Freek de Kruijf <freek>
Component: OtherAssignee: E-mail List <screening-team-bugs>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Major    
Priority: P5 - None CC: suse+build
Version: Current   
Target Milestone: ---   
Hardware: Other   
OS: openSUSE Tumbleweed   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Freek de Kruijf 2023-08-11 08:56:05 UTC 
After the latest update of Tumbleweed starting service amavis fails with the message:

aug 11 10:24:02 eiktum systemd[1]: Starting Amavisd-new Virus Scanner interface...
aug 11 10:24:02 eiktum amavis[7902]: Starting virus-scanner (amavisd-new):
aug 11 10:24:02 eiktum amavis[7903]: Can't locate Amavis/Boot.pm in @INC (you may need to install the Amavis::Boot module) (@INC ent
ries checked: /usr/lib/perl5/site_perl/5.38.0/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.38.0 /usr/lib/perl5/vendor_perl/5
.38.0/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.38.0 /usr/lib/perl5/5.38.0/x86_64-linux-thread-multi /usr/lib/perl5/5.3
8.0 /usr/lib/perl5/site_perl) at /usr/sbin/amavisd line 99.
aug 11 10:24:02 eiktum systemd[1]: amavis.service: Main process exited, code=exited, status=1/FAILURE
aug 11 10:24:02 eiktum systemd[1]: amavis.service: Failed with result 'exit-code'.
aug 11 10:24:02 eiktum systemd[1]: Failed to start Amavisd-new Virus Scanner interface.

I found the module Amavis/Boot.pm in /usr/lib/perl5/site_perl/5.36.0/ but a symbolic link in /usr/lib/perl5/site_perl/5.38.0 to Amavis in /usr/lib/perl5/site_perl/5.36.0/ did not solve the problem.
Comment 1 Arjen de Korte 2023-08-12 12:03:35 UTC 
I requested a rebuild for amavisd-new yesterday and a new build will be available in snapshot 0812 which will fix this for now.

A permanent solution to prevent this from recurring in the future is in https://build.opensuse.org/request/show/1103583 and is already in Staging.
Comment 2 Arjen de Korte 2023-08-14 19:26:56 UTC 
Fixed in snapshot 0812