Re: Postfix using all CPU after nightly mail submission

2018-02-21 Thread Wietse Venema
Zach Sheppard: > I did as you suggested and opened a console on the VMWare host, did a tail > of the mail log, and it sent mail for a good 5-10 minutes before finally > becoming unresponsive. I tried to Ctrl-C out of tail, nothing. I've done Thanks for confirming that the ENTIRE SYSTEM LOCKS UP. E

Re: Postfix using all CPU after nightly mail submission

2018-02-21 Thread MK
Was seeing similar behaviour under high tcp load in other applications (unrelated to postfix). It’s possible you’re running into this bug. Try to Set vmxnet3.rev.30=FALSE under the VMs properties and reboot More info here:191201 – Randomly freezes due to VMXNET3  | | | 191201 – Randomly

RE: Postfix using all CPU after nightly mail submission

2018-02-21 Thread Fazzina, Angelo
, Server Systems 860-486-9075 From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org] On Behalf Of Zach Sheppard Sent: Wednesday, February 21, 2018 8:31 AM To: Postfix users Subject: Re: Postfix using all CPU after nightly mail submission Hi Wietse, I limited my postfix

Re: Postfix using all CPU after nightly mail submission

2018-02-21 Thread Zach Sheppard
Hi Wietse, I limited my postfix installation to default_process_limit 5, 4, 3, 2, and even 1, and still saw the same effects. I am thinking it might be either my opendkim milter (which applies the DKIM signature for each mail) or SASL as these are the only other processes on the server. Are you aw

Re: Postfix using all CPU after nightly mail submission

2018-01-20 Thread Zach Sheppard
Hi Viktor: I configured that internally generated mail to be filtered through our DKIM milter. This was to allow deliveries of error messages from the server to my inbox. However, I see above how this is not ideal since that can just be delivered to the root user inbox. I have turned off that sett

Re: Postfix using all CPU after nightly mail submission

2018-01-20 Thread Ralf Hildebrandt
> > Jan 15 00:42:42 mailrelay postfix/qmgr[5601]: 8EF0980973: > > from=, size=2408, nrcpt=1 (queue > > active)^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^

Re: Postfix using all CPU after nightly mail submission

2018-01-19 Thread Wietse Venema
Zach Sheppard: > Wietse: > > I have not made any changes to rsyslog.conf. All it does it redirect all > mail log messages to one log in /var/log/mail which I rotate with a cron > script nightly. However, I do agree that it really could be the only other > process that could be hanging the server.

Re: Postfix using all CPU after nightly mail submission

2018-01-19 Thread Viktor Dukhovni
On Fri, Jan 19, 2018 at 02:04:05PM -0500, Zach Sheppard wrote: > I have not made any changes to rsyslog.conf. All it does it redirect all > mail log messages to one log in /var/log/mail which I rotate with a cron > script nightly. However, I do agree that it really could be the only other > proces

Re: Postfix using all CPU after nightly mail submission

2018-01-19 Thread Zach Sheppard
Wietse: I have not made any changes to rsyslog.conf. All it does it redirect all mail log messages to one log in /var/log/mail which I rotate with a cron script nightly. However, I do agree that it really could be the only other process that could be hanging the server. I'm not able to determine

Re: Postfix using all CPU after nightly mail submission

2018-01-19 Thread Wietse Venema
Zach Sheppard: > However, whenever Postfix gets a large e-mail load it processes the e-mails > for around 30-45 minutes and then consistently uses around 70-80% of the > CPU effectively locking up the entire system so much so that I can't even > login and debug without either disabling the network

Re: Postfix using all CPU after nightly mail submission

