#248: Database dump failure
----------------------+-----------------------------------------------------
Reporter: tbrooks | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: MiscUtil | Version:
Keywords: INSPIRE |
----------------------+-----------------------------------------------------
As I mentioned on the last EVO, I'm taking some dumps of the db on dev
and beta. Tibor suggested that max_allowed_packet was the culprit for
having an unlcean dump of the db.
This is true for dev, I believe, in that I just finally took a snapshot of
the db there with no errors, after raising max_allowed_packet in
/etc/my.cnf to 500M. Still loading that on my machine here to make sure I
am right.
However, on beta, I set max_allowed_packet to 500M and then 1G (on
pcudssw1502)and still have a problem:
{{{
2010-08-16 20:15:01 --> Task #6337 started.
2010-08-16 20:15:01 --> Reading parameters started
2010-08-16 20:15:01 --> Reading parameters ended
2010-08-16 20:15:01 --> Database dump started
2010-08-16 20:15:01 --> ... writing /opt/tbrooks/data-dumps//inspirehep-
dbdump-2010-08-16_20:15:01.sql
2010-08-16 20:24:53 --> ERROR: mysqldump exit code is 768.
2010-08-16 20:24:54 --> Task #6337 finished. [ERROR]
}}}
I can't find anything obvious about 768 error codes from MySQL.
This is not the same problem that dev was giving when doing the dumps that
failed, so this may be a different issue, but note that the dump file gets
to about 15G and ends with:
{{{
--
-- Dumping data for table `rnkCITATIONDATA`
--
LOCK TABLES `rnkCITATIONDATA` WRITE;
/*!40000 ALTER TABLE `rnkCITATIONDATA` DISABLE KEYS */;
}}}
--
Ticket URL: <http://invenio-software.org/ticket/248>
Invenio <http://invenio-software.org>
