Bug 32751 - Postfix not starting
Summary: Postfix not starting
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 9
Hardware: x86_64 Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-01-20 17:52 CET by Muhammad Tailounie
Modified: 2024-01-22 08:51 CET (History)
1 user (show)

See Also:
Source RPM: postfix-3.8.4-1.mga9.src.rpm
CVE:
Status comment:


Attachments

Description Muhammad Tailounie 2024-01-20 17:52:53 CET
Description of problem: 

Postfix in M9 has never worked. Upon initial launching of M9 postfix.service started even though postfix never worked. This has been tested with mariadb, postgresql and sqlite backends.

postfix-3.8.4-1 from updates-testing is not even launching on M9. Not even with the minimal configuration.

Following is the unuseful logs of postfix. If there is a better way to get better logs, please advise:

# journalctl -fu postfix
Sep 09 05:18:31 pbx postfix[180688]: Job for postfix.service canceled.
Sep 09 05:18:31 pbx systemd[1]: postfix.service: Deactivated successfully.
Sep 09 05:18:31 pbx systemd[1]: postfix.service: Unit process 180643 (postfix-chroot.) remains running after unit stopped.
Sep 09 05:18:31 pbx systemd[1]: postfix.service: Unit process 180662 (service) remains running after unit stopped.
Sep 09 05:18:31 pbx systemd[1]: postfix.service: Unit process 180673 (postfix) remains running after unit stopped.
Sep 09 05:18:31 pbx systemd[1]: postfix.service: Unit process 182541 (postfix) remains running after unit stopped.
Sep 09 05:18:31 pbx systemd[1]: Stopped postfix.service.
Sep 09 05:18:31 pbx postfix[180673]: [FAILED]
Sep 09 05:18:36 pbx systemd[1]: Starting postfix.service...
Sep 09 05:18:36 pbx postfix[182616]: Starting postfix:
Sep 09 05:23:36 pbx systemd[1]: postfix.service: start operation timed out. Terminating.
Sep 09 05:23:36 pbx systemd[1]: postfix.service: Failed with result 'timeout'.
Sep 09 05:23:36 pbx systemd[1]: postfix.service: Unit process 182626 (postfix-chroot.) remains running after unit stopped.
Sep 09 05:23:36 pbx systemd[1]: postfix.service: Unit process 182645 (service) remains running after unit stopped.
Sep 09 05:23:36 pbx systemd[1]: postfix.service: Unit process 182656 (postfix) remains running after unit stopped.
Sep 09 05:23:36 pbx systemd[1]: postfix.service: Unit process 182671 (systemctl) remains running after unit stopped.
Sep 09 05:23:36 pbx systemd[1]: Failed to start postfix.service.
Sep 09 05:23:36 pbx postfix[182656]: Reloading postfix configuration (via systemctl):
Sep 09 05:23:36 pbx postfix[182671]: Job for postfix.service failed because a timeout was exceeded.
Sep 09 05:23:36 pbx postfix[182671]: See "systemctl status postfix.service" and "journalctl -xeu postfix.service" for details.
Sep 09 05:23:36 pbx postfix[182656]: [FAILED]#

Version-Release number of selected component (if applicable):

postfix-3.8.4-1.mga9.src.rpm

How reproducible: 

1. systemctl start postfix or postfix -c /etc/postfix -Dv start
2. Wait for the failure to show up
Comment 1 Dave Hodgins 2024-01-20 18:40:13 CET
Just fyi, it's working for me ...
[root@x3 ~]# systemctl status postfix.service
* postfix.service - LSB: Starts the postfix daemons
     Loaded: loaded (/etc/rc.d/init.d/postfix; generated)
    Drop-In: /etc/systemd/system/postfix.service.d
             `-override.conf
     Active: active (running) since Tue 2024-01-09 16:46:33 EST; 1 week 3 days ago
       Docs: man:systemd-sysv-generator(8)
   Main PID: 2077 (master)
      Tasks: 3 (limit: 19071)
     Memory: 24.8M
        CPU: 9.381s
     CGroup: /system.slice/postfix.service
             |-  2077 /usr/libexec/postfix/master -w
             |-  2182 qmgr -l -t unix -u -c
             `-503349 pickup -l -t unix -u -c -o content_filter= -o receive_override_options=

