Can t connect to local MySQL server through socket var mysql mysql sock 38

Question

I am having a big problem trying to connect to mysql  When I run    usr local mysql bin mysql start   I have the following error    Can t connect to local MySQL server through socket   var mysql mysql sock   38    I do have mysql sock under the  var mysql directory   In  etc my cnf I have    client  port 3306 socket  var mysql mysql sock   mysqld  port 3306 socket  var mysql mysql sock key buffer size 16M max allowed packet 8M   and in  etc php ini I have      Default socket name for local MySQL connects   If empty  uses the built-in   MySQL defaults  mysql default socket    var mysql mysql sock   I have restarted apache using sudo  opt local apache2 bin apachectl restart  But I still have the error   Otherwise  I don t know if that s relevant but when I do mysql config --sockets I get  --socket           tmp mysql sock

User · Answer

You might want to chek if the hard disk is full  df on the console   that s what ultimately triggered this error for me

User · Answer

Adding  --protocol tcp    to the list of pramaters in your connection worked for me

User · Answer

There are a lot of potential problems that will lead to this error  The best thing  as suggested in another answer  is to check the log file  This can be found in different locations  depending on the platform  For me  this was located at  var log mysqld err and the error was  quot No space left on device quot   After doing some cleanup  I could start the service and the problem was fixed

User · Answer

are you sure you installed mysql as well as mysql server    For example to install mySql server I ll use yum or apt to install both mysql command line tool and the server   yum -y install mysql mysql-server  or apt-get install mysql mysql-server    Enable the MySQL service    sbin chkconfig mysqld on   Start the MySQL server    sbin service mysqld start   afterwards set the MySQL root password   mysqladmin -u root password  new-password   with the quotes    I hope it helps

User · Answer

I had the same problem and it has been caused by an update of mysql drivers when mysql server was running  I fixed it just restarting both mysql and apache2      sudo service mysql stop      sudo service mysql start      sudo service apache2 stop      sudo service apache2 start

User · Answer

If anyone looking for Intialization error  Can t connect to database   var run mysql mysql sock   When running civicrm  amp  drupal just make below changes in   settings php and civicrm settings php  only in places where you try to establish db connection  localhost to 127 0 0 1  local installation

User · Answer

Edit your config file  etc mysql my cnf    client  host          127 0 0 1 port          3306 socket        var run mysql mysql sock

User · Answer

If you are using AWS  Amazon Web Services  Micro version  then it is a memory issue  When I ran   mysql   from the terminal it would say   ERROR 2002  HY000   Can t connect to local MySQL server through socket  var run mysqld mysqld sock   111    So I tried the following and it would just fail   service mysqld restart   After much searching  I found out that you have to create a swap file for MySQL to have enough memory  Instructions are listed  http   www prowebdev us 2012 05 amazon-ec2-linux-micro-swap-space html   Then  I was able to restart mysqld

User · Answer

After two days with this stuff  here s my two cents on this      are you using hhvm    if so  append the next line in  etc hhvm server ini  hhvm mysql socket    var run mysqld mysqld sock

User · Answer

I was getting the error because I was running MAMP and my  sock file was in a different location  I just added a symbolic link where the app thought it should be that pointed to where it actually was and it worked like a charm

User · Answer

To prevent the problem from occurring  you must perform a graceful shutdown of the server from the command line rather than powering off the server   shutdown -h now   This will stop the running services before powering down the machine   Based on Centos  an additional method for getting it back up again when you run into this problem is to move mysql sock   mv  var lib mysql mysql sock  var lib mysql mysql sock bak  service mysqld start   Restarting the service creates a new entry called mqsql sock

User · Answer

Another workaround is to edit  etc my cnf and include host in the section  client     client    password         your password  host              127 0 0 1  port              3306  socket             var run mysql mysql sock   And then restarting the mysql service   This workaround was tested in  Server version  5 5 25a-log Source distribution

