From owner-freebsd-current@freebsd.org Thu Apr 20 09:31:52 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 93A24D47A09; Thu, 20 Apr 2017 09:31:52 +0000 (UTC) (envelope-from tvijlbrief@gmail.com) Received: from mail-yw0-x232.google.com (mail-yw0-x232.google.com [IPv6:2607:f8b0:4002:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F9D773; Thu, 20 Apr 2017 09:31:52 +0000 (UTC) (envelope-from tvijlbrief@gmail.com) Received: by mail-yw0-x232.google.com with SMTP id u70so35947254ywe.2; Thu, 20 Apr 2017 02:31:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ZnevUaJhp8o+62+JbDvqcEAzUqPJMpxIZKO2zCCXoLY=; b=jLkzL0Yi+mubmGgdD2rrZt3aaaGl8f9i7tyDtiuu2WxJRuZs5vG9hkc93senxFb1f/ roCkoRwI5nUgyn1DpFAvRzDld07TXDME2n/u+muDVemaom4UbIofuPi1Ellt4qoP0+/P UdJ/qAFwGEiARIjLGrRFI/a5qULC+Y717D139bSz7glcyIdT6dwFmYnk6Ih7Zsh/TXv6 cAFbCUqnw60YwbFW/9+PTsOpjga/HEtelKiAtvQogGVWzAMI9QyHRv/j811Fz8OcebzY MF2vfEHgqhK+6YJAipLj5nm1fa4gMsuFj2ZVewZk5F5iOsgWFbmlEsaxTW/ELz5ki8YY DtuA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ZnevUaJhp8o+62+JbDvqcEAzUqPJMpxIZKO2zCCXoLY=; b=AuwbttPqHsDAORNogVk8Ivfl0dJ69630UykdHnZSTy3qdFElPsoP+ELKguaq0CNgGO HCMAZcGSgUcxYMEH9pdU94Q3pOloL9YyWpj7R8adoyKaQR70BjkYgrefBILhJUL1l/nt ZUCdDRlqaqGmV+LmDgzDb4lBwmvzGJ40B1ZBFx81IagCXLoGwaHcb/FSBIYdxpdUjydq tPg5rqXaZApk5b4p878hQJ+CGsTvv8btGpIp+twXDSS4MXg0F1haAInwtABJS4i2BZ9Z lTv4fO8nTafGvLmMoSk+mQrivDUKfrjKLZCDFht3x0kaJKEtsET6NNrCHpi40j/ehYRn hbuA== X-Gm-Message-State: AN3rC/4XnQla0TzHsBeXP2BHap7k5nCbopdoVtAA3xY/5XYf50G0SsOS ylj3P/rcWzs19ZnXjpNzrZCbSV9fd0Hk X-Received: by 10.13.249.130 with SMTP id j124mr5707553ywf.198.1492680711379; Thu, 20 Apr 2017 02:31:51 -0700 (PDT) MIME-Version: 1.0 References: <91A4570B-69EE-4462-9C60-205C66267599@dsl-only.net> <7AD329E1-2828-42EB-9A14-B44E357CC199@dsl-only.net> In-Reply-To: From: Tom Vijlbrief Date: Thu, 20 Apr 2017 09:31:40 +0000 Message-ID: Subject: Re: Sendmail eats CPU on r317039 [after -r316874 it may be -r316951 and -r316973 are not enough to fix everything] To: Mark Millard , ronald-lists@klop.ws Cc: FreeBSD Current , freebsd-arm , sobomax@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 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: Thu, 20 Apr 2017 09:31:52 -0000 Op wo 19 apr. 2017 09:11 schreef Tom Vijlbrief : > I'm currently rebuilding world and kernel on a just completed SVN checkout. > > Note that the normal sendmail daemon which listens for incoming traffic > does NOT loop. > > The sendmail instance which tries local delivery (echo Hi | mail root) or > the msp_queue instance is looping. > > It might be an arm64 specific issue, but a few weeks ago this was not an > issue. > I just completed a full rebuild on the Pine64 and I cannot reproduce the problem, so there is probably no issue anymore... (Except the spurious interrupts issue) > Op di 18 apr. 2017 om 21:15 schreef Mark Millard : > >> 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 >> > syslog-clients (like sendmail busy-looping on logging. >> > That might be related to this. (it is fixed in the source already, so >> > upgrading again might help) >> > See the thread with subject like 'Re: r316958: booting a server takes >> >10 >> > minutes!' >> > >> > Regards, >> > >> > 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: >> > >> >> Just an FYI of a more recent report of runaway sendmail on a >> >> more recent system version ( -r317039 ): >> >> >> >> Begin forwarded message: >> >> >> >>> 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 >> >>> >> >>> On a recent kernel sendmail is constantly consuming CPU. >> >>> >> >>> truss -p PID >> >>> >> >>> shows: >> >>> >> >>> sendto(3,"<22>Apr 17 10:30:33 sendmail[362"...,163,0x0,NULL,0) ERR#55 >> 'No >> >>> buffer space available' >> >>> nanosleep({ 0.000001000 }) = 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 }) >> >>> ... >> >>> >> >>> This is on an arm64 system >> >> >> >> Analysis of Tom V.'s context for this may be required. >> >> === >> Mark Millard >> markmi at dsl-only.net >> >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >> >