>>> On Wed, Feb 4, 2009 at 11:03 AM, Victor Duchovni <victor.ducho...@morganstanley.com> wrote: > On Wed, Feb 04, 2009 at 08:58:17AM -0500, Doug Jaquays wrote: > >> > - The "pickup" fifo has been deleted from /var/spool/postfix/public >> > >> > Make sure $queue_directory contains a private/pickup fifo. >> >> This is a /var/spool/postfix/public/pickup fifo, there is not a > /var/spool/postfix/private/pickup fifo > > As you can tell from the first of the two lines, it is indeed "public" not > "private".
That's what I figured but wanted to make sure that you were not talking about two separate things > >> > - The O/S is buggy >> > >> > Disable SELinux, App-armor, ... >> >> This is entirely possible, though we have other SLES servers running >> the same environment without issue. I did just turn off AppArmor on >> the server with this problem, so we'll see what happens. > > Is the Postfix queue stored on an NFS server? Is the system clock correct? > Otherwise, report your findings post AppArmor, ... It is not stored via nfs, everything is stored "locally". It's actually stored on a FC lun on our san, but the VM doesn't know that and it doesn't affect file times. Our system times are correct, everything in our organization time syncs. With AppArmor turned off, it is still holding mail. > > Does: > > # postkick public pickup W > > move mail out of the queue in a more timely fashion? It does not seem to be anymore effective than mailq -q. Is there any more verbose logging that I can enable for this situation? PHP just cares that the message gets dumped into the queue and only returns yes it worked or no it didn't, which of course it works. It really seems like the timer to wakeup pickup isn't working properly, though I can't find any reason why it wouldn't be and nothing solid to say it isn't. It's frustrating to see that other systems set up exactly the same as far as I can tell work perfectly fine and this one doesn't. I suppose I could just install the Pear::Mail class and send directly to our main mail server. -Doug This email may contain confidential and privileged material for the sole use of the intended recipient and MSU-KCMS. Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