User · Answer

I had the same issue on Freebsd  I solved it by deleting the my cnf file  Mysql version was 5 6   It seems that after upgrading from 5 5 the old my cnf remains and some incompatible parameters forces to an error  The old my cnf had a lot of parameters but the new one only one  sql mode NO ENGINE SUBSTITUTION STRICT TRANS TABLES   But if you do so  keep in mind that could be a security risk  because this without any further entry may open your db to the rest of the world  -  If you won t that add at least this line  bind-address   127 0 1 1

User · Answer

A quick workaround that worked for me  try using the local ip address  127 0 0 1  instead of  localhost  in mysql connect    This  forces  php to connect through TCP IP instead of a unix socket

User · Answer

For those whose any solution did not work  try   cd  etc mysql   check if my cnf is present  nano my cnf   and make sure you have only one bind-address as follows   bind-address   127 0 0 1  If not  that might be the problem  just exit nano and save the file   and service mysql start  note that if you don t have nano  its a text editor  just install it with apt-get install nano and once in just press Ctrl X to exit  dont forget to say Y to save and use the same file

User · Answer

For me - this was simply a case of MySQL taking a long time to load  I have over 100 000 tables in one of my databases and it did eventually start but obviously has to take a long time in this instance

User · Answer

I ve deleted mysql sock file and it worked  Putting the rights on it didn t work at all  Neither restarting  or whatever

User · Answer

I ran into this issue today  None of these answers provided the fix  I needed to do the following commands  found here https   stackoverflow com a 20141146 633107  for my mysql service to start   sudo  etc init d mysql stop cd  var lib mysql  ls ib logfile  mv ib logfile0 ib logfile0 bak mv ib logfile1 ib logfile1 bak     etc      etc init d mysql restart   This was partly indicated by the following errors in  var log mysql error log   140319 11 58 21 InnoDB  Completed initialization of buffer pool InnoDB  Error  log file   ib logfile0 is of different size 0 50331648 bytes InnoDB  than specified in the  cnf file 0 5242880 bytes  140319 11 58 21  ERROR  Plugin  InnoDB  init function returned error  140319 11 58 21  ERROR  Plugin  InnoDB  registration as a STORAGE ENGINE failed  140319 11 58 21  ERROR  Unknown unsupported storage engine  InnoDB 140319 11 58 21  ERROR  Aborting   I also saw the disk full error  but only when running commands without sudo  If the permissions check fails  it reports disk full  even when your partition is not even close to full

User · Answer

This doesn t directly answer your question but a subset of it  namely using PythonAnywhere  I kept stumbling upon this question when looking for a fix so I m adding it here in the hope that it will help others in my situation     PythonAnywhere decided to change the database connection hostnames in order to improve efficiency and reliability  as detailed here      The official host name you should use for connecting to your account s   MySQL database instance has changed from mysql server to   yourusername mysql pythonanywhere-services com  This bypasses a part of our infrastructure that has started showing problems in recent   weeks  and it should be much more efficient and reliable than the old   way    Hence  you will need to update your hostname to the value highlighted above

User · Answer

I got the following error   ERROR 2002  HY000   Can t connect to local MySQL server through socket   var run mysqld mysqld sock   111    Tried several ways and finally solved it through the following way  sudo gksu gedit  etc mysql my cnf   modified    bind-address         127 0 0 1   to   bind-address          localhost   and restarted  sudo  etc init d mysql restart   it worked

User · Answer

Try running following command   sudo  etc init d mysql start

User · Answer

There are many solutions to this problem but for my situation  I just needed to correct the DATE on the machine server  Ubuntu 16 04 Server    i  Check the date of your server and correct it   ii  Run sudo  etc init d mysql restart  That should get it started

User · Answer

Make sure you are running mysqld    etc init d mysql start

User · Answer

I had this socket error and it basically came down to the fact that MySQL was not running  If you run a fresh install  make sure that you install 1  the system package and 2  the panel installer  mysql prefPane   The panel installer will allow you to goto your System Preferences and open MySQL  and then get an instance running    Note that  on a fresh install  I needed to reset my computer for the changes to properly take effect  Following a reboot  I got a new instance running and was able to open up a connection to localhost with no problem    Also of note  I apparently had previous versions of MySQL installed but had removed the panel  which makes it easy to get an instance of MySQL running for mac users   A good link for this process of reinstalling  http   www coolestguyplanettech com how-to-install-php-mysql-apache-on-os-x-10-6

User · Answer

I used 127 0 0 1 for -h instead localhost and everything was OK  In other case had what had - error that above

User · Answer

If everything worked just fine and you just started seeing this error  before you do anything else  make sure you re not out of disk space   df -h   If the volume where the mysql sock is being created is at 100  use  MySql won t be able to create it and this will be the cause of this error   All you need to do is delete something that s not needed  like old log files

User · Answer

If your file my cnf  usually in the  etc mysql  folder  is correctly configured with  socket  var lib mysql mysql sock   you can check if mysql is running with the following command   mysqladmin -u root -p status   try changing your permission to mysql folder  If you are working locally  you can try   sudo chmod -R 755  var lib mysql    that solved it for me

User · Answer

This was good enough for me  sudo  etc init d mysql restart

User · Answer

In my case  I was using Centos 5 5  I found that the problem was because the mysql service was stopped some how   So I started mysql service with the command     etc init d mysqld start   So   silly mistake

User · Answer

I ve just had this problem  after a day of checking finally I ve got the answer with that The mysql sock file is created when MariaDB starts and is removed when MariaDB is shutdown  It won t exist if MariaDB is not running  maybe you didn t install MariaDB  YOU COULD FOLLOW THE INSTRUCTION BELOW  https   www linode com docs databases mariadb how-to-install-mariadb-on-centos-7 BEST

User · Answer

try with -h  host  and -P port    mysql -h 127 0 0 1 -P 3306 -u root -p

User · Answer

As can be seen by the many answers here  there are lots of problems that can result in this error message when you start the MySQL service  The thing is  MySQL will generally tell you exactly what s wrong  if you just look in the appropriate log file   For example  on Ubuntu  you should check  var log syslog  Since lots of other things might also be logging to this file  you probably want to use grep to look at mysql messages  and tail to look at only the most recent  All together  that might look like   grep mysql  var log syslog   tail -50  Don t blindly make changes to your configuration because someone else said  This worked for my system   Figure out what is actually wrong with your system and you ll get a better result much faster

User · Answer

you can always start mysql server by specifying the location of the mysql sock file using the --socket option like  mysql --socket  var mysql mysql sock    This will work even if the location of socket file in specified in a different location in the my cnf file

User · Answer

In my case the solution was that I had mariadb installed  which was aliased to mysql  So all service commands relating to mysql were not recognised    I just needed   service mariadb start   And for good measure   chkconfig mariadb on

User · Answer

sudo service mysqld start   Worked for me  I m using Centos

User · Answer

sudo service mysql start   This should serve you just fine  There could be a possibility that you changed some commands that affected the mysql configurations

User · Answer

I got this error when I set cron job for my file  I changed the permissions of file to 777 but it still not worked for me  Finally I got the solution  May be it will be helpful for others   Try with this command      mysql -h 127 0 0 1 -P 3306 -u root -p   Remember that -h means host  -P means port and -p means password

User · Answer

