1 |
On Mon, 2004-05-03 at 11:41, Ben Munat wrote: |
2 |
> Thanks (you too, Dadi) for the ideas. My /var/log/qmail-send/current |
3 |
> contains over 500k of lines like this: |
4 |
> |
5 |
> |
6 |
> @400000004095ef010bac1efc alert: cannot start: qmail-send is already running |
7 |
> |
8 |
> I scrolled all the way through it... that's all there is. Doesn't sound |
9 |
> right. |
10 |
|
11 |
It isn't. |
12 |
|
13 |
In /service, there should be qmail-send, which is a symbolic link to |
14 |
/etc/qmail/supervise/qmail-send. Make sure there aren't other links |
15 |
pointing there. But it sounds more like qmail-send is being started |
16 |
somehow other that by svscan (which monitors /service). |
17 |
|
18 |
You can check the status of qmail-send like this: |
19 |
|
20 |
# svstat /service/qmail-send |
21 |
/service/qmail-send: up (pid 7162) 1206573 seconds |
22 |
|
23 |
If you get 0 seconds, something is wrong. I find that pstree is a good |
24 |
way to get a system overview: |
25 |
|
26 |
# pstree |
27 |
init-+-6*[agetty] |
28 |
... |
29 |
|-sshd---sshd---sshd---bash |
30 |
|-svscan-+-supervise---qmail-send-+-qmail-clean |
31 |
| | |-qmail-lspawn |
32 |
| | `-qmail-rspawn |
33 |
| `-supervise---multilog |
34 |
|-syslog-ng |
35 |
... |
36 |
|
37 |
If your system doesn't look like this, something is wrong. Could you |
38 |
have possibly manually started qmail-send? If so, you need to kill it. |
39 |
It may very likely also be running with different default delivery |
40 |
instructions if started manually. |
41 |
-- |
42 |
Andy Dustman <adustman@×××××××××.edu> |
43 |
Office of Information Technology, Terry College of Business, UGA |