SW:
> I've been running for 16 hours now with no crash. I have successfully
> received emails from Facebook and Postfix hasn't given a signal 11 so its
> looking good so far!
This looks like the same problem that Viktor referred to yesterday.
Same symptom (crash in zlib+openssl), same resolution.
I've been running for 16 hours now with no crash. I have successfully
received emails from Facebook and Postfix hasn't given a signal 11 so its
looking good so far!
--
View this message in context:
http://postfix.1071664.n5.nabble.com/Postfix-crashes-with-signal-11-tp65224p65280.html
Sent from
I understand. It was more an FYI.
--
View this message in context:
http://postfix.1071664.n5.nabble.com/Postfix-crashes-with-signal-11-tp65224p65265.html
Sent from the Postfix Users mailing list archive at Nabble.com.
SW:
> I should mention that I am running STABLE:
>
> FreeBSD 10.0-STABLE #0 r260985 (GENERIC kernel).
>
> I'm running it on a 4 core Xeon E31230V3.
Your problem was with zlib/openssl, and you have a solution for that.
The -D option is for trouble shooting. You never use it for normal
Postfix op
I should mention that I am running STABLE:
FreeBSD 10.0-STABLE #0 r260985 (GENERIC kernel).
I'm running it on a 4 core Xeon E31230V3.
--
View this message in context:
http://postfix.1071664.n5.nabble.com/Postfix-crashes-with-signal-11-tp65224p65263.html
Sent from the Postfix Users mailing lis
Wietse Venema:
> Viktor Dukhovni:
> > > If I understand correctly, some buggy kernel reports WIFSTOPPED
> > > events to the Postfix master daemon (the smtpd parent process)
> > > instead of gdb (the smtpd tracing process).
> >
> > This is a plausible guess. Somehow by the time smtpd(8) really
> >
Viktor Dukhovni:
> > If I understand correctly, some buggy kernel reports WIFSTOPPED
> > events to the Postfix master daemon (the smtpd parent process)
> > instead of gdb (the smtpd tracing process).
>
> This is a plausible guess. Somehow by the time smtpd(8) really
> exited, master(8) had alread
I've been running fine for about 3 hours since removing -D and removing zlib
from OpenSSL. I think its still too early to tell for sure if everythings
ok.
I will check the logs again tomorrow morning to see how things look.
I really appreciate both your help (Viktor and Wietse) very much!
--
On Sat, Feb 15, 2014 at 12:49:03PM -0800, SW wrote:
> FreeBSD 10-STABLE amd64. I'd be happy to assist/test if I can.
>
> Am I correct in saying that removing the -D from master.cf will prevent
> Postfix from stopping again?
Whether it does or not, you should not run with "-D" in production.
Inte
*Since your domain is DNSSEC signed, please consider deploying DANE
TLSA records for your domain: *
The company that hosts my DNS doesn't support DANE TLSA as far as I know.
*
Were there any other log entries from master(8) between
the two events?*
None that I could see.
*What OS version are you
On Sat, Feb 15, 2014 at 02:14:50PM -0500, Wietse Venema wrote:
> Viktor Dukhovni:
> > if (!NORMAL_EXIT_STATUS(status)) {
> > + /* Debugged processes may be reported to master(8) as stopped */
> > + if (WIFSTOPPED(status)) {
>
> In that case it would be prudent to log what happens:
Viktor Dukhovni:
> if (!NORMAL_EXIT_STATUS(status)) {
> + /* Debugged processes may be reported to master(8) as stopped */
> + if (WIFSTOPPED(status)) {
In that case it would be prudent to log what happens:
msg_warn("process %s pid %d stopped with signal %d",
On Sat, Feb 15, 2014 at 10:17:38AM -0800, SW wrote:
> Feb 15 17:20:40 mail postfix/smtpd[27935]:
> disconnect from m12-184.163.com[220.181.12.184]
> Feb 15 17:22:20 mail postfix/master[1555]:
> panic: master_reap: unknown pid: 27935
>
> So it looks like there was a delay of 1m40s betw
13 matches
Mail list logo
