Die= could not telnet to port 25 nor port 110 while other services (ssh,
http) worked fine.
I did not see any process entries for qmail-local, qmail-remote,
qmail-smtpd, etc. No supervise, no nothing. When I did a qmail.init
start it said it was running.
At 00:06:51 is did get several remote concurrencies of 95/100:
Jul 11 00:06:51 mail qmail: 963288411.324240 status: local 0/100 remote
95/100
Jul 11 00:06:51 mail qmail: 963288411.375459 delivery 79091: failure:
209.142.136.251_does_not_like_recipient./Remote_host_said:_550_<EMAIL
ADDRESS DELETED>..._User_unknown/Giving_up_on_209.142.136.251./
Then
Jul 11 00:46:26 mail qmail: 963290786.980592 status: local 0/100 remote
95/100
Jul 11 00:47:11 mail qmail: 963290831.710369 delivery 79150: deferral:
CNAME_lookup_failed_temporarily._(#4.4.3)/
Agian:
Jul 11 01:23:52 mail qmail: 963293032.426050 status: local 0/100 remote
96/100
Jul 11 01:25:05 mail qmail: 963293105.760403 delivery 79247: deferral:
CNAME_lookup_failed_temporarily._(#4.4.3)/
qmail goes through this 0-96-0 cycle 5 or 6 times. Either getting a CNAME
failure or saying it delivered to remote.
Did I run out of resources? Was someone jamming up the mail server with
huge mailings??
Paul Farber
Farber Technology
[EMAIL PROTECTED]
Ph 570-628-5303
Fax 570-628-5545
On Tue, 11 Jul 2000, James Raftery wrote:
> On Tue, Jul 11, 2000 at 09:55:03AM -0400, Paul Farber wrote:
> > I just had qmail 1.03 ucspi-88 on a RH box die on me again.
>
> Could you elaborate on "die" ?
>
> > Log files seem to indicate that ident was having problems:
> > Jul 11 00:06:50 mail in.identd[19532]: request_thread: read(0, ..., 1023)
> > failed: Connection reset by peer
>
> We get truck loads of them, and have never been associated with any
> qmail trouble.
>
> > but there are other errors in the mail log, basically CNAME lookup
> > failures
> > It looks like supervise died, but when I tried to restart qmail it said it
> > was already running... I didn't see it in the ps output.
>
> DNS lookups don't cause qmail to stop functioning, just defer mail.
> supervise and qmail are different things entirely. supervise can stop
> and qmail will continue to function. The idea behind supervise is that
> it watches to see if qmail is running. If not, it starts it. If
> supervise stops running all you lose is the process checking that
> qmail is running. qmail itself is unaffected.
>
> Are you sure qmail wasn't running? Did you find 'exiting' in the qmail
> logs ? What else was in the logs ?
>
> > Any ideas? Do I need to run DJB's DNS daemon also? Thanks!
>
> It wouldn't be a bad idea though I doubt it's related to this
> problem!
>
> Regards,
>
> james
> --
> James Raftery (JBR54) - Programmer Hostmaster - IE TLD Hostmaster
> IE Domain Registry - www.domainregistry.ie - (+353 1) 706 2375
> "Managing 4000 customer domains with BIND has been a lot like
> herding cats." - Mike Batchelor, on [EMAIL PROTECTED]
>
