Reply to thread

Message

Okay. From the log files it looks like the way that you're turning off the PC is not "safe". In other words, Windows doesn't appear to be shutting down (and thereby stopping the TV service etc.) in a proper fashion.
How exactly are you turning off or restarting? I mean, are you using the Windows start menu, physically pressing the power or reset button on the PC case, or...?

Yes, that's understood.
My suspicion at this point is that your "apparently-unsafe" shutdown/reboot procedure is negatively affecting MySQL on each shutdown/reboot. So, the previous check + autorepair is superseded.

Speculation here... but I would guess that Windows asks MySQL to start, waits awhile, thinks MySQL has hung because it hasn't completed starting yet, logs the error, doesn't start TV service as a result... and then carries on with booting. Eventually MySQL finishes whatever it is doing and thereby enters the "running" state. Finally, when you come along and check, you think everything is fine and wonder why TV service hasn't started.

Well, the question about why MySQL is not happy is the million dollar question.
As above: at this point it looks like it could be because you're not shutting it (both MySQL and the PC) down cleanly on a frequent basis. I assume you're aware that it is not reasonable to expect to be able to hard-power-off (effectively: pull the plug) a PC without consequences? It looks like that's what you're doing... and therefore I'm not surprised to see that MySQL is suffering. There could well be other consequences too that I haven't noticed.

If the problem persisted after changing your shutdown procedure I would be running the check + auto-repair again, and checking the MySQL logs to see what it is doing that is taking so long.

In my opinion swapping DBs would be premature... and possibly pointless if the problem is your shutdown procedure.

<blockquote data-quote="mm1352000" data-source="post: 1148068" data-attributes="member: 82144">Okay. From the log files it looks like the way that you're turning off the PC is not &quot;safe&quot;. In other words, Windows doesn't appear to be shutting down (and thereby stopping the TV service etc.) in a proper fashion.How exactly are you turning off or restarting? I mean, are you using the Windows start menu, physically pressing the power or reset button on the PC case, or...?Yes, that's understood.My suspicion at this point is that your &quot;apparently-unsafe&quot; shutdown/reboot procedure is negatively affecting MySQL on each shutdown/reboot. So, the previous check + autorepair is superseded.Speculation here... but I would guess that Windows asks MySQL to start, waits awhile, thinks MySQL has hung because it hasn't completed starting yet, logs the error, doesn't start TV service as a result... and then carries on with booting. Eventually MySQL finishes whatever it is doing and thereby enters the &quot;running&quot; state. Finally, when you come along and check, you think everything is fine and wonder why TV service hasn't started.Well, the question about why MySQL is not happy is the million dollar question.As above: at this point it looks like it could be because you're not shutting it (both MySQL and the PC) down cleanly on a frequent basis. I assume you're aware that it is not reasonable to expect to be able to hard-power-off (effectively: pull the plug) a PC without consequences? It looks like that's what you're doing... and therefore I'm not surprised to see that MySQL is suffering. There could well be other consequences too that I haven't noticed.If the problem persisted after changing your shutdown procedure I would be running the check + auto-repair again, and checking the MySQL logs to see what it is doing that is taking so long.In my opinion swapping DBs would be premature... and possibly pointless if the problem is your shutdown procedure.</blockquote>

[QUOTE="mm1352000, post: 1148068, member: 82144"] Okay. From the log files it [I]looks[/I] like the way that you're turning off the PC is not "safe". In other words, Windows doesn't appear to be shutting down (and thereby stopping the TV service etc.) in a proper fashion. How exactly are you turning off or restarting? I mean, are you using the Windows start menu, physically pressing the power or reset button on the PC case, or...? Yes, that's understood. My suspicion at this point is that your "apparently-unsafe" shutdown/reboot procedure is negatively affecting MySQL [B]on each shutdown/reboot[/B]. So, the previous check + autorepair is superseded. Speculation here... but I would guess that Windows asks MySQL to start, waits awhile, thinks MySQL has hung because it hasn't [I]completed [/I]starting yet, logs the error, doesn't start TV service as a result... and then carries on with booting. Eventually MySQL finishes whatever it is doing and thereby enters the "running" state. Finally, when you come along and check, you think everything is fine and wonder why TV service hasn't started. Well, the question about why MySQL is not happy is the million dollar question. As above: at this point it looks like it could be because you're not shutting it (both MySQL and the PC) down cleanly on a frequent basis. I assume you're aware that it is not reasonable to expect to be able to hard-power-off (effectively: pull the plug) a PC without consequences? It looks like that's what you're doing... and therefore I'm not surprised to see that MySQL is suffering. There could well be other consequences too that I haven't noticed. If the problem persisted after changing your shutdown procedure I would be running the check + auto-repair again, and checking the MySQL logs to see what it is doing that is taking so long. In my opinion swapping DBs would be premature... and possibly pointless if the problem is your shutdown procedure. [/QUOTE]