MySQL server wont' start. Reason: Internal error The very vague error message

Reason: Internal error

I've had this happen before, and it usually fixes itself after I restart my machine, but after the 4th time now it still is showing the error :(

Update: Found my.cnf file, details below:

port = 3306
socket = /tmp/mysql.sock

[mysqld]
port = 3306
socket = /tmp/mysql.sock
skip-external-locking
key_buffer_size = 384M
max_allowed_packet = 128M
table_open_cache = 512
sort_buffer_size = 2M
read_buffer_size = 2M
read_rnd_buffer_size = 8M
myisam_sort_buffer_size = 64M
thread_cache_size = 8
query_cache_size = 32M
thread_concurrency = 4
innodb = on
innodb_data_home_dir = /var/lib/mysql
innodb_data_file_path = ibdata1:512M:autoextend
innodb_log_group_home_dir = /var/lib/mysql
innodb_buffer_pool_size = 1024M
innodb_additional_mem_pool_size = 256M
innodb_log_file_size = 256M
innodb_log_buffer_size = 8M
"my.cnf" [readonly] 67L, 1336C
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50
default-storage-engine = innodb
datadir=/var/lib/mysql
user = mysql
symbolic-links = 0
transaction-isolation = READ-COMMITTED
max_length_for_sort_data = 8388608
max_sort_length = 8388608
group_concat_max_len = 32M

net_buffer_length = 1M
max_connections = 32768
back_log = 32768

[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
open-files-limit = 8192

[mysqldump]
quick
max_allowed_packet = 32M

[mysql]
#no-auto-rehash
database = whoat
#safe-updates
[myisamchk]
key_buffer_size = 256M
sort_buffer_size = 256M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout


Any idea what is going on? Here is the server log





I was able to start SQL from MySQL Workbench, would like to know how I breached the max open file limit however
This has happened to me before and while there's nothing in the logs to really point you in the right direction the first place to start is in the MySQL's configuration file (On a Mac, I believe it is called my.cnf and it is found in /etc).

You may have made some adjustments or tweaks that it doesn't agree with. Going a bit overboard with certain values (max_open_files for example you're requesting 33802 out of the maximum of 8192, this could be the culprit) can lead to this scenario where MySQL just doesn't want to kick off.

Take a look inside your conf file and try editing the values to be your defaults. You may be able to find example files here: /usr/local/mysql/support-files/

Once you fix it and wish to tweak, just tweak one at a time and start MySQL to confirm it can run with that desired change. It's a little more time consuming but it helps avoid scenarios like this in the future.