[Koha-devel] mysqldump & restore issues

[Mike Hafen]

Sorry to hear you are having problems with your failover server.  I've had
problems with failovers servers and backups before, it's not fun.

Have you checked the memory and hard drive of the failover server?  (the
host)  That would be my first guess.  Also, it may be the filesystem on
either the host or the guest, but I'm not up on file systems so I can't say
for sure.

There's a good chance the row number in the error message relates to the
biblioitemnumber.  You could try just querying the database for rows around
that.  Something like 'select * from biblioitems where biblioitemnumber >
41470 and biblioitemnumber < 41600.  If you see the error it could be data,
disk, or filesystem related.  If you don't it's probably memory related, but
maybe filesystem related.

Good luck.

2010/9/17 Christopher Curry <ccurry at amphilsoc.org>

>  Hello all,
>
> I'm trying to create a mirrored failover server with data from our live
> Koha.  In order to do so, I'm using *mysqldump* and *mysql* for backup and
> restore.
>
> I've discovered a troubling problem and I can't determine the cause.
>
> I run this command to backup the live server:
>
> *mysqldump --single-transaction -ukoha -p koha >
> /home/koha/KohaServerBackups/koha.`/bin/date +\%Y\%m\%d\%H\%M\%S`.sql*
>
> This seems to work correctly (and very quickly!  1.7 GB database exports in
> 2 min)
>
> Then, I run this command:
>
> *mysql -v -ukoha -p koha < /home/koha/KohaServerBackups/backupFileName.sql
> *
>
> This also seems to work, as I receive no warnings or error messages.
>
> I'm exporting from a 3.00.05.001 system and importing to a 3.00.05.003
> system, so I then run the *$KOHA_SOURCE/installer/data/mysql/
> updatedatabase.pl* script.
>
> Relevant specs:
>
> MySQL version: mysql Ver 14.12 Distrib 5.0.51a, for debian-linux-gnu (i486)
> using readline 5.2
> OS: Debian Lenny
>
> Failover server is virtual, running on VirtualBox 3.2.8, on an Ubuntu 10.4
> host.
>
>
> All GUI functions of the Koha failover server seem to operate correctly,
> but when I run *mysqlcheck -ukoha -p koha* the check fails on
> koha.biblioitems with the following error message:
>
> mysqlcheck: Got error: 2013: Lost connection to MySQL server during query
> when executing 'CHECK TABLE ... '
>
> If I try mysqldump, I get the same error, but it is more specific,
> reporting that it falls on row 41536.
>
> If I check /var/log/syslog, I see this http://pastebin.com/YuuFBHry
>
> "InnoDB: Database page corruption on disk or a failed file read of page
> 58164", etc.
>
> Both mysqlcheck & mysqldump work without error on the live server, so I'm
> thinking that something must be happening to the data during the export or
> import that corrupts the InnoDB data, but this is speculation, since I'm not
> a MySQL expert.
>
> Has anyone seen behavior like this?  Any suggestions for further
> troubleshooting/resolution?
>
> --
>
> Cheers,
>
> Christopher Curry
> Assistant Technical Librarian / Assistant IT Officer
>
> American Philosophical Society
> 105 South Fifth Street
> Philadelphia, PA 19106-3386
> Tel. (215) 599-4299
>
> ccurry at amphilsoc.org
> Main Library number: (215)440-3400
> APS website: http://www.amphilsoc.org
>
>
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20100920/5adeb8f1/attachment.htm>