postfix warns about differing chroot files after package upgrades

Bug #1957884 reported by Martin Richtarsky
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
postfix (Ubuntu)
Undecided
Unassigned

Bug Description

postfix will warn when the chroot binaries (or certificate/settings files) differ, which happens when the system version was updated.

Could an updtae hook be added, so the chroot is also updated alongside any system udates?

Jan 14 09:00:02 mail postfix/postfix-script[1703958]: warning: /var/spool/postfix/lib/x86_64-linux-gnu/libnss_systemd.so.2 and /lib/x86_64-linux-gnu/libnss_systemd.so.2 differ

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: postfix 3.5.6-1ubuntu0.2
ProcVersionSignature: Ubuntu 5.11.0-44.48-generic 5.11.22
Uname: Linux 5.11.0-44-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu65.4
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Fri Jan 14 09:22:08 2022
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: postfix
UpgradeStatus: Upgraded to hirsute on 2021-07-17 (180 days ago)

Revision history for this message
Martin Richtarsky (mrichtarsky) wrote :
Revision history for this message
Scott Kitterman (kitterman) wrote :

Does restarting (not reloading) or stopping/starting postfix get things back in sync?

Revision history for this message
Martin Richtarsky (mrichtarsky) wrote :

@Scott: Yes it does (I did both and don't get the error anymore)

Could that be done automatically when the chroot file dependencies change?

Revision history for this message
Scott Kitterman (kitterman) wrote :

In theory, yes. In practice, it would be very complicated and it's not something that's likely to get done in the near-term.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers