Mysql.sock Problem ( mysqld.sock' (2) )

[theprincy]

I have this problem on a server, I have unsuccessfully tried all the solutions that are being asked to be here on the forum and on google, I changed the settings in the my.cnf file on the socks but nothing has changed ... files below my.cnf, and mysql.err mysql.info

Code:

# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port            = 3306
socket          = /var/run/mysql/mysqld.sock

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket          = /var/run/mysql/mysqld.sock
nice            = 0

[mysqld]
#
# * Basic Settings
#
user            = mysql
pid-file        = /var/run/mysql/mysqld.pid
socket          = /var/run/mysql/mysqld.sock
port            = 3306
basedir         = /usr
datadir         = /var/lib/mysql
tmpdir          = /tmp
language        = /usr/share/mysql/english
skip-external-locking
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
#bind-address           = 127.0.0.1
#
# * Fine Tuning
#
key_buffer              = 16M
max_allowed_packet      = 16M
thread_stack            = 128K
thread_cache_size       = 8
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover          = BACKUP
#max_connections        = 100
#table_cache            = 64
#thread_concurrency     = 10
#
# * Query Cache Configuration
#
query_cache_limit       = 1M
query_cache_size        = 16M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
#log            = /var/log/mysql/mysql.log
#
# Error logging goes to syslog. This is a Debian improvement :)
#
# Here you can see queries with especially long duration
#log_slow_queries       = /var/log/mysql/mysql-slow.log
#long_query_time = 2
#log-queries-not-using-indexes
#
# The following can be used as easy to replay backup logs or for replication.
# note: if you are setting up a replication slave, see README.Debian about
#       other settings you may need to change.
#server-id              = 1
#log_bin                        = /var/log/mysql/mysql-bin.log
expire_logs_days        = 10
max_binlog_size         = 100M
#binlog_do_db           = include_database_name
#binlog_ignore_db       = include_database_name
#
# * BerkeleyDB
#
# Using BerkeleyDB is now discouraged as its support will cease in 5.1.12.
skip-bdb
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
# You might want to disable InnoDB to shrink the mysqld process by circa 100MB.
#skip-innodb
#
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
#
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem



[mysqldump]
quick
quote-names
max_allowed_packet      = 16M

[mysql]
#no-auto-rehash # faster start of mysql but no tab completition

[isamchk]
key_buffer              = 16M

#
# * NDB Cluster
#
# See /usr/share/doc/mysql-server-*/README.Debian for more information.
#
# The following configuration is read by the NDB Data Nodes (ndbd processes)
# not from the NDB Management Nodes (ndb_mgmd processes).
#
# [MYSQL_CLUSTER]
# ndb-connectstring=127.0.0.1


#
# * IMPORTANT: Additional settings that can override those from this file!
#   The files must end with '.cnf', otherwise they'll be ignored.
#
!includedir /etc/mysql/conf.d/

/var/log/mysql.log 0 byte

/var/log/mysql.err 0 byte

Note also if file my.cnf , you can see a different address mysql always just look in '/var/run/mysqld/ the file socks , how can it be?

---

/var/log/syslog

Code:

Nov 29 11:07:17 london mysqld_safe[27531]: A mysqld process already exists
Nov 29 11:07:31 london /etc/init.d/mysql[27696]: 1 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Nov 29 11:07:31 london /etc/init.d/mysql[27696]: #007/usr/bin/mysqladmin: connect to server at 'localhost' failed
Nov 29 11:07:31 london /etc/init.d/mysql[27696]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
Nov 29 11:07:31 london /etc/init.d/mysql[27696]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Nov 29 11:07:31 london /etc/init.d/mysql[27696]:

ps aux

Code:

mysql    26488  0.0  0.9 160112 20492 pts/1    Sl   10:53   0:00 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --user=mysql --pid-file=/var/run/mysql/mysqld.pid --.....

I tried to kill the process, but reboots itself

[kilburn]

So, you changed the socket path from "/var/run/mysqld/mysqld.sock" to "/var/run/mysql/mysqld.sock" in your /etc/mysql/my.cnf file. Nevertheless:

1. You forgot to update /etc/mysql/debian.cnf as stated in the my.cnf file (see the following for reference

Code:

# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port            = 3306
socket          = /var/run/mysql/mysqld.sock

2. Are you sure that the /var/run/mysql folder exists and is owned by the mysql user/group? I bet it doesn't

Anyway, why did you choose to change the socket path to begin with?

[theprincy]

(11-29-2010 09:21 PM)kilburn Wrote:  So, you changed the socket path from "/var/run/mysqld/mysqld.sock" to "/var/run/mysql/mysqld.sock" in your /etc/mysql/my.cnf file. Nevertheless:

1. You forgot to update /etc/mysql/debian.cnf as stated in the my.cnf file (see the following for reference

Code:

# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port            = 3306
socket          = /var/run/mysql/mysqld.sock

cat /etc/mysql/debian.cnf
# Automatically generated for Debian scripts. DO NOT TOUCH!
[client]
host = localhost
user = debian-sys-maint
password =
socket = /var/run/mysql/mysqld.sock
[mysql_upgrade]
user = debian-sys-maint
password =
socket = /var/run/mysql/mysqld.sock
basedir = /usr

(11-29-2010 09:21 PM)kilburn Wrote:  2. Are you sure that the /var/run/mysql folder exists and is owned by the mysql user/group? I bet it doesn't

Anyway, why did you choose to change the socket path to begin with?

yes

ls -asl /var/run/mysql
totale 12K
4,0K drwxr-xr-x 2 mysql root 4,0K 29 nov 10:53 .
4,0K drwxr-xr-x 14 root root 4,0K 29 nov 09:45 ..
4,0K -rw-rw---- 1 mysql mysql 6 29 nov 10:53 mysqld.pid
0 srwxrwxrwx 1 mysql mysql 0 29 nov 10:53 mysqld.sock


---------


Stopping MySQL database server: mysqld.
Starting MySQL database server: mysqld.
Checking for corrupt, not cleanly closed and upgrade needing tables..
---
Connection failed: SQLSTATE[HY000] [2002] Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)

---

but if I access via terminal

mysql -uroot -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 2783
Server version: 5.0.51a-24+lenny4 (Debian)

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql>

[kilburn]

From the default /etc/init.d/mysql file (debian lenny):

Code:

MYADMIN="/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf"
[...]
mysqld_status () {
    ping_output=`$MYADMIN ping 2>&1`; ping_alive=$(( ! $? ))
[...]

Hence, if the socket path is correctly defined in /etc/mysql/debian.cnf you should not be getting this error, unless your mysqladmin is broken somehow. Hence, you should try executing:

Code:

mysqladmin --defaults-file=/etc/mysql/debian.cnf ping

Directly (as root) and see what you get in return. If its an error, then it's a bug in mysqladmin.

[theprincy]

mysqladmin --defaults-file=/etc/mysql/debian.cnf ping
mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/var/run/mysql/mysqld.sock' (111)'
Check that mysqld is running and that the socket: '/var/run/mysql/mysqld.sock' exists!


ls -asl /var/run/mysql/
totale 12K
4,0K drwxr-xr-x 2 mysql root 4,0K 29 nov 16:24 .
4,0K drwxr-xr-x 14 root root 4,0K 29 nov 13:51 ..
4,0K -rw-rw---- 1 mysql mysql 6 29 nov 16:23 mysqld.pid
0 -rw-r--r-- 1 mysql mysql 0 29 nov 16:24 mysqld.sock

...

is a bug ?

---

s xa | grep "mysql"
15628 pts/1 Sl 0:01 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --user=mysql --pid-file=/var/run/mysql/mysqld.pid --skip-external-locking --port=3306 --socket=/var/run/mysql/mysqld.sock
15629 pts/1 S 0:00 logger -p daemon.err -t mysqld_safe -i -t mysqld
15665 pts/1 R+ 0:00 grep mysql
30815 pts/1 S 0:00 /bin/sh /usr/bin/mysqld_safe

[kilburn]

Try to connect with the "debian-sys-maint" user instead of root. I bet it doesn't have permission to connect without password (thus causing the error).

[theprincy]

mysql -udebian-sys-maint -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 3782
Server version: 5.0.51a-24+lenny4-log (Debian)

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql>

---

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

[kilburn]

At this point it is pretty clear that this has nothing to do with ispcp itself. Hence, you should probably go to the debian's bug tracking page...

[theprincy]

for now I solved with a symbolic link , I'll make a ticket there too and we'll see