If you have received this communication in error, please notify us immediately by reply e-mail and destroy all copies of the original message. After a good 20 minutes spent on Google trying various things (hunting down the mysql.plugin file to verify its permissions, removing my file, verifying my file was getting erased, etc), I finally stumbled upon the answer: My SQL was still running under a different hostname.however I wanted to mention this in case anyone else run into this issue.I would also like to Thank Jeff @ No Baloney for his warm voice and a few quick jokes while speaking with him on the phone.but please dont do this 'rm -rf *' under /tmp..may again cause some other unforeseen issues.../tmp is critically used by processes and removing files may cause them to abort or non-responding.It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured.
Hi, SQL was running well until I tried to make a restart and it won't get started any longer.
We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail.
----------------------------------------- Confidentiality Notice: The following mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information.
It's always a laugh or three when talking to Jeff and since this was a critical server (high traffic) I thought first to call him to see if he has hit this yet...
and in fact he had, however it would be nice to understand the exact details here and how we can prevent this for the common user in the future.