Bug #14411 mysql cannot connect to mysql.sock when innodb_log_file_size is enabled!

• Submitted: 27 Oct 2005 21:23
• Modified: 27 Oct 2005 23:50
• Reporter: Hugh McLenaghan
• Status: Not a Bug
• Category: MySQL Server
• Severity: S3 (Non-critical)
• Version: mysql-4.1.13
• OS: Linux (SuSE 10.0)
• Assigned to: MySQL Verification Team
• CPU Architecture: Any

[27 Oct 2005 21:23] Hugh McLenaghan

Description:
This is a strange one!

when trying to run mysql get this:-

   ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111)

How to repeat:
Install SuSE 10.0, and mySQL 4.1.13 packages from the distribution.

Now create /etc/my.cnf with this:-

# Uncomment the following if you are using InnoDB tables
innodb_data_home_dir = /var/lib/mysql/
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = /var/lib/mysql/
innodb_log_arch_dir = /var/lib/mysql/
innodb_buffer_pool_size = 128M
innodb_additional_mem_pool_size = 20M
innodb_log_file_size = 8M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50
innodb_file_per_table

stop/restart mysqld

at prompt #:-   
  #  mysql

Suggested fix:
I commented out the file and slowly added each line back until it broke.

The line that caused the problem:-

 #innodb_log_file_size=64M

I don't know how this will effect the running system, but once I commented it out I could then run mysql from command prompt (after stopping/restarting mysqld).

[27 Oct 2005 23:50] MySQL Verification Team

We're sorry, but the bug system is not the appropriate forum for 
asking help on using MySQL products. Your problem is not the result 
of a bug.

Support on using our products is available both free in our forums
at http://forums.mysql.com and for a reasonable fee direct from our
skilled support engineers at http://www.mysql.com/support/

Thank you for your interest in MySQL.