Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

qmail-send defunct.

Status
Not open for further replies.
Sep 4, 2004
3
US
So in setting up aliases for a client, I restarted qmail.

lo and behold, qmail-send didn't come back up, and is now 'qmail-send <defunct>'.
The logs spew this every two seconds or so:

Sep 4 12:20:13 localhost qmail: 1094325613.914619 alert: cannot start: unable to read controls

-rw-r--r-- 1 root root 3 Aug 18 15:11 concurrencyincoming
-rw-r--r-- 1 root root 10 Aug 18 15:03 defaultdelivery
-rw-r--r-- 1 root root 13 Sep 3 21:36 defaultdomain
-rw-r--r-- 1 root root 13 Sep 3 21:15 defaulthost
-rw-r--r-- 1 root root 36 Sep 4 11:16 locals
-rw-r--r-- 1 root root 23 Sep 4 11:16 me
-rw-r--r-- 1 root root 13 Aug 18 15:00 plusdomain
-rw-r--r-- 1 root root 13 Aug 18 16:13 rcpthosts

Control dir matches my other working server, as do the values.

qmailctl stat:
/service/qmail-send: up (pid 2712) 1 seconds
/service/qmail-send/log: up (pid 31009) 700 seconds
/service/qmail-smtpd: up (pid 31012) 700 seconds
/service/qmail-smtpd/log: up (pid 31023) 700 seconds
messages in queue: 18
messages in queue but not yet preprocessed: 16

qmail-send alternates between 0 and 1, as supervise restarts it.

Life with Qmail's installation checker ( ) says I have a happy, working server.

Except that I don't.

Any ideas? All I did was muck around with aliases file, and such. newaliases wasn't working, due to the lack of defaulthost file in /control. Touched the defaulthost file, and newaliases seemed to work fine.
Then restarted qmail, and no love. I'm guessing that something else broke earlier, and that qmail just hasn't been restarted in a while.

Anyway, any help appreciated.

Thanks!

RN
 
/var/qmail/supervise/qmail-send/run as follows:

[root@mail qmail-send]# more run
#!/bin/sh
exec /var/qmail/rc

RC as follows:

[root@mail qmail]# more rc
#!/bin/sh

# Using stdout for logging
# Using control/defaultdelivery from qmail-local to deliver messages by default

exec env - PATH="/var/qmail/bin:$PATH" \
qmail-start "`cat /var/qmail/control/defaultdelivery`" splogger qmail

Regards,

RN
 
hrm,
this smells of a contention around a port perhaps, although typically smtpd is the one who complains about a competing service on port 25... trying to guess what else might affect qmail-send....

is your disk space ok?

Have you checked for a corrupted queue? You might have something in the queue that's bad. I forget where it is, but there's a queue checker util.

 
Disk is fine:
/dev/sda2 152744900 2829644 142156264 2%

Sendmail is eliminated, just qmail on this machine.

I ran a perl script across the Queue on that recommendation. Got a bunch of this:

message is neither local nor remote: 3833938
,mess message has no entry in info: 3833923
message is neither local nor remote: 3833923
,mess message has no entry in info: 3833944
message is neither local nor remote: 3833944

Neither local nor remote. That doesn't look right. Anyone seen that before?

But I've got locals, the defaults, and me set properly....hrm.

Luckily it's a holiday weekend...

Regards,

RN
 
You had some messages in your queue that must have been either (i) corrupted, or (ii) qmail doesn't know how to deliver them now.

I read your error snippet as there are lots of .mess -ages files with no .info, which is wrong..

You should spend time analyzing these items to see if you can figure out what happened. Make sure you don't have a delivery loop. Make sure that you don't have any typos in your rcpthosts.

In short, you have a bunch of undeliverable messages that should be purged from the queue since its extraordinarily hard to fix queue messages.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top