OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: 3rd instance of Postfix, duplicate of working instance, doesn't work & generates errors

From: Jay Guerette (JayGuerettepobox.com)
Date: Thu Jul 29 2004 - 23:45:58 CDT

Thank you for taking the time to consider my problem.

The solution was as wierd as the problem. It's a busy Linux server, 400+ processes running, and I didn't notice a wedged 'master' process. The init.d script didn't report any failure shutting down the various instances. I noticed it by chance only, and it took a SIGKILL to kill it. Everything ran like a champ after that. Three instances, no problems.

Thanks again, Wietse, for taking the time to try to help.

On Thu, 29 Jul 2004 10:08:16 -0400 (EDT)
wietseporcupine.org (Wietse Venema) wrote:

> Jay Guerette:
> > 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 permissi
>
> Plural? Only "public" is supposed to be a directory.
>
> What about the "qmgr" and "pickup" sockets under that directory?
> They are created by the Postfix master daemon, following instructions
> in master.cf; the same file that tells the Postfix master daemon
> to send wakeup probes to those sockets.
>
> What operating system is this? Some (Linux) systems are quite sloppy
> in their error returns.
>
> Have you tried:
>
> postfix -c config_directory set-permissions
>
> in case the access permissions are incorrect? This is a
> Postfix 2.1 feature.
>
> Given that you have three Postfix instances of which two work,
> try reducing the broken one to just the minimal main.cf changes
> from the default Postfix main.cf file: different queue_directory,
> and all files kept in a separate config_directory, of course.