Reply to thread

Message

<blockquote data-quote="CathodeRay" data-source="post: 1148183" data-attributes="member: 128074">Since we're so keen on observation here rather than guessing, my observation was that MyISAM to innoDB was the only action that immediately caused mysql to start normally (and so tvserver). Something had changed, and the only thing that had changed was the conversion. Call it a conversion rather than a repair, but something changed, and so the key question is what changed to allow mysql to start normally?Actually, that is what happened. I'm not a complete idiot. I did start and stop the mysql service several times - I do know about the importance of repeatability (and anyway I couldn't believe it was working!) - and each start (and stop) took two or three seconds, but once I started tvserver and it had done its mischief it was back to two minute mysql starts and tvserver not starting.Not necessarily. The mptvdb was created by MP's tv-config, tvserver was running (obviously). I've already done this. The ib_logfiles were around 50MB but that seems to be set by mysql, the [pc-name].err file was 555KB, now 2KB. Purging these files made no difference.Since all the tables are now innoDB tables, I can't convert them to innoDB again (though I suppose I could convert them back to MyISAM and then back to innoDB but I might lose the will to live before fininishing that) to repeat the observation that converting to innoDB does cause a normal mysql start until such time as tvserver acts on mptvdb. Doing the conversion table by table in a GUI is safer but tedious. I guess there is a (set of)sql commands that will do it but as we all know one typo and it's sql hell.I will see what I can do to replicate the mysql quick start &gt; run tvserver &gt; mysql slow starts behaviour.Pity a change to sqlite isn't a straight forward option.</blockquote>

[QUOTE="CathodeRay, post: 1148183, member: 128074"] Since we're so keen on observation here rather than guessing, my observation was that MyISAM to innoDB was the only action that immediately caused mysql to start normally (and so tvserver). Something had changed, and the only thing that had changed was the conversion. Call it a conversion rather than a repair, but something changed, and so the key question is what changed to allow mysql to start normally? Actually, that is what happened. I'm not a complete idiot. I did start and stop the mysql service several times - I do know about the importance of repeatability (and anyway I couldn't believe it was working!) - and each start (and stop) took two or three seconds, but once I started tvserver and it had done its mischief it was back to two minute mysql starts and tvserver not starting. Not necessarily. The mptvdb was created by MP's tv-config, tvserver was running (obviously). I've already done this. The ib_logfiles were around 50MB but that seems to be set by mysql, the [pc-name].err file was 555KB, now 2KB. Purging these files made no difference. Since all the tables are now innoDB tables, I can't convert them to innoDB again (though I suppose I could convert them back to MyISAM and then back to innoDB but I might lose the will to live before fininishing that) to repeat the observation that converting to innoDB does cause a normal mysql start until such time as tvserver acts on mptvdb. Doing the conversion table by table in a GUI is safer but tedious. I guess there is a (set of)sql commands that will do it but as we all know one typo and it's sql hell. I will see what I can do to replicate the mysql quick start > run tvserver > mysql slow starts behaviour. Pity a change to sqlite isn't a straight forward option. [/QUOTE]

Verification