mythbuntu-bugs team mailing list archive

[Aaron Whitehouse <question106476@xxxxxxxxxxxxxxxxxxxxx>]

New question #106476 on Mythbuntu:
https://answers.launchpad.net/mythbuntu/+question/106476

I have a cron job to do a backup every day at around 4am.

.sql.gz files for each day are in the correct folder until 31 March 
2010, when they change to being .sql files that are only 803 bytes 
(instead of approx 9 MB) that say the following:
-- MySQL dump 10.13  Distrib 5.1.37, for debian-linux-gnu (x86_64)
--
-- Host: localhost    Database: mythconverg
-- ------------------------------------------------------
-- Server version	5.1.37-1ubuntu5.1

/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8 */;
/*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */;
/*!40103 SET TIME_ZONE='+00:00' */;
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, 
FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;

It looks to me as though the script is now crashing at this point.

When I run mythconverg_backup with the --verbose option, this is the output:

===

Configuring environment:
   -    username: mythbuntu
   -        HOME: /home/mythbuntu
   - MYTHCONFDIR: /home/mythbuntu/.mythtv

Parsing configuration files:
   - checking: /home/mythbuntu/.mythtv/config.xml
      parsing: /home/mythbuntu/.mythtv/config.xml
   - checking: /home/mythbuntu/.mythtv/backuprc
      parsing: /home/mythbuntu/.mythtv/backuprc

Applying command-line arguments.

Checking configuration.

No DBSchemaVer specified, querying database.
Found DBSchemaVer: 1244.

Database Information:
          DBHostName: localhost
              DBPort: 0
          DBUserName: mythtv
          DBPassword: XXX
              DBName: mythconverg
         DBSchemaVer: 1244
   DBBackupDirectory: /home/mythbuntu/Backup/AutoMythBackups
    DBBackupFilename: mythconverg-1244-20100405134846.sql

Executables:
           mysqldump: mysqldump
            compress: gzip

Attempting to use supplied password for mysqldump.
Any [client] or [mysqldump] password specified in the MySQL options file 
will
take precedence.

Executing command:
'/usr/bin/mysqldump' --defaults-extra-file='/tmp/JDUdoBOWE8' 
--host='localhost' --user='mythtv' --add-drop-table --add-locks 
--allow-keywords --complete-insert --extended-insert --lock-tables 
--no-create-db --quick 'mythconverg' 2>&1 
1>'/home/mythbuntu/Backup/AutoMythBackups/mythconverg-1244-20100405134846.sql'

mysqldump exited with status: 2
mysqldump output:
mysqldump: Got error: 144: Table './mythconverg/recordedseek' is marked 
as crashed and last (automatic?) repair failed when using LOCK TABLES

===

Any ideas how to fix this?

You received this question notification because you are a member of
Mythbuntu Bug Team, which is an answer contact for Mythbuntu.