Re: Relating to Domains..

From: N. <visionary_at_gmail.com>
Date: Wed, 28 Sep 2011 20:40:00 -0400

Thank you Murray. I've followed your directions exactly. You can see
where I do indeed do the strace on the child process ID, however the
strace.out doesn't show much it seems. And also, I started it BEFORE
sending the message, the email was sent successfully, and then I
stopped strace. HOWEVER, again the postfix log shows NOTHING. But,
again, the email was received. Latest in maillog followed by the
strace stuff.

Maillog:

Sep 28 19:42:56 private opendkim[26710]: OpenDKIM Filter v2.4.2
starting (args: -x /etc/opendkim.conf -P
/var/run/opendkim/opendkim.pid)

Strace:

[root_at_private ~]# ps laxww | fgrep opendkim
1 101 26709 1 22 0 5480 736 wait Ss ? 0:00
/usr/local/sbin/opendkim -x /etc/opendkim.conf -P
/var/run/opendkim/opendkim.pid
1 101 26710 26709 15 0 25968 1500 stext Sl ? 0:00
/usr/local/sbin/opendkim -x /etc/opendkim.conf -P
/var/run/opendkim/opendkim.pid
0 0 26880 26847 18 0 3988 564 pipe_w S+ pts/1 0:00
fgrep opendkim
[root_at_private ~]# strace -o strace.out -f -p 26710
Process 26710 attached with 3 threads - interrupt to quit
Process 26710 detached
Process 26711 detached
Process 26712 detached
anaconda-ks.cfg install.log install.log.syslog strace.out
[root_at_private ~]# cat strace.out
26712 rt_sigtimedwait([HUP INT TERM], <unfinished ...>
26711 rt_sigtimedwait([USR1], <unfinished ...>
26710 select(4, [3], NULL, [3], {1, 441000}) = 0 (Timeout)
26710 select(4, [3], NULL, [3], {5, 0}) = 0 (Timeout)
26710 select(4, [3], NULL, [3], {5, 0}) = 0 (Timeout)
26710 select(4, [3], NULL, [3], {5, 0}) = 0 (Timeout)
26710 select(4, [3], NULL, [3], {5, 0}) = 0 (Timeout)
26710 select(4, [3], NULL, [3], {5, 0}) = 0 (Timeout)

On Wed, Sep 28, 2011 at 2:50 PM, Murray S. Kucherawy <msk_at_blackops.org> wrote:
> On Wed, 28 Sep 2011, N. wrote:
>>
>> I'm having a very weird problem trying to get that port 8891 "free". I
>> keep trying to kill processes, and more spawn. And its from the opendkim
>> user.
>>
>> Actually, I didn't have this error before and opendkim was starting fine.
>> But it just wasn't logging or signing email.
>>
>> Also, with this instruction Murray:
>>
>> "2) Start strace watching the child process.  Use "ps laxww" to figure
>> out which one was the child."
>>
>> Could you link me to the text that discusses the "child"? I assume
>> this is opendkim "child" yes? I used ps laxww but I saw a lot of
>> things I wasn't familiar with. How do I identify the "child" in that
>> output? (what text will I see)? Also, do you happen to have a command
>> for strace handy that I should use to have it running in the
>> background? I really appreciate it.
>
> medusa[1127]% ps laxww | fgrep opendkim
>  1000   879     1 386 8 0 17608     0 wait   IWs   ??    0:00.00
> /home/msk/auth/opendkim -x /home/msk/auth/opendkim.conf (opendkim-2.4.2)
>  1000   880   879   0  20  0 33944 16776 kserel S     ??    4:31.29
> /home/msk/auth/opendkim -x /home/msk/auth/opendkim.conf (opendkim-2.4.2)
>
> The first column is the UID of the process.  The second is the pid of the
> process, and the third is the pid of its parent.  You can see here that the
> second one is the child, as its parent is 879 which is also an opendkim
> process.  The first one's parent is the init process, so it is not the
> opendkim child.
>
> For strace, try:
>
>        strace -o strace.out -f -p 880
>
> (replace "880" with the process ID of your opendkim child process)
>
> ...and then send a message through postfix.
>
> You are probably seeing 8891 not free because opendkim is configured to
> restart the child when it dies.  Instead, you need to kill the parent. Using
> "kill -9" is too severe to get it to shutdown cleanly unless you use it on
> both the parent and the child at the same time.  Instead, using "kill -15"
> on the parent should complete the process.
>
> On the other hand, you can simplify your work by using "strace" on the
> process that "lsof" tells you is holding port 8891, and then run your
> postfix test.
>
Received on Thu Sep 29 2011 - 00:40:14 PST