|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Subject: Re: cleanup die with long recipient address (?)
From: Wietse Venema (wietse
porcupine.org)Date: Thu Sep 14 2000 - 07:58:07 CDT
- Next message: Wietse Venema: "Re: TODO: ignore sender: header when different from envelope?"
- Previous message: adi: "cleanup die with long recipient address (?)"
- In reply to: adi: "cleanup die with long recipient address (?)"
- Next in thread: Ralf Hildebrandt: "Re: cleanup die with long recipient address (?)"
- Reply: Wietse Venema: "Re: cleanup die with long recipient address (?)"
- Reply: Ralf Hildebrandt: "Re: cleanup die with long recipient address (?)"
- Reply: adi: "Re: cleanup die with long recipient address (?)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> Sep 13 15:33:14 mail postfix/cleanup[30953]: panic: myfree:
> corrupt or unallocated memory block
This means that the contents of memory changed by itself, or that
something stomped over it. I do a fair amount of testing and code
reviewing to ensure that Postfix does not stomp over its own memory
- witness the low incidence of memory-related problems reported on
this list.
So I ask my usual questions:
1) Does the machine have ECC memory error handling?
2) Does the machine have Parity memory error handling?
3) Is memory error actually detection enabled?
4) Does the problem reproduce on a different machine?
If all these questions makes no sense, see the signal 11 FAQ
at http://www.bitwizard.nl/sig11/
Wietse
adi:
> Hi Folks!
>
> I have two machines, one running postfix (as primary mx):
> mail.satunet.com and one runnung qmail (for our newsletter):
> mailhub.satunet.com.
>
> Both of them are using the same domain as $mydestination, i.e
>
> mydestination = satunet.com
>
> Because the postfix machine is the primary mx for the domain, and
> newsletter is handled on qmail machine, then postfix machine should
> be able to received any bounce message which is, of course, using
> VERP (newsletter on the qmail machine, mailhub.satunet.com, is
> handled by ezmlm).
>
> I've setup aliases just like this:
>
> /etc/postfix/aliases:
> newsletter: newsletter
mailhub.satunet.com
>
> /etc/postfix/virtual_maps:
> newsletter
satunet.com newsletter
mailhub.satunet.com
>
> /etc/postfix/main.cf:
> local_recipients_maps = $aliases_maps, unix:passwd.byname
>
> When postfix received bounce message with recipient address like
> this:
>
> --------
> newsletter-return-warn-968832480.cnfialeoiidpjogbooln-xxx=ddddddddddd.ddddddddddddd.dd
satunet.com
> --------
>
> (Of course this one should be delivered on mailhub.satunet.com, i.e qmail
> machine).
>
> Sometimes, it could make cleanup daemon exit with signal 11:
>
> ----
> Sep 13 15:26:43 mail postfix/master[2807]: warning: process /usr/libexec/postfix/cleanup pid 30767 killed by signal 11
> ----
>
> And sometimes, I got this in my syslog:
>
> Sep 13 15:33:14 mail postfix/cleanup[30953]: panic: myfree: corrupt or unallocated memory block
> Sep 13 15:33:15 mail postfix/master[2807]: warning: process /usr/libexec/postfix/cleanup pid 30953 killed by signal 6
>
>
> Hope that anyone would give me the light :-)
> Better alternate approach to facing this problem (if any) would be greatly
> appreciated.
>
> Thanks.
>
> Salam,
>
> P.Y. Adi Prasaja
>
> PS. I'm using latest snapshot.
>
>
>
>
- Next message: Wietse Venema: "Re: TODO: ignore sender: header when different from envelope?"
- Previous message: adi: "cleanup die with long recipient address (?)"
- In reply to: adi: "cleanup die with long recipient address (?)"
- Next in thread: Ralf Hildebrandt: "Re: cleanup die with long recipient address (?)"
- Reply: Wietse Venema: "Re: cleanup die with long recipient address (?)"
- Reply: Ralf Hildebrandt: "Re: cleanup die with long recipient address (?)"
- Reply: adi: "Re: cleanup die with long recipient address (?)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]