public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@bitrange.com>
To: overseers@sourceware.org
Subject: Bugzilla DB error displaying PR25331
Date: Mon, 29 Jun 2020 00:01:47 -0400 (EDT)	[thread overview]
Message-ID: <alpine.BSF.2.20.16.2006282350170.74942@arjuna.pair.com> (raw)

After finally fixing this bug, i.e.
https://sourceware.org/bugzilla/show_bug.cgi?id=25331 I was
adding a few final words and changing the status to
resolved/fixed, but got a message about bugzilla being edited:
"overwrite, throw away, or add just your new comment"
(inaccurate quote but I hope you get what's referred).

I choose "add just your new comment" and was greeted by a page
with a request to send this report and a big red error message
that starts as follows:

"undef error - DBD::mysql::st execute failed: Out of
resources when opening file '/var/tmp/#sql_f6f0_0.MAI'
(Errcode: 24 "Too many open files") [for Statement "SELECT
DISTINCT groups.id, name, description, CASE WHEN
bug_group_map.group_id IS NOT NULL THEN 1 ELSE 0 END, CASE WHEN
groups.id IN(8,7) THEN 1 ELSE 0 END, isactive, membercontrol,
othercontrol FROM groups LEFT JOIN bug_group_map ON
bug_group_map.group_id = groups.id AND bug_id = ? LEFT JOIN
group_control_map ON group_control_map.group_id = groups.id AND
group_control_map.product_id = ? WHERE isbuggroup = 1 ORDER BY
description" with ParamValues: 0=25331, 1=4] at Bugzilla/Bug.pm
line 3869"

...and that you probably see just by visiting PR25331 (as I did
on another machine).  If not, I printed to a PDF, to be sent on
request.

Sorry.

brgds, H-P

             reply	other threads:[~2020-06-29  4:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29  4:01 Hans-Peter Nilsson [this message]
2020-06-29  6:37 ` Andrew Pinski
2020-06-29 10:19 ` 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=alpine.BSF.2.20.16.2006282350170.74942@arjuna.pair.com \
    --to=hp@bitrange.com \
    --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).