From owner-freebsd-current@freebsd.org Tue Apr 18 19:35:06 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 01450D429D8 for ; Tue, 18 Apr 2017 19:35:06 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-89.reflexion.net [208.70.210.89]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A8B8F13BC for ; Tue, 18 Apr 2017 19:35:05 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 18505 invoked from network); 18 Apr 2017 19:08:24 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 18 Apr 2017 19:08:24 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Tue, 18 Apr 2017 15:08:24 -0400 (EDT) Received: (qmail 20130 invoked from network); 18 Apr 2017 19:08:24 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 18 Apr 2017 19:08:24 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id ED3B3EC8AB1; Tue, 18 Apr 2017 12:08:23 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Sendmail eats CPU on r317039 [after -r316874 it may be -r316951 and -r316973 are not enough to fix everything] From: Mark Millard In-Reply-To: <91A4570B-69EE-4462-9C60-205C66267599@dsl-only.net> Date: Tue, 18 Apr 2017 12:08:23 -0700 Cc: sobomax@FreeBSD.org, hrs@FreeBSD.org, freebsd-arm , FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: <7AD329E1-2828-42EB-9A14-B44E357CC199@dsl-only.net> References: <91A4570B-69EE-4462-9C60-205C66267599@dsl-only.net> To: ronald-lists@klop.ws X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2017 19:35:06 -0000 Ronald Klop ronald-lists at klop.ws wrote on Tue Apr 18 09:59:50 UTC = 2017: > there is a thread ono this list about a problem in syslogd which made =20= > syslog-clients (like sendmail busy-looping on logging. > That might be related to this. (it is fixed in the source already, so =20= > upgrading again might help) > See the thread with subject like 'Re: r316958: booting a server takes = >10 =20 > minutes!' >=20 > Regards, >=20 > Ronald. Yes. But Tom V.'s report is for -r317039, which is after the reported fixes as far as I can tell. Something besides syslogd might also cause problems? In my nearly-default -r317015 ardm64 context [as a VirtualBox guest] I've not seen the problem, where I did before. (The only reason sendmail runs in my context is for the messages FreeBSD sends to it own local accounts. I do not otherwise use mail in this context.) Tom V.'s report vs. others finding lack of a problem suggests that the coverage of the fixes is incomplete somehow but useful. I happen to not be doing whatever causes the problem to appear. I've no clue what might be different or unusual in Tom V.'s context. There is also the possibility that Tom V.'s report is a fully = independent issue. But such does not seem all that likely on the initial = information. > On 2017-Apr-17, at 7:57 AM, Mark Millard = wrote: >=20 >> Just an FYI of a more recent report of runaway sendmail on a >> more recent system version ( -r317039 ): >>=20 >> Begin forwarded message: >>=20 >>> From: Tom Vijlbrief >>> Subject: Sendmail eats CPU on r317039 >>> Date: April 17, 2017 at 3:39:37 AM PDT >>> To: "freebsd-current at freebsd.org" , freebsd-arm >>>=20 >>> On a recent kernel sendmail is constantly consuming CPU. >>>=20 >>> truss -p PID >>>=20 >>> shows: >>>=20 >>> sendto(3,"<22>Apr 17 10:30:33 sendmail[362"...,163,0x0,NULL,0) = ERR#55 'No >>> buffer space available' >>> nanosleep({ 0.000001000 }) =3D 0 (0x0) >>> sendto(3,"<22>Apr 17 10:30:33 sendmail[362"...,163,0x0,NULL,0) = ERR#55 'No >>> buffer space available' >>> nanosleep({ 0.000001000 }) >>> ... >>>=20 >>> This is on an arm64 system >>=20 >> Analysis of Tom V.'s context for this may be required. =3D=3D=3D Mark Millard markmi at dsl-only.net