On 13/10/2011 6:40 μμ, Wietse Venema wrote:
A few messages ago, I asked this:To find out what system call is failing, see the strace instructions in http://www.postfix.org/DEBUG_README.html, and compare strace results.
Hi Wietse,First, I found the cause: It was selinux (once more...). Although I thought it was disabled, in fact it wasn't. (And I was SO SURE I had checked; it's embarrassing.)
Sorry for the noise...But, I would like to have a clarification on what I do wrong with the debugging:
I believed I followed in detail the directions (as described in that doc, "Automatically tracing a Postfix daemon process"):
I added in /etc/postfix/main.cf: debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin (strace -p $process_id 2>&1 | logger -p mail.info) & sleep 5 and then in /etc/postfix/master.cf: local unix - n n - - local -DI expected "local" to be automatically strace'd but I didn't see anything in the logs except:
Oct 13 19:33:42 vpnspot postfix/local[12852]: running: PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin (strace -p 12852 2>&1 | logger -p mail.info) & sleep 5
So, I tried running manually in the background: # strace -f -p12843 -odebug2 &where 12843 was the "master" postfix process (at that point). (AFAIK local process is created on the fly and we don't know its process-id beforehand to run strace on it.)
Then I retried sending a local mail to root. The following indication in strace output guided me to re-investigate selinux settings...
12952 lstat("/root/.forward", 0x7fffbbb16660) = -1 EACCES (Permission denied)
But what did I do wrong and strace was not done "automatically"? Thanks, Nick
smime.p7s
Description: S/MIME Cryptographic Signature