Wietse Venema put forth on 9/27/2009 8:30 AM: > Stan Hoeppner: >> Wietse Venema put forth on 9/27/2009 7:39 AM: >>> If you have a question about POSTFIX logs, then it is a good idea >>> to send samples of POSTFIX logging. >> Point taken, sry Wietse. Upon grabbing these sample entries, I noticed >> the transactions pflogsumm is flagging have no qmgr entries. That >> explains why pflogsumm is complaining there is no size data. So, I >> guess the question is, why did qmgr intermittently/randomly stop >> stamping the log file, as of a day or two ago? > > Apparently, your system runs daemons in a chroot environment that > does not contain the required syslog socket. > > As shipped by me, Postfix does not run daemons in a chroot environment, > because the details vary with operating system and with system > version. If a maintainer or system administrator turns on the > Postfix chroot feature, then it is their responsibility to set > things up properly.
Hi Wietse, If the chroot environment does not contain the required syslog socket, then why does qmgr place a stamp in the log for some message transactions and not others? From what I can see in the log file, more messages have a qmgr stamp than not. I'm not very familiar with chroot, other than the basic theory behind it, and the fact that this seems to be the Debian default Postfix configuration. Something I thought of since I originally posted about this is that I tried to change the Debian log rotation a couple of days ago from rolling the mail log every 4 days to 14 days. Since this is done by cron it has nothing to do with syslogd. However, at the time, I made a change that I thought required restarting the syslogd daemon. I'm wondering if merely restarting syslogd while the system was running may have played a part in this inconsistent qmgr logging. So, I rebooted the box late yesterday to see if things come back to normal. I'll post back later today after I have enough log data to make a sensible determination. Sorry for taking up folks' time with this, as the cause may not be related to Postfix. I'm not an expert WRT Postfix logging mechanisms or syslogd. And Debian defaulting to a chroot Postfix environment obviously doesn't make troubleshooting this a routine or mundane exercise. Thanks for your help, and patience with me. -- Stan
