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
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 ma
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
much!
--
View this message in context:
http://postfix.1071664.n5.nabble.com/Postfix-crashes-with-signal-11-tp65224p65250.html
Sent from the Postfix Users mailing list archive at Nabble.com.
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
1071664.n5.nabble.com/Postfix-crashes-with-signal-11-tp65224p65247.html
Sent from the Postfix Users mailing list archive at Nabble.com.
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
On Sat, Feb 15, 2014 at 10:10:25AM -0800, SW wrote:
> I have removed the -D flag and restarted Postfix. I will keep my eye on it
> and report back.
>
> I'm really hoping for an email to come from Ebay and/or Facebook as that
> always caused a signal 11. I'd like to see if removing zlib resolved
delay.
--
View this message in context:
http://postfix.1071664.n5.nabble.com/Postfix-crashes-with-signal-11-tp65224p65240.html
Sent from the Postfix Users mailing list archive at Nabble.com.
On Sat, Feb 15, 2014 at 10:04:09AM -0800, SW wrote:
> Apologies, this was logged under 27935 as well:
>
> postfix/smtpd[27935]: connect from m12-184.163.com[220.181.12.184]
> postfix/smtpd[27935]: NOQUEUE: reject: RCPT from
> m12-184.163.com[220.181.12.184]: 554 5.7.1 Service unavailable; Client h
e one more issue I could use some help with but I will start another
thread for that one!
--
View this message in context:
http://postfix.1071664.n5.nabble.com/Postfix-crashes-with-signal-11-tp65224p65238.html
Sent from the Postfix Users mailing list archive at Nabble.com.
On Sat, Feb 15, 2014 at 09:56:18AM -0800, SW wrote:
> I had a look through the entire maillog for 27935 but all I could see was:
>
> running: PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont; echo
> where; sleep 864) | gdb /usr/local/libexec/postfix/smtpd 27935
> 2>&1 >/us
;
http://www.barracudanetworks.com/reputation/?pr=1&ip=220.181.12.184;
from= to= proto=ESMTP
helo=http://postfix.1071664.n5.nabble.com/Postfix-crashes-with-signal-11-tp65224p65236.html
Sent from the Postfix Users mailing list archive at Nabble.com.
I'm not sure what makes this server quirky but to move forward should I
remove the debugging? Is this what is causing Postfix to stop now?
--
View this message in context:
http://postfix.1071664.n5.nabble.com/Postfix-crashes-with-signal-11-tp65224p65235.html
Sent from the Postfix Users mail
On Sat, Feb 15, 2014 at 09:28:34AM -0800, SW wrote:
> So I removed zlib from OpenSSL and things seemed to be going well until this
> happened:
>
> Feb 15 17:22:20 mail postfix/master[1555]: panic: master_reap: unknown pid:
> 27935
And you did not look earlier in the log to see what process 27935
On Sat, Feb 15, 2014 at 07:02:01AM -0800, SW wrote:
> Apologies for posting the incorrect info previously.
>
> Postfix has just crashed again and this is what is in the logfile:
http://archives.neohapsis.com/archives/postfix/2013-10/thread.html#434
> Program received signal SIGSEGV, Segmentation
single_server_wakeup ()
#16 0x0041b7db in single_server_accept_pass ()
#17 0x0044298a in event_loop ()
#18 0x0041b47d in single_server_main ()
#19 0x00407304 in main ()
--
View this message in context:
http://postfix.1071664.n5.nabble.com/Postfix-crashes-with
SW:
> Loaded symbols for /libexec/ld-elf.so.1
> [Switching to Thread 803406400 (LWP 101354/smtpd)]
> 0x000802027dd8 in wait4 () from /lib/libc.so.7
> (gdb) Continuing.
>
> Program exited normally.
> (gdb) (gdb)
This is the result of normal execution. Please do not send these
again.
Please re
SW:
> Hi Wietse, many thanks for the reply.
>
> egrep '(warning|error|fatal|panic):' /var/log/postfix/maillog | more gives:
>
> Feb 15 05:13:57 mail postfix/master[88477]: warning: process
> /usr/local/libexec/postfix/smtpd pid 40297 killed by signal 11
> Feb 15 05:13:57 mail postfix/master[88477
o Thread 803406400 (LWP 101354/smtpd)]
0x000802027dd8 in wait4 () from /lib/libc.so.7
(gdb) Continuing.
Program exited normally.
(gdb) (gdb)
--
View this message in context:
http://postfix.1071664.n5.nabble.com/Postfix-crashes-with-signal-11-tp65224p65227.html
Sent from the Postfix
mp; sleep 5
and changed master.cf to:
smtpd pass - - n - - smtpd -D
and restarted Postfix.
Do I just wait now until Postfix crashes again? Where is the crash log
stored?
--
View this message in context:
http://postfix.1071664.n5.nabble.com/Postfi
SW:
> Can someone assist me with troubleshooting this further please? I have been
> through the logs but I can't find any clue as to why this is happening.
>
> I'd be happy to answer any questions about my main.cf or master.cf file.
What other warnings does Postfix log?
http://www.postfix.org/DEB
e.
Thank you!
--
View this message in context:
http://postfix.1071664.n5.nabble.com/Postfix-crashes-with-signal-11-tp65224.html
Sent from the Postfix Users mailing list archive at Nabble.com.
29 matches
Mail list logo
