Reply to thread

I realise the MyISAM to innoDB conversion isn't a repair per se, the question I had was whether re-writing the tables (the filesizes get much larger after the conversion) in effect amounted to a repair. The fact is that, immediately after the conversion, but not subsequently, MySQL and tvserver started normally. The implication is that the conversion changed something for the better, but running MP then corrupted it again. I also appreciate when a bit of computer code reports 'All OK' that can sometimes mean 'All pigs fed and ready to fly'. The proof, as another phrase has it, is in the pudding. If MySQL hangs on starting then 'All is Not OK', full stop.

As mentioned earlier, I've already done the drop database routine (I didn't bother to export the data in case it was somehow corrupt) and then recreated mptvdb by running tv-config, rescanning for channels etc. By default, MP points to a system partition recordings folder which I have changed to one on another partition, so I had to reimport my recordings after pointing MP to my recordings folder. The newly created mptvdb made no difference.

The MySQL log files don't reveal much. Here are the entries for yesterday evening and this morning:

150813 20:16:47 [Note] Plugin 'FEDERATED' is disabled.

150813 20:18:42  InnoDB: Started; log sequence number 0 6911736

150813 20:18:42 [Note] Event Scheduler: Loaded 0 events

150813 20:18:42 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld.exe: ready for connections.

Version: '5.1.38-community'  socket: ''  port: 3306  MySQL Community Server (GPL)

150813 20:19:51 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld.exe: Normal shutdown

150813 20:19:51 [Note] Event Scheduler: Purging the queue. 0 events

150813 20:19:51  InnoDB: Starting shutdown...

150813 20:19:52  InnoDB: Shutdown completed; log sequence number 0 6911746

150813 20:19:52 [Warning] Forcing shutdown of 1 plugins

150813 20:19:52 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld.exe: Shutdown complete

150813 20:21:38 [Note] Plugin 'FEDERATED' is disabled.

150813 20:23:33  InnoDB: Started; log sequence number 0 6911746

150813 20:23:33 [Note] Event Scheduler: Loaded 0 events

150813 20:23:33 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld.exe: ready for connections.

Version: '5.1.38-community'  socket: ''  port: 3306  MySQL Community Server (GPL)

150813 22:49:09 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld.exe: Normal shutdown

150813 22:49:09 [Note] Event Scheduler: Purging the queue. 0 events

150813 22:49:11 [Warning] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld.exe: Forcing close of thread 2  user: 'root'

150813 22:49:11 [Warning] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld.exe: Forcing close of thread 1  user: 'root'

150813 22:49:11  InnoDB: Starting shutdown...

150813 22:49:13  InnoDB: Shutdown completed; log sequence number 0 7011219

150813 22:49:13 [Warning] Forcing shutdown of 1 plugins

150813 22:49:13 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld.exe: Shutdown complete

150814  7:22:17 [Note] Plugin 'FEDERATED' is disabled.

150814  7:24:12  InnoDB: Started; log sequence number 0 7011219

150814  7:24:12 [Note] Event Scheduler: Loaded 0 events

150814  7:24:12 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld.exe: ready for connections.

Version: '5.1.38-community'  socket: ''  port: 3306  MySQL Community Server (GPL)

The only [Warnings] (which have been around for ages, from long before the problems started last week) are

Forcing close of thread x user: 'root'

Forcing shutdown of 1 plugins

but as I say these aren't new. But then again, maybe 'forcing close/forcing shutdown' is what does the damage?

Other parts of MP use sqlite successfully, and Lehmden reports using it with MP2 by implication with tvserver. I wonder if it is possible to use it with tvserver in MP1, ie get shot of that blasted MySQL once and forever?