Starting mysql manager of pid file quit without updating

var hatena_jsonp_base = ' var jsr = new JSONscript Request(hatena_jsonp_base '?

Python, Lua, Tcl, C and C training - public course schedule [here]Private courses on your site - see [here]Please ask about maintenance training for Perl, PHP, Java, Ruby, My SQL and Linux / Tomcat systems I got an email a couple of hours ago ...

Not sure why, which frightens me, but I'm working from a cruise boat with a poor connection and the important thing was to fix it.

It appears that what's happened is that the My SQL daemon has stopped catastrophically for some reason.

It's confused into thinkig it should be referring to a PID file which didn't exist, and because it's crashed, it's refusing to restart. Ensure that /etc/contains: And restart the server as this will overstep the problem above, and also recover the databases; error recovery levels of 1 or 2 are likely to let you recover (almost) everything we're told, and I have the previous good backup anyway, so I can restore if I need to.

Therefore, I need to start it again after the update is done. During the system upgrade, the OS may disable some of your daemons.

Unfortunately, the upgrade process is not smooth every time. Instead of troubleshooting each one by one, the easiest way is to start everything over.