Run

 killall mysqld

as root

_________________
Paid support
How to ask for help
1. Give details of your problem
2. Post any errors
3. Post relevant logs.
4. Don't hide details i.e. your domain, it just makes things harder
5. Be polite or you'll be eaten by a grue

Oh boy is my face red. I had put in "TABLES" instead of "TABLE" and got this error:

[ERROR] Wrong option to log-output. Option(s) given: TABLES
Alternatives are: 'NONE','FILE','TABLE'

The good news is finally I found something I could debug on my own!

One question about this, after I put the command "/usr/sbin/mysqld" in, it gives a couple warnings:

120116 11:20:08 [Warning] option 'thread_stack': unsigned value 65536 adjusted t                                                                                       o 131072
120116 11:20:09 [Warning] Although a path was specified for the --log_slow_queri                                                                                       es option, log tables are used. To enable logging to files use the --log-output=                                                                                       file option.

And then just hangs in PuTTY for me. I have to actually close the window and start PuTTY up again. MySQL does start mind you so it's mostly just an annoyance for me.

_________________
Andrew G Johnson
http://www.andrewgjohnson.com

Btw I should note that my CPU and IO are both down since I started all this so a big thanks to obs and hybinet I think we've already come a ways.

Here are the graphs:

CPU: http://screensnapr.com/e/uONRPR.png
IO: http://screensnapr.com/e/jaVFGH.png

Also here is my IPv6 traffic graph: http://screensnapr.com/e/k8mtXz.png Kind of odd but since I did the upgrade to the better linode some activity is hovering in it. Is this any cause for concern?

_________________
Andrew G Johnson

http://www.andrewgjohnson.com

You can ignore those warnings, also it's not hanging putty it's just running the mysql daemon as it should do, this was just a diagnostic command so output was printed to the screen, you should go back to using the start|restart|stop mysql command now everything is working.

For IPv6 you probably have some daemon using it, ntp would be a good guess

If you run

netstat -lpntu6

it'll tell you what's listening on ipv6 (replace the 6 with a 4 for ipv4 traffic and omit the number to show both)

Personally I just block all ipv6 traffic with iptables if I'm not going to use it.

_________________
Paid support
How to ask for help
1. Give details of your problem
2. Post any errors
3. Post relevant logs.
4. Don't hide details i.e. your domain, it just makes things harder
5. Be polite or you'll be eaten by a grue