RE: cannot start: hath the daemon spawn no fire?

[Dave Sill]

[EMAIL PROTECTED] wrote:

cannot start: hath the daemon spawn no fire?

That means qmail-send was unable to talk to qmail-lspawn,
qmail-rspawn, or qmail-clean, which means that qmail-start wasn't able
to start them or they died immediately.

-Dave

RE: cannot start: hath the daemon spawn no fire?

[MIS - Ben Murphy]

Hi All,

I guess its not exactly a common problem - no so ones responding.
forget the rpms, and all that stuff. simply what would/could cause the
error?

cannot start: hath the daemon spawn no fire?

in /var/log/qmail/ log file?

Thanx in advance

Ben Murphy,
e-mail: [EMAIL PROTECTED]

RE: cannot start: hath the daemon spawn no fire?

[Mike Peppard]

www.ezmlm.org/pub/patches/qmail-bigrem.patch

The code and reason is there.  You should check
with the ezmlm group.

 -Original Message-
 From: MIS - Ben Murphy [mailto:[EMAIL PROTECTED]]
 Sent: Friday, June 29, 2001 7:30 AM
 To: Mailing List - Qmail (E-mail)
 Subject: RE: cannot start: hath the daemon spawn no fire?

Re: cannot start: hath the daemon spawn no fire?

[Petru Paler]

 Greetings:
 
 I have installed qmail-1.0.3 with the qmail-ldap-1.03-19990525 patch
 applied on a Caldera 1.3 box.
 
 When attempting to start qmail, the daemons do not come up.  The only
 indication that anything at all happened is a line like the following in
 /var/log/mail.
 
 Jun  7 10:55:44 blitz qmail: 928770944.705898 alert: cannot start: hath
 the daemon spawn no fire?
 
 That diagnostic doesn't give me a whole lot to go on, and web searches
 on that phrase come up empty.  I gather that it isn't terribly common.
 Does anybody know what causes this problem and what I should be looking
 at to fix it?

   Is the LDAP server started and control/ldap* files set up correctly ?

---
Keep your mouth shut and people will think you stupid;
Open it and you remove all doubt.