LinHES Forums http://forum.linhes.org/ |
|
MySQL, mythfilldatabase and mythconverg problem http://forum.linhes.org/viewtopic.php?f=6&t=11126 |
Page 1 of 1 |
Author: | mihanson [ Thu Aug 10, 2006 3:49 pm ] |
Post subject: | MySQL, mythfilldatabase and mythconverg problem |
Hi everyone, I'm having a problem with MySQL and mythfilldatabase. My mythfilldatabase is execcuting automaticly, but I'm receiving the: Quote: Last mythfilldatabase run started on 2006-08-10 14:23 and ended on 2006-08-10 14:23. mythfilldatabase ran, but did not insert any new data into the Guide. This can indicate a potential grabber failure. error.Suggested next mythfilldatabase run: 2006-08-11 03:00. There's guide data until 2006-08-22 22:30 (12 days). DataDirect Status: Your subscription expires on 09/28/06 05:31:59 This mythconverg database was imported from a R5B7 install automagiclly from tjc's backup/restore scripts and yes, I used his check_backup.sh script and everything checked out. It was running fine for a few weeks. At the same time, the mysql.log file is HUGE! This morning it was nearly 900MB. To prevent it from killing my root partition I moved it to a samba share and created a new file in it's place Code: # touch /var/log/mysql/mysql.log # chown mysql:adm /var/log/mysql/mysql.log # chmod 640 /var/log/mysql/mysql.log After this, I rebooted the machine and when it came back up, I ran mythfilldatabase again. I checked the size of the mysql.log and it was nearly 200MB already! Obviously, there's something wrong. Nothing blatantly sticks out to me in the mysql.log and the mysql.err log is empty. The only thing that I can see are some lines in the log that are duplicated. Some end with: Quote: hostname = 'mythbox' and that makes sense because that's what my box is called, but some entries end withQuote: hostname IS NULL here are a couple examples:Code: 5 Query SELECT data FROM settings WHERE value = 'AutoCommflagWhileRecording' AND hostname = 'mythbox' 5 Query SELECT data FROM settings WHERE value = 'AutoCommflagWhileRecording' AND hostname IS NULL 4 Query SELECT data FROM settings WHERE value = 'AutoExpireLiveTVMaxAge' AND hostname = 'mythbox' 4 Query SELECT data FROM settings WHERE value = 'AutoExpireLiveTVMaxAge' AND hostname IS NULL 4 Query SELECT data FROM settings WHERE value = 'LogEnabled' AND hostname = 'mythbox' 4 Query SELECT data FROM settings WHERE value = 'LogEnabled' AND hostname IS NULL 4 Query SELECT data FROM settings WHERE value = 'RecordPreRoll' AND hostname = 'mythbox' 4 Query SELECT data FROM settings WHERE value = 'RecordPreRoll' AND hostname IS NULL 10 Query SELECT data FROM settings WHERE value = 'MythFillGrabberSuggestsTime' AND hostname = 'mythbox' 10 Query SELECT data FROM settings WHERE value = 'MythFillGrabberSuggestsTime' AND hostname IS NU$ 10 Query SELECT data FROM settings WHERE value = 'MythFillPeriod' AND hostname = 'mythbox' 10 Query SELECT data FROM settings WHERE value = 'MythFillPeriod' AND hostname IS NULL 12 Query UPDATE settings SET data = '7' WHERE value = 'MythFillMinHour' 12 Query UPDATE settings SET data = '9' WHERE value = 'MythFillMaxHour' 12 Query UPDATE settings SET data = '2006-08-11T07:44:04' WHERE value = 'MythFillSuggestedRunTime' 10 Query SELECT data FROM settings WHERE value = 'MasterServerIP' AND hostname = 'mythbox' 10 Query SELECT data FROM settings WHERE value = 'MasterServerIP' AND hostname IS NULL 10 Query SELECT data FROM settings WHERE value = 'MasterServerPort' AND hostname = 'mythbox' 10 Query SELECT data FROM settings WHERE value = 'MasterServerPort' AND hostname IS NULL Also, I have oodles and oodles of entries like this: Code: 12 Query INSERT INTO dd_productioncrew (programid, role, givenname, surname, fullname) VALUES('EPP3803410062','Guest_Star','Romy','Rosemont','Romy Rosemont') along with lots of others that say similar things, but say INSERT INTO dd_schedule, INSERT INTO dd_genre, and so on. There are literally pages and pages of this stuff. I don't know how normal that is. When I use WebMin to look at mythconverg --> settings table --> search field values for "mythfill" and here is what comes back: Code: value data hostname
mythfilldatabaseLastRunStart 2006-08-10 09:58 mythfilldatabaseLastRunEnd 2006-08-10 09:58 mythfilldatabaseLastRunStatus mythfilldatabase ran, but did not insert any new data into the Guide. This can indicate a potential grabber failure. MythFillSuggestedRunTime 2006-08-11T07:44:04 MythFillGrabberSuggestsTime 1 MythFillEnabled 1 MythFillDatabasePath /usr/bin/mythfilldatabase MythFillDatabaseArgs --quiet mythbox MythFillDatabaseLog /var/log/mythfilldatabse.log MythFillPeriod 1 MythFillMinHour 7 MythFillMaxHour 9 The only line with a hostname is the MythFillDatabaseArgs. Everything else is NULL. Could this be the problem? I changed all NULL instances to "mythbox" (without the quotes, of course) and re-ran mythfilldatabase, but I still got the same error about not being able to insert any data. The mysql.log doubled it's size. I tried to clear my capture card and channel info from mythtv-setup as well. That did not do it. I did recently (~ a week ago) get the channels icons setup. I followed the instructions at http://www.mythtvtalk.com/forum/archive/o_t/t_3140/mkiconmap.pl_returns_invalid_postal_code_solved.html, but it only started giving me a problem on Sunday/Monday. It worked just fine for several days. Can anyone think of anything else I can try? |
Author: | ceenvee703 [ Thu Aug 10, 2006 4:30 pm ] |
Post subject: | |
I can't address some of your other issues (as I'm having my own mythfilldatabase problems in another thread) but your runaway MySQL log is a known problem. One way of fixing it is to send the log to /dev/null/ http://mysettopbox.tv/phpBB2/viewtopic.php?t=9261 But the better way is to fix the broken log rotation: http://mysettopbox.tv/phpBB2/viewtopic.php?t=9818 |
Author: | mihanson [ Thu Aug 10, 2006 6:09 pm ] |
Post subject: | |
Thanks for the logrotation tip. I actually got the idea to change the hostname from your thread! I'm grasping for anything at this point... |
Author: | mihanson [ Thu Aug 10, 2006 8:46 pm ] |
Post subject: | |
Ok, I found some errors in my mythbackend.log that may be of help... Code: 2006-08-10 15:35:15.672 DB Error (Error in JobQueue::GetJobCmd()):
Query was: SELECT cmds FROM jobqueue WHERE id = 22; Driver error was [2/2002]: QMYSQL3: Unable to execute query Database error was: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) 2006-08-10 15:35:15.687 DB Error (Error in JobQueue::ChangeJobStatus()): Query was: UPDATE jobqueue SET status = 4, comment = '48% Completed @ 60.3611 fps.' WHERE id = 22; Driver error was [2/2002]: QMYSQL3: Unable to execute query Database error was: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) 2006-08-10 15:35:23.224 DB Error (Error in JobQueue::GetJobCmd()): Query was: SELECT cmds FROM jobqueue WHERE id = 22; Driver error was [2/2002]: QMYSQL3: Unable to execute query Database error was: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) 2006-08-10 15:35:23.237 DB Error (Error in JobQueue::ChangeJobStatus()): Query was: UPDATE jobqueue SET status = 4, comment = '48% Completed @ 60.4198 fps.' WHERE id = 22; Driver error was [2/2002]: QMYSQL3: Unable to execute query Database error was: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) QSqlQuery::exec: database not open 2006-08-10 15:35:30.866 DB Error (KickDatabase): Query was: SELECT NULL; No error type from QSqlError? Strange... QSqlQuery::prepare: database not open QSqlQuery::exec: database not open 2006-08-10 15:35:30.924 DB Error (Error in JobQueue::GetJobCmd()): Query was: SELECT cmds FROM jobqueue WHERE id = :ID; No error type from QSqlError? Strange... 2006-08-10 15:35:30.938 Unable to connect to database! 2006-08-10 15:35:30.941 Driver error was [1/2002]: QMYSQL3: Unable to connect Database error was: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) QSqlQuery::exec: database not open QSqlQuery::exec: database not open 2006-08-10 15:35:30.999 DB Error (KickDatabase): Query was: SELECT NULL; No error type from QSqlError? Strange... QSqlQuery::prepare: database not open QSqlQuery::exec: database not open 2006-08-10 15:35:31.057 DB Error (Error in JobQueue::ChangeJobStatus()): Query was: UPDATE jobqueue SET status = :STATUS, comment = :COMMENT WHERE id = :ID; No error type from QSqlError? Strange... 2006-08-10 15:35:38.595 Unable to connect to database! 2006-08-10 15:35:38.598 Driver error was [1/2002]: QMYSQL3: Unable to connect Database error was: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) QSqlQuery::exec: database not open 2006-08-10 15:35:38.653 DB Error (KickDatabase): Query was: SELECT NULL; No error type from QSqlError? Strange... QSqlQuery::prepare: database not open QSqlQuery::exec: database not open 2006-08-10 15:35:38.707 DB Error (Error in JobQueue::GetJobCmd()): Query was: SELECT cmds FROM jobqueue WHERE id = :ID; No error type from QSqlError? Strange... 2006-08-10 15:35:38.720 Unable to connect to database! 2006-08-10 15:35:38.721 Driver error was [1/2002]: QMYSQL3: Unable to connect Database error was: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) QSqlQuery::exec: database not open QSqlQuery::exec: database not open 2006-08-10 15:35:38.777 DB Error (KickDatabase): Query was: SELECT NULL; No error type from QSqlError? Strange... QSqlQuery::prepare: database not open QSqlQuery::exec: database not open 2006-08-10 15:35:38.831 DB Error (Error in JobQueue::ChangeJobStatus()): Query was: UPDATE jobqueue SET status = :STATUS, comment = :COMMENT WHERE id = :ID; No error type from QSqlError? Strange... 2006-08-10 15:35:46.303 Unable to connect to database! 2006-08-10 15:35:46.313 Driver error was [1/2002]: QMYSQL3: Unable to connect Database error was: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) QSqlQuery::exec: database not open QSqlQuery::exec: database not open 2006-08-10 15:35:46.371 DB Error (KickDatabase): Query was: SELECT NULL; No error type from QSqlError? Strange... QSqlQuery::prepare: database not open QSqlQuery::exec: database not open 2006-08-10 15:35:46.429 DB Error (Error in JobQueue::GetJobCmd()): Query was: SELECT cmds FROM jobqueue WHERE id = :ID; No error type from QSqlError? Strange... 2006-08-10 15:35:46.445 Unable to connect to database! 2006-08-10 15:35:46.447 Driver error was [1/2002]: QMYSQL3: Unable to connect Database error was: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) QSqlQuery::exec: database not open QSqlQuery::exec: database not open 2006-08-10 15:35:46.505 DB Error (KickDatabase): Query was: SELECT NULL; No error type from QSqlError? Strange... QSqlQuery::prepare: database not open QSqlQuery::exec: database not open 2006-08-10 15:35:46.564 DB Error (Error in JobQueue::ChangeJobStatus()): Query was: UPDATE jobqueue SET status = :STATUS, comment = :COMMENT WHERE id = :ID; No error type from QSqlError? Strange... 2006-08-10 15:35:53.963 Unable to connect to database! 2006-08-10 15:35:53.965 Driver error was [1/2002]: QMYSQL3: Unable to connect Database error was: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) These seem to repeat for each attempt mythfilldatabase makes at inserting data into my listings. I'm currently googling, but coming up empty so far. Any ideas anyone? |
Author: | cesman [ Thu Aug 10, 2006 10:08 pm ] |
Post subject: | |
Ok... Is MySQL running? |
Author: | mihanson [ Thu Aug 10, 2006 10:32 pm ] |
Post subject: | |
cesman wrote: Ok... Is MySQL running?
Yes and thank you. Code: mythtv@mythbox:~$ ps ax | grep mysql
3502 ? S 0:00 /bin/sh /usr/bin/mysqld_safe 3538 ? S<l 2:37 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --user=mysql --pid-file=/var/run/mysqld/mysqld.pid --skip-locking --port=3306 --socket=/var/run/mysqld/mysqld.sock 3539 ? S 0:00 logger -p daemon.err -t mysqld_safe -i -t mysqld 18475 ttyp0 S+ 0:00 grep mysql |
Author: | cesman [ Thu Aug 10, 2006 11:09 pm ] |
Post subject: | |
Check the db for errors. |
Author: | mihanson [ Thu Aug 10, 2006 11:46 pm ] |
Post subject: | |
Code: root@mythbox:/var/lib/mysql/mythconverg# /etc/init.d/mythtv-backend stop Stopping MythTV server: mythbackend . root@mythbox:/var/lib/mysql/mythconverg# /etc/init.d/mysql stop Stopping MySQL database server: mysqld. root@mythbox:/var/lib/mysql/mythconverg# myisamchk *.MYI >> mythconverg_check.log No errors were found. Code: root@mythbox:/var/lib/mysql/mythconverg# cat mythconverg_check.log | less
Checking MyISAM file: callsignnetworkmap.MYI Data records: 137 Deleted blocks: 0 - 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 - check record links --------- Checking MyISAM file: capturecard.MYI Data records: 2 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check record links --------- Checking MyISAM file: cardinput.MYI Data records: 2 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check record links --------- Checking MyISAM file: channel.MYI Data records: 142 Deleted blocks: 0 - 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 - check record links --------- Checking MyISAM file: codecparams.MYI Data records: 272 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check record links --------- Checking MyISAM file: credits.MYI Data records: 82543 Deleted blocks: 0 - 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 --------- Checking MyISAM file: dtv_multiplex.MYI Data records: 22 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check record links --------- Checking MyISAM file: dtv_privatetypes.MYI Data records: 48 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check record links --------- Checking MyISAM file: dvdinput.MYI Data records: 8 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check record links --------- Checking MyISAM file: dvdtranscode.MYI Data records: 11 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check record links --------- Checking MyISAM file: favorites.MYI Data records: 0 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 --------- Checking MyISAM file: filemarkup.MYI Data records: 0 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check record links --------- Checking MyISAM file: gallerymetadata.MYI Data records: 0 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check record links --------- Checking MyISAM file: gamemetadata.MYI Data records: 2 Deleted blocks: 0 - 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 - check data record references index: 3 - check data record references index: 4 - check data record references index: 5 - check record links --------- Checking MyISAM file: gameplayers.MYI Data records: 5 Deleted blocks: 0 - 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 - check record links --------- Checking MyISAM file: housekeeping.MYI Data records: 5 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check record links --------- Checking MyISAM file: inuseprograms.MYI Data records: 2 Deleted blocks: 3 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check record links --------- Checking MyISAM file: jobqueue.MYI Data records: 5 Deleted blocks: 2 - 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 - check record links --------- Checking MyISAM file: jumppoints.MYI Data records: 31 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check record links --------- Checking MyISAM file: keybindings.MYI Data records: 198 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check record links --------- Checking MyISAM file: keyword.MYI Data records: 0 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check record links --------- Checking MyISAM file: musicmetadata.MYI Data records: 0 Deleted blocks: 0 - 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 - check data record references index: 3 - check data record references index: 4 - check data record references index: 5 - check data record references index: 6 - check data record references index: 7 - check record links --------- Checking MyISAM file: musicplaylist.MYI Data records: 2 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check record links --------- Checking MyISAM file: mythlog.MYI Data records: 150 Deleted blocks: 1 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check record links --------- Checking MyISAM file: mythweb_sessions.MYI Data records: 3 Deleted blocks: 0 - 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 - check record links --------- Checking MyISAM file: networkiconmap.MYI Data records: 137 Deleted blocks: 0 - 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 - check record links --------- Checking MyISAM file: newssites.MYI Data records: 0 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check record links --------- Checking MyISAM file: oldfind.MYI Data records: 11 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 --------- Checking MyISAM file: oldprogram.MYI Data records: 5997 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check record links --------- Checking MyISAM file: oldrecorded.MYI Data records: 338 Deleted blocks: 0 - 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 - check data record references index: 3 - check data record references index: 4 - check data record references index: 5 - check data record references index: 6 - check record links --------- Checking MyISAM file: people.MYI Data records: 34528 Deleted blocks: 0 - 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 --------- Checking MyISAM file: phonecallhistory.MYI Data records: 0 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check record links --------- Checking MyISAM file: phonedirectory.MYI Data records: 1 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check record links --------- Checking MyISAM file: pidcache.MYI Data records: 311 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 --------- Checking MyISAM file: playgroup.MYI Data records: 1 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check record links --------- Checking MyISAM file: profilegroups.MYI Data records: 9 Deleted blocks: 0 - 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 - check record links --------- Checking MyISAM file: program.MYI Data records: 41608 Deleted blocks: 10 - 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 - check data record references index: 3 - check data record references index: 4 - check data record references index: 5 - check data record references index: 6 - check data record references index: 7 - check record links --------- Checking MyISAM file: programgenres.MYI Data records: 56023 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 --------- Checking MyISAM file: programrating.MYI Data records: 14546 Deleted blocks: 0 - 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 --------- Checking MyISAM file: recgrouppassword.MYI Data records: 0 Deleted blocks: 0 - 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 - check record links --------- Checking MyISAM file: record.MYI Data records: 23 Deleted blocks: 0 - 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 - check data record references index: 3 - check data record references index: 4 - check data record references index: 5 - check record links --------- Checking MyISAM file: record_tmp.MYI Data records: 23 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check record links --------- Checking MyISAM file: recorded.MYI Data records: 13 Deleted blocks: 12 - 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 - check data record references index: 3 - check data record references index: 4 - check data record references index: 5 - check data record references index: 6 - check record links --------- Checking MyISAM file: recordedcredits.MYI Data records: 55 Deleted blocks: 22 - 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 --------- Checking MyISAM file: recordedmarkup.MYI Data records: 399602 Deleted blocks: 17535 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check record links --------- Checking MyISAM file: recordedprogram.MYI Data records: 56 Deleted blocks: 7 - 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 - check data record references index: 3 - check data record references index: 4 - check data record references index: 5 - check data record references index: 6 - check data record references index: 7 - check record links --------- Checking MyISAM file: recordedrating.MYI Data records: 26 Deleted blocks: 2 - 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 --------- Checking MyISAM file: recordingprofiles.MYI Data records: 29 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check record links --------- Checking MyISAM file: recordmatch.MYI Data records: 57 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 --------- Checking MyISAM file: romdb.MYI Data records: 0 Deleted blocks: 0 - 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 - check data record references index: 3 - check data record references index: 4 - check data record references index: 5 - check data record references index: 6 - check record links --------- Checking MyISAM file: schemalock.MYI Data records: 0 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference --------- Checking MyISAM file: settings.MYI Data records: 397 Deleted blocks: 1 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check record links --------- Checking MyISAM file: smartplaylist.MYI Data records: 8 Deleted blocks: 0 - 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 - check data record references index: 3 - check record links --------- Checking MyISAM file: smartplaylistcategory.MYI Data records: 3 Deleted blocks: 0 - 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 - check record links --------- Checking MyISAM file: smartplaylistitem.MYI Data records: 8 Deleted blocks: 0 - 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 - check record links --------- Checking MyISAM file: tvchain.MYI Data records: 70 Deleted blocks: 9 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check record links --------- Checking MyISAM file: videobookmarks.MYI Data records: 0 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check record links --------- Checking MyISAM file: videocategory.MYI Data records: 5 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check record links --------- Checking MyISAM file: videocountry.MYI Data records: 5 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check record links --------- Checking MyISAM file: videogenre.MYI Data records: 18 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check record links --------- Checking MyISAM file: videometadata.MYI Data records: 35 Deleted blocks: 0 - 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 - check data record references index: 3 - check data record references index: 4 - check record links --------- Checking MyISAM file: videometadatacountry.MYI Data records: 37 Deleted blocks: 0 - 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 --------- Checking MyISAM file: videometadatagenre.MYI Data records: 76 Deleted blocks: 0 - 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 --------- Checking MyISAM file: videosource.MYI Data records: 2 Deleted blocks: 0 - 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 - check record links --------- Checking MyISAM file: videotypes.MYI Data records: 9 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check record links --------- Checking MyISAM file: websites.MYI Data records: 19 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check record links --------- Checking MyISAM file: xvmc_buffer_settings.MYI Data records: 2 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check record links |
Author: | mihanson [ Fri Aug 11, 2006 12:25 am ] |
Post subject: | |
Well, with the help of dmcman in this thread I was able to get those ugly MySQL errors that I had in my mythtvbackend.log to cease. To quickly summerize: I stopped the backend & mysql. Ensured no instance of mysql was running with ps. Move the mysqld.sock file to another location. Started mysql in safe mode. Verified a new mysqld.sock was created (yes) and then rebooted my box. After the reboot, I ran mythfilldatabase again, but I'm still getting the error: Quote: Last mythfilldatabase run started on 2006-08-10 23:06 and ended on 2006-08-10 23:06. mythfilldatabase ran, but did not insert any new data into the Guide. This can indicate a potential grabber failure.
Hmmm.... ![]() |
Author: | sjwanta [ Mon Aug 14, 2006 3:34 pm ] |
Post subject: | Any luck? |
I am getting the same error ("mythfilldatabase ran, but did not insert any new data into the Guide. This can indicate a potential grabber failure."). The only difference seems to be that my MySQL log was half the size (450MB). I followed the steps from this thread, and am still getting the mythfilldatabase error. Before this started, I made no changes to any settings, I have only used MythTV for watching and recording television programs. Has anyone had any luck in troubleshooting this yet? My setup: Knoppmyth R5C7 (clean install) AMD Athlon 2800+ (2.0 GhZ) * 512 MB WinTV PVR-350 ~250 GB storage using LVM across 2 PATA drives. |
Author: | mihanson [ Mon Aug 14, 2006 7:25 pm ] |
Post subject: | |
I'm still getting te error (mythfill ran, but did not insert) sporadically. One day it will say "successful" the next 2 days it will have the error. I'm giving it time to see if it will work itself out. |
Author: | sjwanta [ Tue Aug 15, 2006 2:21 pm ] |
Post subject: | It worked once, but not again. |
Thanks. It sounds like we're having the exact same problem. It ran successfully last night, but only inserted 1 day (for a total of 13 total days of info, it is set to grab 14 days). This morning, I had the same error as before (and down to 12 days of info). I wonder if this is an error on the content provider's end. I'll keep this thread updated if anything changes. sjw |
Author: | mihanson [ Sun Aug 27, 2006 8:10 pm ] |
Post subject: | |
Yes, mine has only been keeping 12 days of advance programing. I don't know why, but as long as it keeps being "sucessful," 12 days is plenty for me. There is some info on Zap2It's message board. It seems that it's a Zap2It issue and they're working on it. |
Page 1 of 1 | All times are UTC - 6 hours |
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |