From: Konstantin Ryabitsev <email@example.com>
To: Eric Wong <firstname.lastname@example.org>
Subject: Re: trying to figure out 100% CPU usage in nntpd...
Date: Mon, 9 Sep 2019 06:05:00 -0400 [thread overview]
Message-ID: <20190909100500.GA9452@pure.paranoia.local> (raw)
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?
next prev parent reply other threads:[~2019-09-09 10:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-08 10:45 [PATCH] nntp: regexp always consumes rbuf if "\n" exists Eric Wong
2019-09-08 10:52 ` trying to figure out 100% CPU usage in nntpd Eric Wong
2019-09-09 10:05 ` Konstantin Ryabitsev [this message]
2019-09-09 17:53 ` Eric Wong
2019-09-10 8:38 ` Konstantin Ryabitsev
2019-09-10 18:12 ` Eric Wong
2019-09-11 2:22 ` httpd 502s [was: trying to figure out 100% CPU usage in nntpd...] Eric Wong
2019-09-11 10:24 ` Konstantin Ryabitsev
2019-09-11 17:12 ` Eric Wong
2019-09-11 17:36 ` Konstantin Ryabitsev
2019-09-12 0:05 ` Eric Wong
2019-09-12 2:49 ` Eric Wong
2019-09-12 8:35 ` Eric Wong
2019-09-12 11:37 ` Konstantin Ryabitsev
2019-09-13 3:12 ` Eric Wong
2019-09-13 7:03 ` Eric Wong
2019-09-13 9:01 ` Eric Wong
2019-09-13 18:07 ` Konstantin Ryabitsev
2019-09-14 5:25 ` Eric Wong
2019-09-11 9:44 ` trying to figure out 100% CPU usage in nntpd Konstantin Ryabitsev
2019-09-11 17:12 ` Eric Wong
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).