Submitted by PaliGap on Mon, 04/12/2010 - 09:52 Pro Licensee
I followed the instructions for a clean install on CentOS Linux 5.4.
That seems to have gone very well except for one thing. Postfix was hanging because it expected unix db "hash". But this was not present on this CentOS image. After figuring out the problem , I changed Postfix "default database type" to "btree" and it worked.
Status:
Active
Comments
Submitted by JamieCameron on Mon, 04/12/2010 - 13:31 Comment #1
That's surprising - the hash map type is the Postfix default, and should always be available.
What does the
postconf -mcommand output on your system?Submitted by PaliGap on Mon, 04/12/2010 - 14:57 Pro Licensee Comment #2
Mmm... Now I'm puzzled.
Yesterday I ran that and I'm sure hash was missing. Postfix wasn't working and I had errors in the log. I then changed over to btree and also ran "newaliases". Post fix was now OK. And now.. I have this for postconf -m!
btree cidr environ hash ldap nis pcre proxy regexp static unix
Now I'm wondering whether all that was wrong was that I hadn't run "newaliases".
;-)
Submitted by JamieCameron on Mon, 04/12/2010 - 15:07 Comment #3
That's certainly odd, I've never seen the
hashtype go missing like that before.What was the exact error message from Postfix?
Submitted by PaliGap on Mon, 04/12/2010 - 17:28 Pro Licensee Comment #4
The log was:
Apr 11 04:03:09 postfix/local[11480]: fatal: open database /etc/aliases.db: No such file or directory Apr 11 04:03:10 postfix/master[6319]: warning: process /usr/libexec/postfix/local pid 11480 exit status 1 Apr 11 04:03:10 postfix/master[6319]: warning: /usr/libexec/postfix/local: bad command startup -- throttling
Submitted by JamieCameron on Mon, 04/12/2010 - 17:33 Comment #5
Ok, looks like the issue was that aliases.db didn't exist yet, and newaliases hadn't been run.
I will add that to our install script.