From: Jay Guerette (JayGuerettepobox.com)
Date: Thu Jul 29 2004 - 00:39:31 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

I am currently running 2 instances of postfix, and I am trying to add a 3rd. This is the same process I used to create the 2nd from the 1st.

I duplicated the configuration from a working instance, changed the domain name and IP addresses. A simple diff of the main.cf in each configuration directory confirms those are the only differences.

I duplicated the spool directory from a working instance, and ran 'postfix -c /path/to/newconfdir check'. Careful examination and some diffs prove it is identical.

The third instance does not send mail, and there are no log entries made when I try to send mail through that instance. Meanwhile, these errors keep popping up:

warning: master_wakeup_timer_event: service public/qmgr: No such file or directory
warning: master_wakeup_timer_event: service public/pickup: No such file or directory

The "directories" DO exist, as pipes, with the same ownership and permissions as those in the spool directory of a working instance. When I rename the spool directories between the 2nd and 3rd instance, the 2nd instance continues to work fine, and the 3rd instance still doesn't work. So I know the spool directory is/was fine.

Having spent 3 days of examining verbose logging and just about everything even tangentionally related; I'm at a loss.

There is only one thing that is different about this instance from the other 2. It is for a domain that I will take ownership of in a few days. I had the current owner create an A record for this new mail host, and the reverse is also mapped to the hostname. Is it possible that Postfix is detecting the fact that this server is not in the MX for this domain, and silently refusing to run or simply failing?

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]