From owner-freebsd-current@freebsd.org Wed Apr 19 07:11:23 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 EE93DD44E72; Wed, 19 Apr 2017 07:11:23 +0000 (UTC) (envelope-from tvijlbrief@gmail.com) Received: from mail-yw0-x22d.google.com (mail-yw0-x22d.google.com [IPv6:2607:f8b0:4002:c05::22d]) (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 A589C351; Wed, 19 Apr 2017 07:11:23 +0000 (UTC) (envelope-from tvijlbrief@gmail.com) Received: by mail-yw0-x22d.google.com with SMTP id k13so6670711ywk.1; Wed, 19 Apr 2017 00:11:23 -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=F7vU/zIPm/+iWyy7LV1oUJjzZ6ylvvnIIH0nuPXQy9A=; b=ADqkC2xkmRaN+/JOuGCH7NB7Op7ZktdWYHWtTb07VMbk3neU4ayybJ9v25FXwBzE90 aFoaE3PGGKTA2qZiHz7wyiHkLb0/CedWMlzyZInGKWM/McBv1li0J3WkpyCn9e6HF3xx +BHwMWZIIHb2/k5G685XzG/C5NcRkzlQE0z59JJN1WqQOA/xfNDJk71ObyGn771hATkz oup6+YSN/uUazfmzNFk5tNrRXxJMJNCm2wfLOwc1b5NNqt1n08V8JdvL1y50LzqXc3pZ cUx6736YIYFu73f+qmwloBifJholk9uzDZbQD6dpuz9EkrlX53Z6gpJR2KXO2x2wMlF8 4/8w== 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=F7vU/zIPm/+iWyy7LV1oUJjzZ6ylvvnIIH0nuPXQy9A=; b=mc5cmVMloWG9sBzUmp3YCruoaYUbe3VhCrQTvfKM2tU8fls7wSXfdxkTsw22gB+bma e73RIjHLp3jLCX+vQHqEZCUzt94KFc8CeyCKqPCj94YkwY7PPgKHU3I9u4KQ+h4c9DMj T9oyOM0y1TU/iNN3Bw4QDs6Fxf1yvTPv34mrxkqVP/4e8uCj5cH6P7anGvcMKhnDRvr5 RdsWTnM5jjJy5r84MvK4kzZGhmbPKYGwefVM7JtkCLWunxIxc0OyZpbotr2OLct6fKtO oMFft65Iz6v0+DW0b/AgncV90NNOY6IgB2soLG0AvhhNZQ8wlQ4sE9L6FlufBmS8e/RF wjAw== X-Gm-Message-State: AN3rC/4llB3CEnXvg24kQOZ9X4tF3R49ITHOejUwSZAM4OWP2m3GQY4d CsUEKbBRQUEPOdSd+VbZlqKWtJK1uUH6 X-Received: by 10.13.199.196 with SMTP id j187mr876819ywd.197.1492585882789; Wed, 19 Apr 2017 00:11:22 -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: <7AD329E1-2828-42EB-9A14-B44E357CC199@dsl-only.net> From: Tom Vijlbrief Date: Wed, 19 Apr 2017 07:11:12 +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: sobomax@freebsd.org, freebsd-arm , FreeBSD Current 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: Wed, 19 Apr 2017 07:11:24 -0000 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. 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" >