From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Status: No, score=-3.2 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com [IPv6:2607:f8b0:4864:20::d2d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 707891F4B7 for ; Mon, 9 Sep 2019 10:05:07 +0000 (UTC) Received: by mail-io1-xd2d.google.com with SMTP id k13so12023838ioj.1 for ; Mon, 09 Sep 2019 03:05:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=h5sZji4+nMeHpvX+yOPsLywuKYi30tb1FdQEmh4ZckI=; b=EYB7ajrUxfkxdeS41yKQAMBXB2FbNin3gVKfMleqF+QGh17lEENX/zpg/mal40G2Nm 6rFUPomKm4XHO+Pbd712JLLFIaCpiL+Ht1M7ERnIxEz/HZ7LltSpusNnu6+1vgaWmXGT 7zviMqYLHs8bF+0qNlTejAF8GwmsWZSBKeerg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=h5sZji4+nMeHpvX+yOPsLywuKYi30tb1FdQEmh4ZckI=; b=lXipwr9/APwUsHOllbnKwecXi5Jjl6+OygJZfXlJMV3ODSI6YxHR4/5vLkIImuD7we 2tGxSPGxrhwoiJFrsWTKiMBw1Zjf5Dder8fMrveIdrN8akKuvur/raY72Hm3t9mz//06 7CihVUjpDroKiTB9J7lCoCdNX0zYgG7DpDYm/a3SR3IEigzKDWa73nGo/AX/ifUYc7qu 1VZsueyISC/JZMv25FHWpUILHPhA9miT7ttQ+M02AZjjFGSR61ksu+ibcGOXHp/YatrF ATKrBB2sc4fy8NpiPOJOxAVGB5Lb47RV72XhKxDj4W+gUWxhDBo9dJqv2bsJYwRqwlZ7 545A== X-Gm-Message-State: APjAAAW4NhlZ7wTutvL4vsKQe33zr3tSh+p0PHqQwOOIvYXtd96dfhJ6 jOBi4u73b7ExwRvi58yerubTtQ== X-Google-Smtp-Source: APXvYqzhJ0kta1CKOynKGrmPC42PDBotdXRSHtVeckWBKPtkzO7raa/TS1L7K4PbiwwA0dATSTPQnA== X-Received: by 2002:a5d:9c46:: with SMTP id 6mr17335586iof.261.1568023506397; Mon, 09 Sep 2019 03:05:06 -0700 (PDT) Received: from pure.paranoia.local ([87.101.92.157]) by smtp.gmail.com with ESMTPSA id a21sm9880249ioe.27.2019.09.09.03.05.04 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 09 Sep 2019 03:05:05 -0700 (PDT) Date: Mon, 9 Sep 2019 06:05:00 -0400 From: Konstantin Ryabitsev To: Eric Wong Cc: meta@public-inbox.org Subject: Re: trying to figure out 100% CPU usage in nntpd... Message-ID: <20190909100500.GA9452@pure.paranoia.local> Mail-Followup-To: Eric Wong , meta@public-inbox.org References: <20190908104518.11919-1-e@80x24.org> <20190908105243.GA15983@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190908105243.GA15983@dcvr> User-Agent: Mutt/1.12.1 (2019-06-15) List-Id: On Sun, Sep 08, 2019 at 10:52:43AM +0000, Eric Wong wrote: > I've been having trouble reproducing this bug (but maybe summer > weather has been taking its toll, certainly has on my HW). I did notice the same thing after updating to what was the latest master last week -- the nntpd process was always 100% or above load in htop. I just applied the latest updates, so we'll see if there is any change. There also was a weird problem a couple of days ago where one of the httpd daemons started returning "Internal Server Error" to all requests. Restarting public-inbox-httpd fixed the problem, but I am not sure how I would troubleshoot the causes if it happens next time -- is there a way to enable error logging for the httpd daemon? -K