From: Jonathan Larmour <jifl@jifvik.org>
To: Jim Meyering <jim@meyering.net>
Cc: overseers@sourceware.org
Subject: Re: high load average -> slow builds
Date: Tue, 15 Jan 2013 18:25:00 -0000 [thread overview]
Message-ID: <50F59F01.3000106@jifvik.org> (raw)
In-Reply-To: <87txqiltrg.fsf@rho.meyering.net>
On 15/01/13 08:45, Jim Meyering wrote:
>
> top - 08:39:36 up 812 days, 17:27, 2 users, load average: 22.23, 26.47, 25.77
> Tasks: 318 total, 16 running, 299 sleeping, 0 stopped, 3 zombie
> Cpu(s): 18.3% us, 7.7% sy, 43.6% ni, 15.7% id, 14.5% wa, 0.2% hi, 0.0% si
> Mem: 16631336k total, 15213152k used, 1418184k free, 199780k buffers
> Swap: 2096376k total, 22868k used, 2073508k free, 12319912k cached
>
> PID USER PR NI %CPU TIME+ %MEM VIRT RES SHR S COMMAND
> 13593 apache 33 8 67.9 0:07.56 0.4 73536 67m 1516 R python
> 8219 bugzilla 25 0 56.0 26:17.24 3.1 506m 502m 3104 R email_in.pl
That email_in.pl is odd. There's one running now, occupying full CPU, and
has been running for 45 mins and counting. It comes from this:
bugzilla 25689 25675 25689 0 1 17:31 ? 00:00:00
/qmail/bin/preline sh -c /www/gcc/bugzilla/email_in.pl -v
2>>/sourceware/bugzilla/email_in.log || exit 99
Presumably started directly from qmail. I tried stracing the perl script
instance itself, but whatever it's doing is all user space.
It seems too much of a coincidence that it's there at the top when you
looked and when I looked.
The log at this time includes:
Comments cannot be longer than 65535 characters.
which seems fair enough as a one-off, except this log message seems to get
triggered a lot - about once an hour, which doesn't seem right.
Also:
SENDER=gcc-bugzilla@gcc.gnu.org
which implies bugzilla was the one sending the mail.
Has the script got stuck, perhaps sending ever larger email in a loop? Or
is someone abusing it?
It's hard for me to see what the email is it's dealing with. Perhaps
someone more familiar with bugzilla can work out where (or if) it spools
it temporarily.
Jifl
--
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine
next prev parent reply other threads:[~2013-01-15 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 8:45 Jim Meyering
2013-01-15 18:25 ` Jonathan Larmour [this message]
2013-01-15 18:31 ` Jonathan Larmour
2013-01-15 18:36 ` Daniel Berlin
2013-01-15 21:18 ` Frank Ch. Eigler
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=50F59F01.3000106@jifvik.org \
--to=jifl@jifvik.org \
--cc=jim@meyering.net \
--cc=overseers@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).