how to restore old bugzilla db in new environment
daniel....@yellowworld.ch
had a hd crash. Now i need to setup a new environment and restore the
MySQL DB "bugs". The Problem i encounter is to find the same versions
of Bugzilla and MySQL, including all perl modules in the required
versions.
Does any one have experience with something like that, and maybe could
say if that is going to work at all.
Any help is highly appreciated.
Thanks
daniel
Tosh, Michael J
> Hi all. Our Linux box running Bugzilla (2.16.4) with MySQL (3.22.5)
> had a hd crash. Now i need to setup a new environment and restore the
> MySQL DB "bugs". The Problem i encounter is to find the same versions
> of Bugzilla and MySQL, including all perl modules in the required
> versions.
>
> Does any one have experience with something like that, and maybe could
> say if that is going to work at all.
You don't need the SAME version of MySQL. So long as you have a
database dump and a running MySQL daemon, you should be able to restore
your database.
You also don't NEED Bugzilla 2.16.x, but you can find it here:
http://ftp.mozilla.org/pub/mozilla.org/webtools/archived/
I would recommend using at LEAST 2.16.11, if not something newer. Any
newer version of Bugzilla will 'work', but you'd need to upgrade your
database using checksetup.pl first.
Good luck.
Gervase Markham
> Hi all. Our Linux box running Bugzilla (2.16.4) with MySQL (3.22.5)
> had a hd crash. Now i need to setup a new environment and restore the
> MySQL DB "bugs". The Problem i encounter is to find the same versions
> of Bugzilla and MySQL, including all perl modules in the required
> versions.
You don't necessarily need to do that. If you run "checksetup.pl",
Bugzilla will automatically upgrade the database to work with the newer
version of Bugzilla.
Of course, you may not want to do an upgrade at this point.
> Does any one have experience with something like that, and maybe could
> say if that is going to work at all.
No, sorry :-( No experience.
Gerv
daniel....@yellowworld.ch
First of all thanks.
I installed MySQL 4.1 and Bugzilla 2.16.11 as you suggested and
restored the backup. Everything is running and i can login into
Bugzilla. When i run the sanity check as suggested in the release
notes i get the following error:
Software error:
SELECT DISTINCT submitter_id, bug_id FROM attachments WHERE
submitter_id IS NOT NULL: Got error 127 from storage engine at
globals.pl line 276.
I also get a weired result when i query for bugs for a list of those,
only the bug_id is shown aligned to right. Also get an error when i
try to show more columns, i can select columns but when submit the
changes i get an software error.
Any idea what i should do?
thanks
Tosh, Michael J
> Software error:
> SELECT DISTINCT submitter_id, bug_id FROM attachments WHERE
> submitter_id IS NOT NULL: Got error 127 from storage engine at
> globals.pl line 276.
Sounds like an odd error, here is a discussion about error 127:
http://forums.mysql.com/read.php?88,27250,35249#msg-35249
Another resource:
http://bugs.mysql.com/bug.php?id=6306
My suggestion? REPAIR TABLE attachments;
daniel....@yellowworld.ch
> Quoting daniel.meye...@yellowworld.ch:
>
After a restart the problem with the columns for the bug list has
disappeard.
mysqlcheck gives the following result:
bugs.attachments
warning : 1 client is using or hasn't closed the table properly
error : Wrong bytesec: 177-196-2 at linkstart: 17789404
error : Corrupt
mysqlrepair gives the following result:
bugs.attachments
info : Wrong bytesec: 177-196- 2 at 17789404; Skipped
info : Found link that points at 6095796864119566159 (outside data
file) at 17789420
info : Found link that points at -947003061847194407 (outside data
file) at 17789756
info : Found block with too small length at 17789828; Skipped
... (more)
info : Found link that points at 9175206683477003464 (outside data
file) at 17794028
info : Found block with too small length at 17794368; Skipped
error : Not enough memory for blob at 17795336 (need 934327745)
info : Wrong bytesec: 177-196- 2 at 17789404; Skipped
... (more)
info : Found link that points at 6095796864119566159 (outside data
file) at 17789420
error : Not enough memory for blob at 17795336 (need 934327745)
status : Operation failed
It seems that the problem with the hd existed already before the last
backup, so some data restored are corrupt. As we do daily backup, i
try to restore earlier backups to find the original add of the
corrupted attachment and attach them again to the bugs. I think there
is no other way around this.
thanks v m for all the help.