holland-coredev team mailing list archive

[MikeG <668161@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

It would be a useful feature for Holland to log perror output in cases
where a backup fails.  Currently, it will log a failed backup due to a
crashed table as follows:

2010-10-28 19:27:27,520 [ERROR] /usr/bin/mysqldump[4773]: mysqldump: Got
error: 1016: Can't open file: 'post.MYI' (errno: 145) when using LOCK
TABLES

It would be nice if it could capture errno and run it through perror so
that you end up seeing:

2010-10-28 19:27:27,520 [ERROR] /usr/bin/mysqldump[4773]: mysqldump: Got error: 1016: Can't open file: 'post.MYI' (errno: 145) when using LOCK TABLES
2010-10-28 19:27:27,520 [INFO]  MySQL error code 145: Table was marked as crashed and should be repaired

** Affects: holland-backup
     Importance: Undecided
         Status: New

-- 
Failures log perror output
https://bugs.launchpad.net/bugs/668161
You received this bug notification because you are a member of Holland
Developers, which is the registrant for holland-backup.

Status in Holland Backup Framework: New

Bug description:
It would be a useful feature for Holland to log perror output in cases where a backup fails.  Currently, it will log a failed backup due to a crashed table as follows:

2010-10-28 19:27:27,520 [ERROR] /usr/bin/mysqldump[4773]: mysqldump: Got error: 1016: Can't open file: 'post.MYI' (errno: 145) when using LOCK TABLES

It would be nice if it could capture errno and run it through perror so that you end up seeing:

2010-10-28 19:27:27,520 [ERROR] /usr/bin/mysqldump[4773]: mysqldump: Got error: 1016: Can't open file: 'post.MYI' (errno: 145) when using LOCK TABLES
2010-10-28 19:27:27,520 [INFO]  MySQL error code 145: Table was marked as crashed and should be repaired