[SOLVED] Upgraded f15 to f16 Postfix doesn't start

[pnelsonsr]

Upgraded from F15 to F16.

On reboot Postfix is not starting up. I checked with chkconfig postfix --list and its listed as:

postfix 0:off 1:off 2:on 3:on 4:on 5:on 6:off

but when the systems starts it doesn't. I looked at the systemd stuff with:

ls /etc/systemd/system/*.wants/postfix.service

and its not listed. So I tried systemctl enable postfix.service and got:

postfix.service is not a native service, redirecting to /sbin/chkconfig.
Executing /sbin/chkconfig postfix on
Warning: unit files do not carry install information. No operation executed.

I tried setting up a posfix.service with:

<--snip-->
[Unit]
Description=Postfix Mail Server
After=syslog.target
After=network.target

[Service]
Type=forking
ExecStart=/usr/sbin/postfix -c /etc/postfix start
ExecStop=/usr/sbin/postfix -c /etc/postfix stop
ExecReload=/usr/sbin/postfix -c /etc/postfix reload

[Install]
WantedBy=multi-user.target
<--snip-->

and then enabling it with:

systemctl enable postfix.service
-and-
chkconfig postfix on

and while this works with chkconfig and systemctl commands, it still does not load up at boot. I have checked the mail log and the last entry after a reboot is:

Nov 27 09:46:44 <srv name removed> postfix/postfix-script[1235]: starting the Postfix mail system

so it seems it is stopping there and I cannot find out why. When I run service postfix start or systemctl start postfix.service then it starts with that starting log entry and is followed by a:

Nov 27 10:02:40 <srv name removed> postfix/master[2508]: daemon started -- version 2.8.7, configuration /etc/postfix

After a reboot I run systemctl list-units which should list postfix (in any state) but doesn't and chkconfig --list doesn't list it either. But once I run systemctl start postfix it then shows up in systemctl list-units list.

Kind of clueless as to where else to look.. Any ideas? Maybe moving it further down to the end of the boot process?

[AdamW]

yeah, it does seem like the service is firing but postfix isn't successfully starting.

i'd probably start by removing your hand-made systemd service, it's likely only to confuse things. stick with the legacy service and focus on figuring out why postfix isn't starting successfully. see if the process is still there after boot completes, and see if you can connect to it with strace or gdb and figure out what it's stuck on, maybe. or see if you can make it start up with more verbose logging parameters, and see if that gives a better clue about how it gets stuck.

[pnelsonsr]

I now did go back to dropping out of the postfix.service systemd thing and back to the system V thing. Same thing happens though. I'll poke around a bit with your suggestions.

[DBelton]

possibly this is that bash bug that happened on F16??

Since sysvinit is basically bash scripts, it is possible that the bash bug bit you, but not sure if it's what is causing your problems or not.

AdamW up there posted it someplace, but the fix is to reinstall bash.

(This is just a shot in the dark, but you really need to do the re-install of bash if you haven't already anyway)

yum reinstall bash

Edit: add link to AdamW's post:

http://forums.fedoraforum.org/showthread.php?t=272671

[pnelsonsr]

Well I check the /etc/shells file and sure enough it was missing bash and sh entries. So I ran the yum reinstall bash and rebooted. Drat postfix still didn't start on its own.

[pnelsonsr]

After upgrading with the new kernel package (kernel-PAE-3.1.5-1.fc16.i686) postfix started on bootup. So I'll close this for now.