From: sl@9front.org
To: 9front@9front.org
Subject: cs/dns woesMIME-Version: 1.0
Date: Thu, 11 Apr 2013 09:52:05 -0500 [thread overview]
Message-ID: <3748dfae418a7f1152775fe2f0d90d23@9front.org> (raw)
I'm consistently seeing some strange behavior from cs
and dns on cat-v.org. Tons of cs/dns procs are getting
(seemingly) stuck in Pwrite/Pread and never dying.
The number keeps building until the machine slows
to a crawl and I can no longer even cpu into it.
For example, right now:
cpu% ps|grep -e ' cs'|wc -l
20
cpu% ps|grep -e ' dns'|wc -l
60
The system is still useable but from recent experience
this will keep building until things become unuseably
slow. I did some traces in acid:
One of the cs procs stuck in Pwrite:
http://okturing.com/src/1639/body
One of the dns procs stuck in Pread:
http://okturing.com/src/1638/body
I think this is being triggered by mail messages, either
incoming or outgoing. I'm running another mlmgr list
that developed the same problem as what happened
with the 9front list when I was offline, moving -- people
were receiving numerous multiple copies of every message
sent to the list. After rebooting the flood of messages
seemed to stop. I suspect there is a connection here...
somewhere.
-sl
next reply other threads:[~2013-04-11 14:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 14:52 sl [this message]
2013-04-11 18:50 sl
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3748dfae418a7f1152775fe2f0d90d23@9front.org \
--to=sl@9front.org \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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.
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 NNTP newsgroup(s).