From: fche@elastic.org
To: overseers@sources.redhat.com
Subject: Re: Error message from http://sources.redhat.com/bugzilla/show_bug.cgi
Date: Sun, 02 Sep 2007 13:35:00 -0000 [thread overview]
Message-ID: <20070902133516.GJ3951@elastic.org> (raw)
Hi -
On Sun, Sep 02, 2007 at 02:23:02PM +0100, Israel G. Lugo wrote:
> I've been getting the following error when trying to access specific
> bugs on the source.redhat.com bugzilla: [...]
> DBD::mysql::st execute failed: Can't open file: 'bugs.MYI' (errno: 145)
> [...]
A mysql "repair table" appears to have brought this back to life.
The mysql logs indicate something may have gone wrong yesterday:
070815 6:09:38 [ERROR] Got error -1 when reading table './sourcesbugs/longdescs'
070827 8:54:10 [ERROR] Got error -1 when reading table './sourcesbugs/longdescs'
070827 9:18:37 [ERROR] Got error -1 when reading table './sourcesbugs/longdescs'
070901 14:40:32 [Note] /usr/libexec/mysqld: Normal shutdown
070901 14:40:32 InnoDB: Starting shutdown...
070901 14:40:35 InnoDB: Shutdown completed; log sequence number 0 43654
070901 14:40:35 [Note] /usr/libexec/mysqld: Shutdown complete
070901 14:40:35 mysqld ended
070901 14:40:35 mysqld started
070901 14:40:35 InnoDB: Started; log sequence number 0 43654
/usr/libexec/mysqld: ready for connections.
Version: '4.1.20' socket: '/var/lib/mysql/mysql.sock' port: 0 Source distribution
070901 14:46:41 [ERROR] /usr/libexec/mysqld: Can't open file: 'bugs.MYI' (errno: 145)
070901 14:46:41 [ERROR] /usr/libexec/mysqld: Can't open file: 'bugs.MYI' (errno: 145)
070901 14:47:23 [ERROR] /usr/libexec/mysqld: Can't open file: 'bugs.MYI' (errno: 145)
070901 14:47:23 [ERROR] /usr/libexec/mysqld: Can't open file: 'bugs.MYI' (errno: 145)
070901 14:47:28 [ERROR] /usr/libexec/mysqld: Can't open file: 'bugs.MYI' (errno: 145)
- FChE
reply other threads:[~2007-09-02 13:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070902133516.GJ3951@elastic.org \
--to=fche@elastic.org \
--cc=overseers@sources.redhat.com \
/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).