|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: 451 Error: queue file write error
Subject: Re: 451 Error: queue file write error
From: Lutz Jaenicke (Lutz.Jaenicke
aet.TU-Cottbus.DE)
Date: Sat Jan 08 2000 - 12:53:35 CST
- Next message: furio ercolessi: "Re: 451 Error: queue file write error"
- Previous message: winfried szukalski: "Re: 451 Error: queue file write error"
- In reply to: winfried szukalski: "Re: 451 Error: queue file write error"
- Next in thread: furio ercolessi: "Re: 451 Error: queue file write error"
- Reply: Lutz Jaenicke: "Re: 451 Error: queue file write error"
- Reply: furio ercolessi: "Re: 451 Error: queue file write error"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, Jan 08, 2000 at 07:02:03PM +0100, winfried szukalski wrote:
> /var/log/mail:
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Jan 8 18:49:09 keun postfix-script:
> starting the Postfix mail system
> Jan 8 18:49:09 keun postfix/master[23244]:
> daemon started
> Jan 8 18:53:29 keun postfix/pickup[23245]: 23BCD3AC80:
> uid=0 from=<szukw000
mail.uni-mainz.de>
> Jan 8 18:53:29 keun postfix/pickup[23245]:
> warning: mail_scan_any: got EOF; expected: integer
> Jan 8 18:53:29 keun postfix/pickup[23245]:
> warning: maildrop/0BA7A3AC7E: Error writing message file
> Jan 8 18:53:29 keun postfix/master[23244]:
> warning: process /usr/lib/postfix/cleanup pid 23255 killed by signal 11
> Jan 8 18:53:29 keun postfix/master[23244]:
> warning: /usr/lib/postfix/cleanup: bad command startup -- throttling
Hi!
signal 11 is defined in /usr/include/signal.h (or some header file included
from there, on my SuSE Linux it is found in /usr/include/asm/signal.h)
#define SIGSEGV 11
(Even though the numbers should be quite similar between UNIX variants.
So it seems, cleanup experienced a segmentation violation. Normally,
there should now be a core dump in /var/spool/postfix, that can be
analyzed with your preferred debugger.
If you don't have a core dump, you might have to set some ulimit value
I don't remember, typically, the (non-understandable) Linux-default for
the max coredump size is 0.
Once you have a core dump, you will easily find the reason for the segmentation
fault... And we would like to hear of it eventually.
Best regards,
Lutz
-- Lutz Jaenicke Lutz.Jaenickeaet.TU-Cottbus.DE BTU Cottbus http://www.aet.TU-Cottbus.DE/personen/jaenicke/ Lehrstuhl Allgemeine Elektrotechnik Tel. +49 355 69-4129 Universitaetsplatz 3-4, D-03044 Cottbus Fax. +49 355 69-4153
- Next message: furio ercolessi: "Re: 451 Error: queue file write error"
- Previous message: winfried szukalski: "Re: 451 Error: queue file write error"
- In reply to: winfried szukalski: "Re: 451 Error: queue file write error"
- Next in thread: furio ercolessi: "Re: 451 Error: queue file write error"
- Reply: Lutz Jaenicke: "Re: 451 Error: queue file write error"
- Reply: furio ercolessi: "Re: 451 Error: queue file write error"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
This archive was generated by hypermail 2b27 : Sat Jan 08 2000 - 12:55:28 CST