CentOS 7  64 bit  Fresh installation  In my case  the error was because I didn t have the right MySQL server and MySQL client installed  Using yum  I removed mariadb and mysql-community edition  I downloaded the rpm s for the client and server from the official MySQL website and installed the server and client     On installing the server  I was shown a message that the password to the root account for MySQL was stored in a file which I could view with sudo cat  root  mysql secret     So after installing the client and server  I checked if MySQL was working  I think I rebooted before doing so  with the command sudo service mysql status and I got the result        MySQL running  2601                                           OK      I logged into MySQL using the password from the  mysql secret file  mysql -uroot -pdxM01Xfg3DXEPabpf  Note that dxM01Xfg3DXEPabpf is the password mentioned in the  mysql secret file     and then typed entered the following command at the mysql prompt to change the password of root     mysql gt  SET PASSWORD FOR  root   localhost    PASSWORD  somePassword       Everything worked fine from then on

User · Answer

I solved by deleting tc log into  var lib mysql directory because it was corrupdet after full disk  Than  when i started mysql  the log file was created as new

User · Answer

I had this problem too when trying to start the server  so many of the answers here that just say to start the server didn t work  The first thing you can do is execute the following to see if there are any config errors    usr sbin mysqld --verbose --help 1 gt  dev null   I did have one error that showed up   160816 19 24 33  Note   usr sbin mysqld  mysqld 5 5 50-0ubuntu0 14 04 1-log  starting as process 9461     160816 19 24 33  Warning  Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release  Please use the full name instead  160816 19 24 33  Note  Plugin  FEDERATED  is disabled  160816 19 24 33  ERROR   usr sbin mysqld  unknown variable  innodb-online-alter-log-max-size 4294967296  160816 19 24 33  ERROR  Aborting   A simple grep -HR  innodb-online-alter-log-max-size   etc mysql  showed me exactly what file contained the offending line  so I removed that line from the file   Then  checking my  var log mysql error log file I had   InnoDB  Error  log file   ib logfile0 is of different size 0 5242880 bytes InnoDB  than specified in the  cnf file 0 671088640 bytes  160816 22 46 46  ERROR  Plugin  InnoDB  init function returned error  160816 22 46 46  ERROR  Plugin  InnoDB  registration as a STORAGE ENGINE failed  160816 22 46 46  ERROR  Unknown unsupported storage engine  InnoDB 160816 22 46 46  ERROR  Aborting   Based on this question the accepted solution wouldn t work because I couldn t even get the server started  so I followed what some of the comments said and deleted my  var lib mysql ib logfile0 and  var lib mysql ib logfile1 files   This allowed the server to start and I was able to connect and execute queries  however checking my error log file it was quickly getting filled up with several tens of thousands of lines like this   160816 22 52 15  InnoDB  Error  page 1415 log sequence number 82039318708 InnoDB  is in the future  Current system log sequence number 81640793100  InnoDB  Your database may be corrupt or you may have copied the InnoDB InnoDB  tablespace but not the InnoDB log files  See InnoDB  http   dev mysql com doc refman 5 5 en forcing-innodb-recovery html InnoDB  for more information    Based on a suggestion from here  to fix this I did a mysqldump and restore of all databases  see the link for several other solutions      mysqldump -u root -p --allow-keywords --add-drop-database --comments --hex-blob --opt --quote-names --databases db 1 db 2 db 3 db etc  gt  backup-all-databases sql   mysql -u root -p  lt  backup-all-databases sql   Everything appears to be working as expected now

User · Answer

I also found that this was a permissions problem   I compared the MySQL files to a working install  both on Debian 6 squeeze  and had to make the following ownership changes  where mydatabase is any database s  you have    Ownership mysql mysql   chown mysql mysql  var lib mysql chown mysql mysql  var lib mysql ib  chown mysql mysql  var lib mysql mydatabase chown mysql mysql  var lib mysql mydatabase   chown mysql mysql  var lib mysql mysql      Ownership mysql root   chown mysql root  var lib mysql mysql chown mysql root  var run mysqld    Ownership mysql adm   chown mysql adm  var log mysql chown mysql adm  var log mysql err chown mysql adm  var log mysql log

[mysql] Can't connect to local MySQL server through socket '/var/mysql/mysql.sock' (38)

Examples related to mysql