[SOLVED] ZCS 6.0: Postfix does not start

[rty]

can you post the output of zmcontrol status. are you sure you don't have any OS installed versions of postfix running?

zimbra@zimbra:~$ zmcontrol status
Host zimbra.....
	antispam                Running
	antivirus               Running
	ldap                    Running
	logger                  Running
	mailbox                 Running
	mta                     Stopped
		postfix is not running
	snmp                    Running
	spell                   Running
	stats                   Stopped

Yes, I am sure about that. All I did was to install a missing stats package and upgrade from 5.0.18 to 6.0.
Nobody else is listening on port 25.

[quanah]

Why do you have things in your spool that aren't owned by postfix?

/opt/zimbra/data/postfix/./spool/maildrop/1A0FF27E

for example

[rty]

Why do you have things in your spool that aren't owned by postfix?



for example

good question. Since the thing I changed is Zimbra 6.0 instead of Zimbra 5.0.38, that's where I am pretty sure the reason lies. You should know better than me what exactly it is about Zimbra 6.0 that messes up file ownerships.
As I said, to get from a working Zimbra 5 installation to a messed-up Zimbra 6 installation, all I did was to install the one new package install.sh asked for, and then upgrade Zimbra.

[brian]

Your /etc/nsswitch.conf contained

protocols: db files
services: db files
ethers: db files
rpc: db files

This was causing libnss.so to load libnss_db.so which is linked against libdb-4.3.so. This conflicts with the bdb version libdb-4.7.so that postfix is linked against. Postfix output wasn't really indicating that it was segfaulting but if you tried to run /opt/zimbra/postfix/libexec/master by hand it was noticeable.

Changing db files to just files resolves the issue.

[rty]

thank you very much!

I would suggest to add something about this to the release notes.

Zimbra 5 worked fine with that version of /etc/nsswitch.conf.

[rty]

I am not marking it as solved yet because there still seems to be some postfix issue lingering. Yes, it does not crash now, but I get this error message:

Sep  4 08:54:30 zimbra postfix/postqueue[10678]: fatal: chdir /opt/zimbra/data/postfix/spool: Permission denied
Sep  4 08:54:46 zimbra su[8705]: (pam_unix) session closed for user zimbra
Sep  4 08:54:46 zimbra postfix/sendmail[10683]: fatal: chdir /opt/zimbra/data/postfix/spool: Permission denied
Sep  4 08:55:00 zimbra postfix/postqueue[10949]: fatal: chdir /opt/zimbra/data/postfix/spool: Permission denied

I find this odd because the spool directory is owned by postfix:

zimbra:/# ll /opt/zimbra/data/postfix/      
total 4
-rw-------  1 postfix zimbra   17 Sep  4 08:51 master.lock
drwxr-xr-x 16 postfix postfix 384 Jan 30  2009 spool

Inside the directory, stuff is owned by postfix:

 ll /opt/zimbra/data/postfix/spool/
total 1
drwx------  2 postfix postfix   48 Sep  3 23:50 active
drwx------  2 postfix postfix   48 Sep  3 23:50 bounce
drwx------  2 postfix postfix   48 Jan 30  2009 corrupt
drwx------ 18 postfix postfix  432 Jul  4 14:44 defer
drwx------ 18 postfix postfix  432 Jul  4 14:44 deferred
drwx------  2 postfix postfix   48 Jan 30  2009 flush
drwx------  2 postfix postfix   48 Jan 30  2009 hold
drwx------  2 postfix postfix   48 Sep  3 23:50 incoming
drwx-wx---  2 postfix postdrop  48 Sep  3 23:46 maildrop
drwxr-xr-x  2 postfix root     464 Sep  1 14:24 pid
drwx------  2 postfix postfix  640 Sep  4 08:51 private
drwx--x---  2 postfix postdrop 168 Sep  4 08:51 public
drwx------  2 postfix postfix   48 Jan 30  2009 saved
drwx------  2 postfix postfix   48 Jan 30  2009 trace

How should I understand this?
I ran zmfixperms and looked again, and the permissions are still the same.

[uxbod]

What are the permissions on the directory /opt/zimbra/data/postfix ?

[rty]

What are the permissions on the directory /opt/zimbra/data/postfix ?

drwx------ 3 postfix zimbra 104 Sep 3 12:37 postfix

[uxbod]

chmod 755 postfix

[rty]

chmod 755 postfix

thanks, of course this cures the symptom (for now), but I'd also be interested in the underlying problem:
- why does zmfixperms not fix the perms?
- even more importantly, why are they messed up in the first place?