2018-01-19 Thread Dominic Raferd
On 19 January 2018 at 16:02, Viktor Dukhovni wrote: > > >> On Jan 19, 2018, at 10:58 AM, Dominic Raferd wrote: >> >>> The pipes to "sort" should not be needed. The output of "postconf" is >>> pre-sorted. >> >> yes I thought that - but without piping through sort I see: >> $ comm -1 -2 <(postcon

Re: Postfix using all CPU after nightly mail submission

2018-01-19 Thread Viktor Dukhovni
> On Jan 19, 2018, at 10:58 AM, Dominic Raferd wrote: > >> The pipes to "sort" should not be needed. The output of "postconf" is >> pre-sorted. > > yes I thought that - but without piping through sort I see: > $ comm -1 -2 <(postconf -n) <(postconf -d) > comm: file 2 is not in sorted order >

Re: Postfix using all CPU after nightly mail submission

2018-01-19 Thread Dominic Raferd
On 19 January 2018 at 15:55, Viktor Dukhovni wrote: > > >> On Jan 19, 2018, at 10:46 AM, Dominic Raferd wrote: >> >> Here's a way to check for explicit settings in main.cf that are >> actually defaults and so could be removed (works under bash): >> >> comm -1 -2 <(postconf -n|sort) <(postconf -d|

Re: Postfix using all CPU after nightly mail submission

2018-01-19 Thread Viktor Dukhovni
> On Jan 19, 2018, at 10:46 AM, Dominic Raferd wrote: > > Here's a way to check for explicit settings in main.cf that are > actually defaults and so could be removed (works under bash): > > comm -1 -2 <(postconf -n|sort) <(postconf -d|sort) The pipes to "sort" should not be needed. The outpu

Re: Postfix using all CPU after nightly mail submission

2018-01-19 Thread Dominic Raferd
On 19 January 2018 at 15:21, Viktor Dukhovni wrote: > > > > > default_destination_concurrency_limit = 50 > > This is the default, remove the setting. > > ... Here's a way to check for explicit settings in main.cf that are actually defaults and so could be removed (works under bash): comm -1 -2

Re: Postfix using all CPU after nightly mail submission

2018-01-19 Thread Viktor Dukhovni
> On Jan 19, 2018, at 9:55 AM, Zach Sheppard > wrote: > > bounce_queue_lifetime = 0 This is a bad idea. Don't do that. Allow transient delivery failures to be retried. > default_destination_concurrency_limit = 50 This is the default, remove the setting. > internal_mail_filter_classes = b

Re: Postfix using all CPU after nightly mail submission

2018-01-19 Thread Viktor Dukhovni
> On Jan 19, 2018, at 8:52 AM, Zach Sheppard > wrote: > > Jan 15 00:42:42 mailrelay postfix/qmgr[5601]: 8EF0980973: > from=, size=2408, nrcpt=1 (queue > active)^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

Re: Postfix using all CPU after nightly mail submission

2018-01-19 Thread Zach Sheppard
Hi Bastian, I did read that debug readme and saw the following: >> If you can't use a test email address, please anonymize email addresses and host names consistently. Replace each letter by "A", each digit by "D" so that the helpers can still recognize syntactical errors. ...and is why I replac

Re: Postfix using all CPU after nightly mail submission

2018-01-19 Thread Bret Busby
On Fri, 19 Jan 2018, Bastian Blank wrote: Date: Fri, 19 Jan 2018 22:06:15 From: Bastian Blank To: postfix-users@postfix.org Subject: Re: Postfix using all CPU after nightly mail submission On Fri, Jan 19, 2018 at 08:52:39AM -0500, Zach Sheppard wrote: I see no errors or alarms in the mail

Re: Postfix using all CPU after nightly mail submission

2018-01-19 Thread Bastian Blank
On Fri, Jan 19, 2018 at 08:52:39AM -0500, Zach Sheppard wrote: > I see no errors or alarms in the mail log nor syslog. The only odd message > I see is a series of ^@ symbols before the system freezes: Please read http://www.postfix.org/DEBUG_README.html#mail about how to report problems. > Jan 15

Postfix using all CPU after nightly mail submission

2018-01-19 Thread Zach Sheppard
Hello, We use a Postfix installation on Debian 9 in our network to serve as a send-only SMTP server for a very large application in our school district. This application does not have its own built-in SMTP server and requires a relay to send notification e-mails to students, teachers, and parents