Re: Qmail Problems

2004-12-13 Thread Mike Grissom
Anyone have an insights to this problem?
- Original Message - 
From: Mike Grissom [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, December 12, 2004 2:59 PM
Subject: Qmail Problems

I have been having a problem with qmail-send dying for a while now.  In the
log file it says that alert: oh no! lost spawn connection which leads me
to believe the problem is with the qmail-lspawn or qmail-rspawn.  I have
FreeBSD 4.10-STABLE #0: Thu Nov 11 17:21:04 EST 2004 installed on the box.
Any ideas what could be causing this?  Or how to fix this problem?

No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.296 / Virus Database: 265.5.0 - Release Date: 12/9/2004



___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
[EMAIL PROTECTED]

--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.296 / Virus Database: 265.5.0 - Release Date: 12/9/2004
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Qmail Problems

2004-12-13 Thread Giorgos Keramidas
On 2004-12-13 14:53, Mike Grissom [EMAIL PROTECTED] wrote:
 Mike Grissom [EMAIL PROTECTED] wrote:
  I have been having a problem with qmail-send dying for a while now.
  In the log file it says that alert: oh no! lost spawn connection
  which leads me to believe the problem is with the qmail-lspawn or
  qmail-rspawn.  I have FreeBSD 4.10-STABLE #0: Thu Nov 11 17:21:04
  EST 2004 installed on the box.  Any ideas what could be causing
  this?  Or how to fix this problem?

 Anyone have an insights to this problem?

Please don't top-post.  I've fixed your post this time, but I don't feel
like doing it for any future posts.

Regarding qmail now: It would help if you posted more details about your
setup or even the log messages in their entirety.

A quick search at google reveals that qmail people think this message
signifies an OS bug:

http://www.bsw.dk/qmail-archive/1998/msg00221.html

You may also find the following web pages of interest:

http://www.faqts.com/knowledge_base/view.phtml/aid/1749
http://citadelle.intrinsec.com/mailing/current/HTML/ml_qmail/8150.html
https://citadelle.intrinsec.com/mailing/current/HTML/ml_qmail/25931.html

HTH,
Giorgos

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Qmail Problems

2004-12-13 Thread Tabor Kelly
Mike Grissom wrote:
I have been having a problem with qmail-send dying for a while now. In the log file
 it says that alert: oh no! lost spawn connection which leads me to
 believe the problem is with the qmail-lspawn or qmail-rspawn.  I have
 FreeBSD 4.10-STABLE #0: Thu Nov 11 17:21:04 EST 2004 installed on the
 box.  Any ideas what could be causing this?  Or how to fix this
 problem?
snip
In addition to everything Mike Grissom [EMAIL PROTECTED] said, please 
tell us if you installed qmail from ports or directly from the source 
tarball on cr.yp.to?

Also, how often does it die? Can you reproduce the bug on demand?
-Tabor Kelly
PS- please configure your email client to use hard line breaks after 70 
characters (70 characters per line).
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Qmail Problems

2004-12-13 Thread Tabor Kelly
Tabor Kelly wrote:
snip
In addition to everything Mike Grissom [EMAIL PROTECTED] said
Sorry, I meant Giorgos Keramidas [EMAIL PROTECTED].
snip
-Tabor Kelly
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Qmail Problems

2004-12-13 Thread Mike Grissom
How do I set hard line breaks in outlook express?
It was installed via source.  It seems to die every day or 2.  I have
some ktrace outputs now from qmail-lspawn and qmail-rspawn.  One of
those are the ones that are dying and making qmail-send die.
Here is the outputs (last 50 lines):
qmail-lspawn ktrace output:
23190 qmail-lspawn RET   close 0
23190 qmail-lspawn CALL  fcntl(0x4,0x2,0x1)
23190 qmail-lspawn RET   fcntl 0
23190 qmail-lspawn CALL  sigprocmask(0x2,0xbfbffca0,0)
23190 qmail-lspawn RET   sigprocmask 0
23190 qmail-lspawn CALL  select(0x4,0xbfbffd00,0,0,0)
23190 qmail-lspawn RET   select 1
23190 qmail-lspawn CALL  sigprocmask(0x1,0xbfbffca0,0)
23190 qmail-lspawn RET   sigprocmask 0
23190 qmail-lspawn CALL  read(0x3,0x804d520,0x80)
23190 qmail-lspawn GIO   fd 3 read 10 bytes
  did 0+0+1
  
23190 qmail-lspawn RET   read 10/0xa
23190 qmail-lspawn CALL  sigprocmask(0x2,0xbfbffca0,0)
23190 qmail-lspawn RET   sigprocmask 0
23190 qmail-lspawn CALL  select(0x4,0xbfbffd00,0,0,0)
23190 qmail-lspawn PSIG  SIGCHLD caught handler=0x80492a4 mask=0x0
code=0x0
23190 qmail-lspawn RET   select -1 errno 4 Interrupted system call
23190 qmail-lspawn CALL  wait4(0x,0xbfbffb10,0x1,0)
23190 qmail-lspawn RET   wait4 51093/0xc795
23190 qmail-lspawn CALL  close(0x4)
23190 qmail-lspawn RET   close 0
23190 qmail-lspawn CALL  wait4(0x,0xbfbffb10,0x1,0)
23190 qmail-lspawn RET   wait4 -1 errno 10 No child processes
23190 qmail-lspawn CALL  sigreturn(0xbfbffb30)
23190 qmail-lspawn RET   sigreturn JUSTRETURN
23190 qmail-lspawn CALL  sigprocmask(0x1,0xbfbffca0,0)
23190 qmail-lspawn RET   sigprocmask 0
23190 qmail-lspawn CALL  sigprocmask(0x2,0xbfbffca0,0)
23190 qmail-lspawn RET   sigprocmask 0
23190 qmail-lspawn CALL  select(0x4,0xbfbffd00,0,0,0)
23190 qmail-lspawn RET   select 1
23190 qmail-lspawn CALL  sigprocmask(0x1,0xbfbffca0,0)
23190 qmail-lspawn RET   sigprocmask 0
23190 qmail-lspawn CALL  read(0x3,0x804d520,0x80)
23190 qmail-lspawn GIO   fd 3 read 0 bytes
  
23190 qmail-lspawn RET   read 0
23190 qmail-lspawn CALL  write(0x1,0x804d9c0,0xe)
23190 qmail-lspawn GIO   fd 1 wrote 14 bytes
  \0\0Kdid 0+0+1
   \0
23190 qmail-lspawn RET   write 14/0xe
23190 qmail-lspawn CALL  close(0x3)
23190 qmail-lspawn RET   close 0
23190 qmail-lspawn CALL  sigprocmask(0x2,0xbfbffca0,0)
23190 qmail-lspawn RET   sigprocmask 0
23190 qmail-lspawn CALL  select(0x1,0xbfbffd00,0,0,0)
23190 qmail-lspawn PSIG  SIGHUP SIG_DFL
qmail-rspawn ktrace output:
23191 qmail-rspawn CALL  read(0x3,0x804c720,0x80)
23191 qmail-rspawn GIO   fd 3 read 67 bytes
  r\0K67.28.113.10 accepted message.
   Remote host said: 250 ok dirdel
   \000
23191 qmail-rspawn RET   read 67/0x43
23191 qmail-rspawn CALL  sigprocmask(0x2,0xbfbffcb0,0)
23191 qmail-rspawn RET   sigprocmask 0
23191 qmail-rspawn CALL  select(0x4,0xbfbffd10,0,0,0)
23191 qmail-rspawn PSIG  SIGCHLD caught handler=0x8048c20 mask=0x0
code=0x0
23191 qmail-rspawn RET   select -1 errno 4 Interrupted system call
23191 qmail-rspawn CALL  wait4(0x,0xbfbffb20,0x1,0)
23191 qmail-rspawn RET   wait4 46703/0xb66f
23191 qmail-rspawn CALL  close(0x4)
23191 qmail-rspawn RET   close 0
23191 qmail-rspawn CALL  wait4(0x,0xbfbffb20,0x1,0)
23191 qmail-rspawn RET   wait4 -1 errno 10 No child processes
23191 qmail-rspawn CALL  sigreturn(0xbfbffb40)
23191 qmail-rspawn RET   sigreturn JUSTRETURN
23191 qmail-rspawn CALL  sigprocmask(0x1,0xbfbffcb0,0)
23191 qmail-rspawn RET   sigprocmask 0
23191 qmail-rspawn CALL  sigprocmask(0x2,0xbfbffcb0,0)
23191 qmail-rspawn RET   sigprocmask 0
23191 qmail-rspawn CALL  select(0x4,0xbfbffd10,0,0,0)
23191 qmail-rspawn RET   select 1
23191 qmail-rspawn CALL  sigprocmask(0x1,0xbfbffcb0,0)
23191 qmail-rspawn RET   sigprocmask 0
23191 qmail-rspawn CALL  read(0x3,0x804c720,0x80)
23191 qmail-rspawn GIO   fd 3 read 0 bytes
  
23191 qmail-rspawn RET   read 0
23191 qmail-rspawn CALL  write(0x1,0x804cbc0,0x43)
23191 qmail-rspawn GIO   fd 1 wrote 67 bytes
  \0\0K67.28.113.10 accepted message.
   Remote host said: 250 ok dirdel
   \000
23191 qmail-rspawn RET   write 67/0x43
23191 qmail-rspawn CALL  close(0x3)
23191 qmail-rspawn RET   close 0
23191 qmail-rspawn CALL  sigprocmask(0x2,0xbfbffcb0,0)
23191 qmail-rspawn RET   sigprocmask 0
23191 qmail-rspawn CALL  select(0x1,0xbfbffd10,0,0,0)
23191 qmail-rspawn RET   select 1
23191 qmail-rspawn CALL  sigprocmask(0x1,0xbfbffcb0,0)
23191 qmail-rspawn RET   sigprocmask 0
23191 qmail-rspawn CALL  read(0,0x804c7a0,0x400)
23191 qmail-rspawn GIO   fd 0 read 0 bytes
  
23191 qmail-rspawn RET   read 0
23191 qmail-rspawn CALL  exit(0)
- Original Message - 
From: Tabor Kelly [EMAIL PROTECTED]
To: Mike Grissom [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, December 13, 2004 9:55 PM
Subject: Re: Qmail Problems


Mike Grissom wrote:
I have been having a problem with qmail-send dying for a while now. 
In the log file
 it says that alert: oh no! lost spawn connection which leads me

Qmail Problems

2004-12-12 Thread Mike Grissom
I have been having a problem with qmail-send dying for a while now.  In the log 
file it says that alert: oh no! lost spawn connection which leads me to 
believe the problem is with the qmail-lspawn or qmail-rspawn.  I have FreeBSD 
4.10-STABLE #0: Thu Nov 11 17:21:04 EST 2004 installed on the box.  Any ideas 
what could be causing this?  Or how to fix this problem?No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.296 / Virus Database: 265.5.0 - Release Date: 12/9/2004
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]