Jan 20 04:02:05 x3.hodgins.homeip.net postfix/pickup[489153]: 3E41C3C001B: uid=0 from=<root>
Jan 20 04:02:05 x3.hodgins.homeip.net postfix/cleanup[491297]: 3E41C3C001B: message-id=<20240120090205.3E41C3C001B@x3.hodgins.homeip.net>
Jan 20 04:02:05 x3.hodgins.homeip.net postfix/qmgr[2182]: 3E41C3C001B: from=<root@x3.hodgins.homeip.net>, size=1722, nrcpt=1 (queue active)
Jan 20 04:02:05 x3.hodgins.homeip.net postfix/local[491303]: 3E41C3C001B: to=<dave@x3.hodgins.homeip.net>, orig_to=<root>, relay=local, delay=0.05, delays=0.04/0/0/0.01, dsn=2.0.0, status=sent (delivered to ma>
Jan 20 04:02:05 x3.hodgins.homeip.net postfix/qmgr[2182]: 3E41C3C001B: removed
Jan 20 04:02:06 x3.hodgins.homeip.net postfix/pickup[489153]: 71DB13C001B: uid=0 from=<root>
Jan 20 04:02:06 x3.hodgins.homeip.net postfix/cleanup[491297]: 71DB13C001B: message-id=<20240120090206.71DB13C001B@x3.hodgins.homeip.net>
Jan 20 04:02:06 x3.hodgins.homeip.net postfix/qmgr[2182]: 71DB13C001B: from=<root@x3.hodgins.homeip.net>, size=1740, nrcpt=1 (queue active)
Jan 20 04:02:06 x3.hodgins.homeip.net postfix/local[491303]: 71DB13C001B: to=<dave@x3.hodgins.homeip.net>, orig_to=<root>, relay=local, delay=0.05, delays=0.04/0/0/0.01, dsn=2.0.0, status=sent (delivered to ma>
Jan 20 04:02:06 x3.hodgins.homeip.net postfix/qmgr[2182]: 71DB13C001B: removed
[root@x3 ~]# systemctl restart postfix.service
[root@x3 ~]# systemctl status postfix.service
* postfix.service - LSB: Starts the postfix daemons
     Loaded: loaded (/etc/rc.d/init.d/postfix; generated)
    Drop-In: /etc/systemd/system/postfix.service.d
             `-override.conf
     Active: active (running) since Sat 2024-01-20 12:33:30 EST; 2s ago
       Docs: man:systemd-sysv-generator(8)
    Process: 503510 ExecStart=/etc/rc.d/init.d/postfix start (code=exited, status=0/SUCCESS)
   Main PID: 503801 (master)
      Tasks: 3 (limit: 19071)
     Memory: 183.6M
        CPU: 1.574s
     CGroup: /system.slice/postfix.service
             |-503801 /usr/libexec/postfix/master -w
             |-503802 pickup -l -t unix -u -c -o content_filter= -o receive_override_options=
             `-503803 qmgr -l -t unix -u -c

Jan 20 12:33:26 x3.hodgins.homeip.net postfix[503510]: Starting postfix:
Jan 20 12:33:26 x3.hodgins.homeip.net postfix[503588]: ldd: warning: you do not have execution permission for `/var/spool/postfix/usr/lib64/libcap.so.2'
Jan 20 12:33:26 x3.hodgins.homeip.net postfix[503596]: ldd: warning: you do not have execution permission for `/var/spool/postfix/usr/lib64/libcap.so.2.52'
Jan 20 12:33:27 x3.hodgins.homeip.net postfix[503721]: Postfix is using backwards-compatible default settings
Jan 20 12:33:27 x3.hodgins.homeip.net postfix[503721]: See http://www.postfix.org/COMPATIBILITY_README.html for details
Jan 20 12:33:27 x3.hodgins.homeip.net postfix[503721]: To disable backwards compatibility use "postconf compatibility_level=3.6" and "postfix reload"
Jan 20 12:33:30 x3.hodgins.homeip.net postfix/postfix-script[503799]: starting the Postfix mail system
Jan 20 12:33:30 x3.hodgins.homeip.net postfix/master[503801]: daemon started -- version 3.8.4, configuration /etc/postfix
Jan 20 12:33:30 x3.hodgins.homeip.net postfix[503510]: [  OK  ]
Jan 20 12:33:30 x3.hodgins.homeip.net systemd[1]: Started postfix.service.
[root@x3 ~]# rpm -q postfix
postfix-3.8.4-1.mga9

I use postfix to put the email in /var/spool/mail, and dovecot to provide
pop3 access on one system and imap on another.

Don't forget to alter /etc/postfix/aliases and run the newaliases command.

CC: (none) => davidwhodgins

Comment 2 Muhammad Tailounie 2024-01-21 13:41:34 CET
Are you using it with a database backend?

I am using Mageia as my main server and postfix has never worked for me since I upgraded from M8!

I'll try to investigate it deeper, but please confirm what database backend you are using.
Comment 3 Muhammad Tailounie 2024-01-21 17:03:05 CET
Update:

Good news is that it works now :)

It was weird that it did not work yesterday, so I have decided today to reboot the server. After rebooting, postfix started perfectly, however still could not use mariadb backend. After digging into the issue, I have found out that postfix in M9 is running in chroot, Now I cannot tell if it was running in chroot on M8 or M7 where it always worked perfectly. So All I had to do is to bind-mount the mariadb socket directory to postfix chroot.

Thank you.

I do not know, whether to mark it as invalid, worksforme or what!

Status: NEW => RESOLVED
Resolution: (none) => INVALID

Comment 4 Dave Hodgins 2024-01-21 17:27:30 CET
Glad it's sorted.

Invalid is the correct resolution, as nothing Mageia provides was changed to
fix it.

I think it was Mageia 3 where postfix switched to running postfix in a chroot,
but I could be wrong about that.

What are you using the sql database for? The user aliases map?
Comment 5 Muhammad Tailounie 2024-01-22 08:51:15 CET
Thank you, I still find it weird that upon upgrade postfix did not work though!

Anyways, it is sorted now as you said.

I am using the database for aliases, domains, restrictions, users, quota...etc. Everything is configured using the sql database.

Note You need to log in before you can comment on or make changes to this bug.