| Author |
Message |
|
mattbatt
|
 Posted: Tue Feb 01, 2011 12:50 am |
|
|
Joined: Tue Aug 15, 2006 11:14 am
Posts: 1343
Location:
Orlando FL
|
I am trying to migrate my myth install to a new machine. The latest issue I have run into is that my mythbackup isn't working. If I run it from the command line I can see an error ( I don't know if it is THE error)
Code: "Warning, could not get record counts from DB dump!" the files show up as 1 kb.
What should I do? How can I repair the database and copy it. As you all know the database is the most valuable file on mythtv I need to protect my 6 years worth of "investment". _________________ My System
Last edited by mattbatt on Fri Feb 04, 2011 12:57 am, edited 1 time in total.
|
|
| Top |
|
 |
|
mattbatt
|
Posted: Tue Feb 01, 2011 11:55 am |
|
|
Joined: Tue Aug 15, 2006 11:14 am
Posts: 1343
Location:
Orlando FL
|
Getting closer to an answer. I found this page http://www.knoppmythwiki.org/index.php? ... hConvergDB
I have an improvement on the Code: myisamchk *.MYI >> /tmp/myisamchk_log.txt the second bit dumps it to a txt file. the file was 1400 lines long so Putty didn't want to scroll all the way back.
Unfortunately there weren't any problems that I could see. _________________ My System
|
|
| Top |
|
|
|
mattbatt
|
Posted: Tue Feb 01, 2011 12:06 pm |
|
|
Joined: Tue Aug 15, 2006 11:14 am
Posts: 1343
Location:
Orlando FL
|
I also output mythbackup to a text file and found no errors except these at the very end.
Code: Sanity checking your backup...
Checking for the existance of the backup tar file...
Using file /myth/backup/savedfiles.tar.gz
Backup tar file exists. Checking the compression...
Compression looks OK. Checking backup tar file contents...
Generating a list of the backup contents...
/bin/tar: ./var/lib/alsa/asound.state: Not found in archive
/bin/tar: Exiting with failure status due to previous errors
Generating a list of the directory contents...
Comparing directory versus backup contents...
Live and saved file lists match.
Checking for the existance of the DB dump file...
Using file /myth/backup/mythconverg.sql.gz
DB dump file exists. Checking the compression...
Compression looks OK. Checking DB dump contents...
Generating a list of tables and record counts in the DB dump...
Warning, could not get record counts from DB dump!
The backup is bad or already out of date!
_________________ My System
|
|
| Top |
|
|
|
mattbatt
|
Posted: Tue Feb 01, 2011 12:28 pm |
|
|
Joined: Tue Aug 15, 2006 11:14 am
Posts: 1343
Location:
Orlando FL
|
I think I found something inside the /data/srv/mysql/ folder there was a file called pippin.err (pippin is the name of mythtv on my network LOTR)
It has a slew of errors and I don't know where to start Sorry for the long post.
Code: 100921 17:37:42 mysqld started
100921 17:37:42 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295
100921 17:37:42 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
100921 17:37:42 InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
100921 17:37:42 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
100921 17:37:42 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
100921 17:37:43 InnoDB: Started; log sequence number 0 0
100921 17:37:43 [Warning] 'user' entry 'root@pippin' ignored in --skip-name-resolve mode.
100921 17:37:43 [Warning] 'user' entry '@pippin' ignored in --skip-name-resolve mode.
100921 17:37:43 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.75' socket: '/tmp/mysql.sock' port: 3306 Source distribution
100921 17:37:43 [Note] /usr/sbin/mysqld: Normal shutdown
100921 17:37:43 InnoDB: Starting shutdown...
100921 17:37:47 InnoDB: Shutdown completed; log sequence number 0 43655
100921 17:37:47 [Note] /usr/sbin/mysqld: Shutdown complete
100921 17:37:47 mysqld ended
100921 17:37:47 mysqld started
100921 17:37:47 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295
100921 17:37:47 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295
100921 17:37:47 InnoDB: Started; log sequence number 0 43655
100921 17:37:47 [Warning] 'user' entry 'root@pippin' ignored in --skip-name-resolve mode.
100921 17:37:47 [Warning] 'user' entry '@pippin' ignored in --skip-name-resolve mode.
100921 17:37:47 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.75' socket: '/tmp/mysql.sock' port: 3306 Source distribution
100921 17:37:49 [Warning] 'user' entry 'root@pippin' ignored in --skip-name-resolve mode.
100921 17:37:49 [Warning] 'user' entry '@pippin' ignored in --skip-name-resolve mode.
100921 17:37:49 [Warning] 'user' entry 'mythtv@myhost' ignored in --skip-name-resolve mode.
100921 17:37:49 [Warning] 'db' entry 'mythconverg mythtv@myhost' ignored in --skip-name-resolve mode.
100921 17:37:49 [Warning] 'user' entry 'root@pippin' ignored in --skip-name-resolve mode.
100921 17:37:49 [Warning] 'user' entry '@pippin' ignored in --skip-name-resolve mode.
100921 17:37:49 [Warning] 'user' entry 'mythtv@myhost' ignored in --skip-name-resolve mode.
100921 17:37:49 [Warning] 'db' entry 'mythconverg mythtv@myhost' ignored in --skip-name-resolve mode.
100921 17:39:37 [Note] /usr/sbin/mysqld: Normal shutdown
100921 17:39:37 InnoDB: Starting shutdown...
100921 17:39:37 InnoDB: Shutdown completed; log sequence number 0 92092
100921 17:39:37 [Note] /usr/sbin/mysqld: Shutdown complete
100921 17:39:37 mysqld ended
100929 00:21:25 mysqld started
100929 0:21:25 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295
100929 0:21:25 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
100929 0:21:25 InnoDB: Retrying to lock the first data file
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
100929 0:23:05 InnoDB: Unable to open the first data file
InnoDB: Error in opening ./ibdata1
100929 0:23:05 InnoDB: Operating system error number 11 in a file operation.
InnoDB: Error number 11 means 'Resource temporarily unavailable'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html
InnoDB: Could not open or create data files.
InnoDB: If you tried to add new data files, and it failed here,
InnoDB: you should now edit innodb_data_file_path in my.cnf back
InnoDB: to what it was, and remove the new ibdata files InnoDB created
InnoDB: in this failed attempt. InnoDB only wrote those files full of
InnoDB: zeros, but did not yet use them in any way. But be careful: do not
InnoDB: remove old data files which contain your precious data!
100929 0:23:06 [Warning] 'user' entry 'root@pippin' ignored in --skip-name-resolve mode.
100929 0:23:06 [Warning] 'user' entry '@pippin' ignored in --skip-name-resolve mode.
100929 0:23:06 [Warning] 'user' entry 'mythtv@myhost' ignored in --skip-name-resolve mode.
100929 0:23:06 [Warning] 'db' entry 'mythconverg mythtv@myhost' ignored in --skip-name-resolve mode.
100929 0:23:06 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.75' socket: '/tmp/mysql.sock' port: 3306 Source distribution
100929 0:29:39 [ERROR] /usr/sbin/mysqld: Incorrect information in file: './mythconverg/weatherscreens.frm'
100929 0:29:39 [ERROR] /usr/sbin/mysqld: Incorrect information in file: './mythconverg/weatherscreens.frm'
100929 0:29:46 [ERROR] /usr/sbin/mysqld: Incorrect information in file: './mythconverg/weatherscreens.frm'
100929 0:29:46 [ERROR] /usr/sbin/mysqld: Incorrect information in file: './mythconverg/weatherscreens.frm'
100929 0:29:49 [ERROR] /usr/sbin/mysqld: Incorrect information in file: './mythconverg/weatherscreens.frm'
100929 0:29:49 [ERROR] /usr/sbin/mysqld: Incorrect information in file: './mythconverg/weatherscreens.frm'
100929 0:29:49 [ERROR] /usr/sbin/mysqld: Incorrect information in file: './mythconverg/weatherscreens.frm'
100929 0:29:49 [ERROR] /usr/sbin/mysqld: Incorrect information in file: './mythconverg/weatherscreens.frm'
100929 0:29:51 [ERROR] /usr/sbin/mysqld: Incorrect information in file: './mythconverg/weatherscreens.frm'
100929 0:29:51 [ERROR] /usr/sbin/mysqld: Incorrect information in file: './mythconverg/weatherscreens.frm'
100929 0:29:52 [ERROR] /usr/sbin/mysqld: Incorrect information in file: './mythconverg/weatherscreens.frm'
100929 0:29:52 [ERROR] /usr/sbin/mysqld: Incorrect information in file: './mythconverg/weatherscreens.frm'
100929 0:30:01 [ERROR] /usr/sbin/mysqld: Incorrect information in file: './mythconverg/weatherscreens.frm'
100929 0:30:01 [ERROR] /usr/sbin/mysqld: Incorrect information in file: './mythconverg/weatherscreens.frm'
100929 0:32:11 [Note] /usr/sbin/mysqld: Normal shutdown
100929 0:32:13 [Note] /usr/sbin/mysqld: Shutdown complete
100929 00:32:13 mysqld ended
_________________ My System
|
|
| Top |
|
|
|
manicmike
|
Posted: Tue Feb 01, 2011 2:57 pm |
|
|
Joined: Sun Aug 28, 2005 7:07 pm
Posts: 821
Location:
Melbourne, Australia
|
mattbatt wrote: What should I do? How can I repair the database and copy it.
Have you performed a mysqlcheck? Sorry if it seems obvious, but you haven't mentioned it.
Mike
_________________
*********************
LinHES 7.4
Australian Dragon
*********************
|
|
| Top |
|
|
|
mattbatt
|
Posted: Tue Feb 01, 2011 5:54 pm |
|
|
Joined: Tue Aug 15, 2006 11:14 am
Posts: 1343
Location:
Orlando FL
|
|
I've done a myisamchk and reported no errors but I haven't done a mysqlcheck
_________________ My System
|
|
| Top |
|
|
|
mattbatt
|
Posted: Wed Feb 02, 2011 10:55 pm |
|
|
Joined: Tue Aug 15, 2006 11:14 am
Posts: 1343
Location:
Orlando FL
|
OK so I do have some weather related errors when I run mysqlcheck almost everything came back as "OK" here are the bad ones. Code: mythconverg.videotypes OK
mythconverg.weatherdatalayout
note : The storage engine for the table doesn't support repair
mythconverg.weatherscreens
note : The storage engine for the table doesn't support repair
mythconverg.weathersourcesettings
note : The storage engine for the table doesn't support repair
mythconverg.websites OK
I really don't care about the weather stuff how can I get around this? _________________ My System
|
|
| Top |
|
|
|
mattbatt
|
Posted: Wed Feb 02, 2011 11:04 pm |
|
|
Joined: Tue Aug 15, 2006 11:14 am
Posts: 1343
Location:
Orlando FL
|
|
| Top |
|
|
|
welner
|
Posted: Thu Feb 03, 2011 6:30 am |
|
|
Joined: Sat Jan 06, 2007 7:08 pm
Posts: 125
|
|
just a general unix hint related to your scrolling problems in putty....
there is a buffer setting somewhere inside of the putty app. good luck finding it. if you do find it, you have to start a new ssh session.
also, you can do:
less filename
or
more filename
or
vi filename
hitting space, up, down arrow keys when using less will allow you to navigate. with more, you can hit the space key to move forward. and vi will allow you to do a bunch of stuff.
_________________
DH87MC i7-4770 16GB ram Xonar Essence ST geforce 710 LinHes 8.6
|
|
| Top |
|
|
|
mattbatt
|
Posted: Thu Feb 03, 2011 10:14 am |
|
|
Joined: Tue Aug 15, 2006 11:14 am
Posts: 1343
Location:
Orlando FL
|
|
| Top |
|
|
|
christ
|
Posted: Thu Feb 03, 2011 5:02 pm |
|
|
Joined: Mon Dec 24, 2007 9:47 am
Posts: 535
Location:
Ottawa, Canada
|
Hi mattbatt,
The error you mention is not familiar to me and ideally if it was me, I would manually edit the backup script to add verbose flags on the commands and generally narrow down the offending issue. The script is normally at "/usr/LH/bin/mythbackup" but to know for sure you can run:
Code: which mythbackup You can also try: Code: optimize_mythdb.py
It really just does mysqlcheck but with optimize as well as repair flags. Normally LinHES runs this nightly.
Also it may be worth trying the backup procedure with mythbackend and frontend shutdown. The script should do this but you never know.
I'm also curious about the warnings in your log that speak of mysqld already running and ibdata1 not able to write a lock file. If you shut mysqld down then in the associated lock file should not exist. Not certain what the name of the lock file is.
You could also try the mythtv.org version of backup just to see if it gives you more info or fixes things. It is at: http://www.mythtv.org/wiki/Database_Backup_and_Restore
not much help but I couldn't let a brother in need twist...
|
|
| Top |
|
|
|
tjc
|
Posted: Thu Feb 03, 2011 8:54 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
christ wrote: Also it may be worth trying the backup procedure with mythbackend and frontend shutdown. The script should do this but you never know.
That was definitely on my short list of things to try.
BTW - the script can and does shut down the BE and DB, but it can not shutdown the FE as that might be what kicked it off. Aside from certain types of daemon processes, killing your parent process is generally a bad idea, especially if you want to keep running. 
|
|
| Top |
|
|
|
mattbatt
|
Posted: Thu Feb 03, 2011 10:26 pm |
|
|
Joined: Tue Aug 15, 2006 11:14 am
Posts: 1343
Location:
Orlando FL
|
Alright I shut down Myth front and backend and ran Code: sudo mythbackup >> /tmp/mythbackup.log the only anomalous things I could see were this MYI file with a ton of deleted blocks. Code: Checking MyISAM file: credits.MYI
Data records: 49415 Deleted blocks: 2496
- check file-size
- check record delete-chain
- check key delete-chain
- check index reference
- check data record references index: 1
- check data record references index: 2 and of course my old stand-by. Code: ./etc/unclutter.cfg
/bin/tar: ./var/lib/alsa/asound.state: Cannot stat: No such file or directory
/bin/tar: Exiting with failure status due to previous errors
Sanity checking your backup...
Checking for the existance of the backup tar file...
Using file /myth/backup/savedfiles.tar.gz
Backup tar file exists. Checking the compression...
Compression looks OK. Checking backup tar file contents...
Generating a list of the backup contents...
/bin/tar: ./var/lib/alsa/asound.state: Not found in archive
/bin/tar: Exiting with failure status due to previous errors
Generating a list of the directory contents...
Comparing directory versus backup contents...
Live and saved file lists match.
Checking for the existance of the DB dump file...
Using file /myth/backup/mythconverg.sql.gz
DB dump file exists. Checking the compression...
Compression looks OK. Checking DB dump contents...
Generating a list of tables and record counts in the DB dump...
Warning, could not get record counts from DB dump!
The backup is bad or already out of date!
ok: run: mythbackend: (pid 14533) 1s
_________________ My System
|
|
| Top |
|
|
|
mattbatt
|
Posted: Thu Feb 03, 2011 10:49 pm |
|
|
Joined: Tue Aug 15, 2006 11:14 am
Posts: 1343
Location:
Orlando FL
|
running Optimize gave me
Code: /usr/lib/python2.6/site-packages/MySQLdb/__init__.py:34: DeprecationWarning: the sets module is deprecated
from sets import ImmutableSet
REPAIR archiveitems
OPTIMIZE archiveitems
ANALYZE archiveitems
REPAIR callsignnetworkmap
OPTIMIZE callsignnetworkmap
ANALYZE callsignnetworkmap
REPAIR capturecard
OPTIMIZE capturecard
ANALYZE capturecard
.... etc......
_________________ My System
|
|
| Top |
|
|
|
mattbatt
|
Posted: Thu Feb 03, 2011 11:15 pm |
|
|
Joined: Tue Aug 15, 2006 11:14 am
Posts: 1343
Location:
Orlando FL
|
OK OK OK
I think I may have found a chink in some armor
I ran
Code: /usr/share/mythtv/mythconverg_backup.pl -verbose and I think it worked it saved a file called Code: mythconverg-1254-20110204000901.sql.gz in the /myth/backup folder.
I am going to try it to see if it works. _________________ My System
|
|
| Top |
|
|
View unanswered posts
View active topics
Print view
Previous topic Next topic 
LinHES Home
Board index
FAQ
Search
Login 
Register
