Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
I had this same problem 2-3 weeks ago on another PC that is running Ubuntu 11.10 (which this PC is too old to run) and fixed the problem by deleting /var/run/mysqld/mysqld.sock and entering
Code:
service mysql restart
However that does not work this time. I still get
Code:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
When I enter
Code:
ps aux|grep mysql
I get
Code:
peter 15595 0.0 0.0 4156 868 pts/2 S+ 15:51 0:00 grep --color=auto mysql
Any assistance with resolving this issue would be most appreciated,
Peter.
Hrm... if ps faux | grep mysql returns zero results for a running mysql server, but that error is occuring when trying to start MySQL, it sounds like the PID file still exists for some reason.
If you're positive that MySQL is not running, try removing the PID file from wherever its configured to exist (should be able to find its location set in etc/my.cnf in most distros).
Just make absolutely sure that MySQL is not really running.
Last edited by nick2day; 06-16-2012 at 06:12 PM.
Reason: clarified that the PID file is not my.cnf. my.cnf is the configuration file for mysql.
Hrm... if ps faux | grep mysql returns zero results for a running mysql server, but that error is occuring when trying to start MySQL, it sounds like the PID file still exists for some reason.
If you're positive that MySQL is not running, try removing the PID file from wherever its configured to exist (should be able to find its location set in etc/my.cnf in most distros).
Just make absolutely sure that MySQL is not really running.
I was unable to find a reference to a pid, or PID, file in /etc/mysql/my.cnf or in /etc/mysql/debian.cnf. I did a search for .pid files, on my system, and found the following.
Hrm.. this one is interesting. Can you post the .cnf file that you're using?
And sorry I have to ask this, but do you have the permissions to execute the service? (yah... you've probably already checked, but I gotta ask just to fully troubleshoot this with ya )
Hrm.. this one is interesting. Can you post the .cnf file that you're using?
And sorry I have to ask this, but do you have the permissions to execute the service? (yah... you've probably already checked, but I gotta ask just to fully troubleshoot this with ya )
I installed LAMP on this system. mysql was working a week ago. I don't know what happened in the interim. /etc/mysql/my.cnf is as follows.
Code:
[mysqld]
#
# * Basic Settings
#
#
# * IMPORTANT# also need to also adjust /etc/apparmor.d/usr.sbin.mysqld.
#
user = mysql
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
datadir = /var/lib/mysql
tmpdir = /tmp
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 = 192.168.1.6
#
# * Fine Tuning
#
key_buffer = 16M
max_allowed_packet = 16M
thread_stack = 192K
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.
# As of 5.1 you can enable the log at runtime!
# If you make changes to these settings and your system uses apparmor, you may
#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "~/.my.cnf" to set user-specific options.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html
# 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/mysqld/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/mysqld/mysqld.sock
nice = 0
#general_log_file = /var/log/mysql/mysql.log
#general_log = 1
log_error = /var/log/mysql/error.log
# 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
#
# * 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!
#
# * 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
#
# * 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/
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
)
