Upgraded mySQL to 5.5.34 via cPanel, get #2002 Cannot log in to the MySQL server

Jesse Smith

Member
Dec 12, 2013
5
0
1
cPanel Access Level
Website Owner
Trying to log in to phpMyAdmin generates...

#2002 Cannot log in to the MySQL server

SSH generates...

Code:
-bash-3.2# mysql
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
-bash-3.2# service mysql start
Starting MySQL... ERROR! The server quit without updating PID file (/var/lib/mysql/wor.domain.com.pid).

and if it will help...

-bash-3.2# tail -n 50 /var/lib/mysql/`hostname`.err
131219 22:37:10 [ERROR] /usr/sbin/mysqld: unknown variable 'record_buffer=1M'
131219 22:37:10 [ERROR] Aborting

131219 22:37:10  InnoDB: Starting shutdown...
131219 22:37:10  InnoDB: Shutdown completed; log sequence number 2481200
131219 22:37:10 [Note] /usr/sbin/mysqld: Shutdown complete

131219 22:37:10 mysqld_safe mysqld from pid file /var/lib/mysql/wor.domain.com.pid ended
131219 22:42:09 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
131219 22:42:10 [Warning] Using unique option prefix join_buffer instead of join_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
131219 22:42:10 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
131219 22:42:10 [Note] Plugin 'FEDERATED' is disabled.
131219 22:42:10 InnoDB: The InnoDB memory heap is disabled
131219 22:42:10 InnoDB: Mutexes and rw_locks use GCC atomic builtins
131219 22:42:10 InnoDB: Compressed tables use zlib 1.2.3
131219 22:42:10 InnoDB: Using Linux native AIO
131219 22:42:10 InnoDB: Initializing buffer pool, size = 128.0M
131219 22:42:10 InnoDB: Completed initialization of buffer pool
131219 22:42:10 InnoDB: highest supported file format is Barracuda.
131219 22:42:10  InnoDB: Waiting for the background threads to start
131219 22:42:11 InnoDB: 5.5.34 started; log sequence number 2481200
131219 22:42:11 [ERROR] /usr/sbin/mysqld: unknown variable 'record_buffer=1M'
131219 22:42:11 [ERROR] Aborting

131219 22:42:11  InnoDB: Starting shutdown...
131219 22:42:11  InnoDB: Shutdown completed; log sequence number 2481200
131219 22:42:11 [Note] /usr/sbin/mysqld: Shutdown complete

131219 22:42:11 mysqld_safe mysqld from pid file /var/lib/mysql/wor.domain.com.pid ended
131219 22:47:11 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
131219 22:47:11 [Warning] Using unique option prefix join_buffer instead of join_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
131219 22:47:11 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
131219 22:47:11 [Note] Plugin 'FEDERATED' is disabled.
131219 22:47:11 InnoDB: The InnoDB memory heap is disabled
131219 22:47:11 InnoDB: Mutexes and rw_locks use GCC atomic builtins
131219 22:47:11 InnoDB: Compressed tables use zlib 1.2.3
131219 22:47:11 InnoDB: Using Linux native AIO
131219 22:47:11 InnoDB: Initializing buffer pool, size = 128.0M
131219 22:47:11 InnoDB: Completed initialization of buffer pool
131219 22:47:11 InnoDB: highest supported file format is Barracuda.
131219 22:47:11  InnoDB: Waiting for the background threads to start
131219 22:47:12 InnoDB: 5.5.34 started; log sequence number 2481200
131219 22:47:12 [ERROR] /usr/sbin/mysqld: unknown variable 'record_buffer=1M'
131219 22:47:12 [ERROR] Aborting

131219 22:47:12  InnoDB: Starting shutdown...
131219 22:47:13  InnoDB: Shutdown completed; log sequence number 2481200
131219 22:47:13 [Note] /usr/sbin/mysqld: Shutdown complete

131219 22:47:13 mysqld_safe mysqld from pid file /var/lib/mysql/wor.domain.com.pid ended
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,880
2,261
463
Hello :)

The relevant error message here is:

Code:
[ERROR] /usr/sbin/mysqld: unknown variable 'record_buffer=1M'
Remove that value from your /etc/my.cnf file and then restart MySQL.

Thank you.