Hi there,
I went back to the snapshot before trying to install postfix
from source, did an
apt-get install --reinstall postfix postfiy-mysql
But still the master executable has an old version:
root@jerakeen:~# objdump -T /usr/libexec/postfix/master | grep
compat_level
0000000000000000 DO *UND* 0000000000000000 var_compat_level
root@jerakeen:~# strings /usr/libexec/postfix/master | grep mail_version
mail_version=3.4.13
That's the mess I'm dealing with right now. Well, the "new" appropiate
executable has to be somewhere, I'll look for it. Maybe there's been a
symbolic link or directory problem during (re)install.
...
...
I've found different versions (old one and new one). I guess that's why
the
installation went totally wrong:
root@jerakeen:~# strings /usr/libexec/postfix/master | grep mail_version
mail_version=3.4.13
root@jerakeen:~# strings /usr/lib/postfix/sbin/master | grep
mail_version
mail_version=3.6.4
root@jerakeen:~# ls -l /usr/libexec/postfix/master
/usr/lib/postfix/sbin/master
lrwxrwxrwx 1 root root 32 Dez 14 2021 /usr/libexec/postfix/master ->
/usr/libexec/postfix/sbin/master
-rwxr-xr-x 1 root root 47496 Mär 21 2022 /usr/lib/postfix/sbin/master
As I assumed: There's a symbolic link involved. I'll try to get rid off
that mess
...
...
All files in /usr/libexec/postfix pointed to /usr/libexec/postfix/sbin
-> old versions.
The current versions (all) are in /usr/lib/postfix/sbin
Now all links are pointing to the /usr/lib/postfix/sbin directory ->
Postfix starts!
Right now I get lots of warnings that the symbolic links leave
the directory structure.
What ist the original directory structure which is expected by postfix?
I'd like to leave it just like postfix wants it so there's no warning
left
(and possibly there will be no problem when doing the next update :))
Best Regards, thanks for all your helpful answers,
Martin
Am 03.10.2022 14:44 schrieb Martin Hahn:
> P.S.: I went back to the snapshot before trying to install postfix
> from source, did an
> apt-get install --reinstall postfix postfiy-mysql
>
> But still the master executable has an old version:
> root@jerakeen:~# objdump -T /usr/libexec/postfix/master | grep compat_level
> 0000000000000000 DO *UND* 0000000000000000 var_compat_level
>
> root@jerakeen:~# strings /usr/libexec/postfix/master | grep version | grep
> "3."
> mail_version=3.4.13
>
> That's the mess I'm dealing with right now. Well, the "new" appropiate
> executable has to be somewhere, I'll look for it. Maybe there's been a
> symbolic link or directory problem during (re)install.
>
> Cheers,
> Martin
>
> Am 03.10.2022 13:36 schrieb Martin Hahn: Hi Jaroslaw, hi Wietse, hi Shawn,
>
> that's right, I've had a well functioning postfix installation which
> came wich ubuntu 20.04 LTS (at latest patch level). Then I did
> the do-release-upgrade and some packets did not work after-
> wards (e.g. Apache2, but that was based on problems with PHP
> which I could resolve on my own).
>
> Obbiously (Viktor wrote it) the postfix installation during release
> upgrade mixed up at least some executables which prevent
> postfix from starting up (master executable carried a symbol
> called var_compat_level which is not to be supposed to be part
> of the 3.6.4 master executable => no start possible.
> Some things during do-release-upgrade went absolutely wrong,
> a mix of executable versions was left to me.
>
> Then - because I could not get postfix starting up - I tried to
> build 3.7.2 from source file (did not succeed due to SASL
> problems) and later on I tried 3.6.6 from source and that does
> almost work except for the fact SASL "forgot" how to ask my
> mysql database for credentials, the log says:
> postfix/smtpd[14601]: warning: SASL authentication problem: unable to open
> Berkeley db /etc/sasldb2: Permission denied
>
> -> smtpd should not ask any Berkeley database for credentials,
> maybe the smtpd.conf was not found.
>
> -----------------------------------------------------------
>
> So my next try will be the advice of Shawn: Re-installing the postfix
> packages using apt:
>
> Installed:
> root@jerakeen:~# dpkg -l | grep -E "s+postfix" | awk '{print $2}'
> postfix
> postfix-mysql
>
> Therefore:
> apt install --reinstall postfix postfix-mysql
>
> But: That was not my best idea, now the executables are really
> mixed up as I can see lots of warnings during startup of postfix.
>
> Luckily I've made a snapshot I can return to (right before I start
> the installation from source), then I try to repeat the apt reinstall
> mentioned above.
>
> Regards,
> Martin
>
> ---
>
> Am 02.10.2022 23:43 schrieb Jaroslaw Rafa:
>
> Dnia 2.10.2022 o godz. 17:35:23 Wietse Venema pisze:
> I recommend that you use a pre-built package for your OS distribution. That
> will solve the startup problem too.
>
> I guess he did use those packages, because he wrote that he did a release
> upgrade from Ubuntu 20.04 to 22.04 and then Postfix stopped working. The
> release upgrade must have upgraded the Postfix packages too.
>
> However, from my experience, relase upgrade is always a risky thing and
> something can always go wrong. I never recommend to people to do a release
> upgrade. What I recommend is freshly install a new OS release and migrate
> all configs (with manual adjustments if necessary) from the previous OS.
