1 |
Well, that appears to have been one of my problems. I think it was |
2 |
because of the "start qmail processes" button in webmin. This is how my |
3 |
process tree looked right after I read your email: |
4 |
|
5 |
|-pagebufd |
6 |
|-qmail-send-+-qmail-clean |
7 |
| |-qmail-lspawn |
8 |
| `-qmail-rspawn |
9 |
|-sshd---sshd---bash---pstree |
10 |
|-svscan-+-2*[supervise---tcpserver] |
11 |
| |-3*[supervise---multilog] |
12 |
| `-supervise---qmail-send |
13 |
|-syslog-ng |
14 |
|
15 |
I stopped the qmail processes from within webmin and then, just to be |
16 |
safe, restarted svscan with /etc/init.d/svscan. Now I get this: |
17 |
|
18 |
|-sshd---sshd---bash---pstree |
19 |
|-svscan-+-2*[supervise---tcpserver] |
20 |
| |-3*[supervise---multilog] |
21 |
| `-supervise---qmail-send-+-qmail-clean |
22 |
| |-qmail-lspawn |
23 |
| `-qmail-rspawn |
24 |
|-syslog-ng |
25 |
|
26 |
My question now is, is it okay that my process tree says 2* and 3* for |
27 |
tcpserver and multilog? |
28 |
|
29 |
And, unfortunately, it still doesn't seem to be working. Well, at least |
30 |
I don't get the "cannot start" messages in the log... but now they look |
31 |
like this: |
32 |
|
33 |
@40000000409669710e4d4334 status: local 0/10 remote 0/20 |
34 |
@40000000409669710eec55dc bounce msg 248578 qp 3022 |
35 |
@40000000409669710eec7134 end msg 248578 |
36 |
@40000000409669710f065dec new msg 248577 |
37 |
@40000000409669710f067944 info msg 248577: bytes 1368 from <#@[]> qp |
38 |
3022 uid 206 |
39 |
@40000000409669710f5099d4 starting delivery 9: msg 248577 to remote |
40 |
postmaster@×××××.org |
41 |
@40000000409669710f50bcfc status: local 0/10 remote 1/20 |
42 |
@40000000409669710fc3c24c delivery 9: failure: |
43 |
Sorry._Although_I'm_listed_as_a_best-preference_MX_or_A_for_that_host,/it_isn't_in_my_control/locals_file,_so_I_don't_treat_it_as_local._(#5.4.6)/ |
44 |
@40000000409669710fc3e574 status: local 0/10 remote 0/20 |
45 |
@40000000409669710fc3f12c triple bounce: discarding bounce/248577 |
46 |
@40000000409669710fc3f8fc end msg 248577 |
47 |
|
48 |
BTW, I'm trying to do the qmail-inject example in the gentoo docs... and |
49 |
I still have a problem with mutt. How else can I check to see if the |
50 |
mail has gone through? Should it just be a file under ~/.maildir/new? |
51 |
|
52 |
Thanks for sticking with me! |
53 |
|
54 |
Ben |
55 |
|
56 |
|
57 |
|
58 |
Andy Dustman wrote: |
59 |
> On Mon, 2004-05-03 at 11:41, Ben Munat wrote: |
60 |
> |
61 |
>>Thanks (you too, Dadi) for the ideas. My /var/log/qmail-send/current |
62 |
>>contains over 500k of lines like this: |
63 |
>> |
64 |
>> |
65 |
>>@400000004095ef010bac1efc alert: cannot start: qmail-send is already running |
66 |
>> |
67 |
>>I scrolled all the way through it... that's all there is. Doesn't sound |
68 |
>>right. |
69 |
> |
70 |
> |
71 |
> It isn't. |
72 |
> |
73 |
> In /service, there should be qmail-send, which is a symbolic link to |
74 |
> /etc/qmail/supervise/qmail-send. Make sure there aren't other links |
75 |
> pointing there. But it sounds more like qmail-send is being started |
76 |
> somehow other that by svscan (which monitors /service). |
77 |
> |
78 |
> You can check the status of qmail-send like this: |
79 |
> |
80 |
> # svstat /service/qmail-send |
81 |
> /service/qmail-send: up (pid 7162) 1206573 seconds |
82 |
> |
83 |
> If you get 0 seconds, something is wrong. I find that pstree is a good |
84 |
> way to get a system overview: |
85 |
> |
86 |
> # pstree |
87 |
> init-+-6*[agetty] |
88 |
> ... |
89 |
> |-sshd---sshd---sshd---bash |
90 |
> |-svscan-+-supervise---qmail-send-+-qmail-clean |
91 |
> | | |-qmail-lspawn |
92 |
> | | `-qmail-rspawn |
93 |
> | `-supervise---multilog |
94 |
> |-syslog-ng |
95 |
> ... |
96 |
> |
97 |
> If your system doesn't look like this, something is wrong. Could you |
98 |
> have possibly manually started qmail-send? If so, you need to kill it. |
99 |
> It may very likely also be running with different default delivery |
100 |
> instructions if started manually. |