Cant connect to local mysql server through socket /var/run/mysqld/mysqld.sock 13

My problem started off with me not being able to log in as root any more on my mysql install. I was attempting to run mysql without passwords turned on… but whenever I ran the command

I would never get the prompt back. I was trying to follow these instructions to recover the password.

The screen just looks like this:

and I don’t get a prompt to start typing the SQL commands to reset the password.

When I kill it by pressing CTRL + C, I get the following message:

If I retry the command and leave it long enough, I do get the following series of messages:

But then if I try to log in as root by doing:

I get the following error message:

I checked and /var/run/mysqld/mysqld.sock file doesn’t not exist. The folder does, but not the file.

Also, I don’t know if this helps or not, but I ran find / -name mysqld and it came up with:

I’m new to Linux and MySQL, so I don’t know if this is normal or not. But I’m including this info just in case it helps.

I finally decided to uninstall and reinstall mysql.

After reinstalling all packages again in the same order as above, during the phpmyadmin install, I got the same error:

So I tried again to uninstall/reinstall. This time, after I uninstalled the packages, I also manually renamed all mysql files and directories to mysql.bad in their respective locations.

Then I tried to reinstall mysql-server and mysql-client again. But I’ve noticed that it doesn’t prompt me for a password. Isn’t it supposed to ask for an admin password?

I got the same problem. I solved it just now. stackoverflow.com/questions/18150858/… – robertAug 9, 2013 at 16:28

• solved by just reboot the server, then restart the mysql service – bowpunya Jan 19, 2017 at 8:09

• None of the answers here or anywhere else I could find solved my problem. As it was a new project I switched to PostgreSQL and it just works! 🙂 – James Bradbury Apr 8, 2020 at 20:55

Try this command,

• I tried the accepted answer but couldn’t find the mysql.sock, this worked for me. Thank you – Giovanne Afonso Feb 23, 2015 at 5:59

• 20sudo apt-get install mysql-server if you dont have it installed already 🙂 – aimme Jun 9, 2016 at 23:12

If you hit this issue, by all means, run this simple command FIRST before testing the other stuff, it only takes a second, and if the server simply isn’t running, and is fine after you start it, it just means it didn’t autostart, which would then be the actual problem to solve. – LizardxAug 25, 2016 at 22:48

This error occurs due to multiple installations of mysql. Run the command:

Kill the process by using:

and then run command:

Also Kill this process by running:

Now you are fully set just run the following commands:

Have very well working mysql again

Hey folks, I was running all over the web trying to fix this. My problem was that I was trying to setup docker. I wanted it to use the mysql data dir that was previously used by mysql outside of docker… that ps command was the best! – MichaelNov 13, 2014 at 16:14

• 7Job for mysql.service failed because the control process exited with error code. See “systemctl status mysql.service” and “journalctl -xe” for details. – John Joe Oct 9, 2017 at 15:42

Job for mysql.service failed because the control process exited with error code. See “systemctl status mysql.service” and “journalctl -xe” for details. – Adib ArouiAug 18, 2018 at 12:13

Tnx, you save my time. – Aleksandur AtanasovMay 28, 2019 at 18:24

Job for mysql.service failed because the control process exited with error code. See “systemctl status mysql.service” and “journalctl -xe” for details. – Imad OulhouAug 28, 2020 at 23:23

• Short, well-explained and accurate. Should be the top answer. THANKS! – araujophillips Jan 30, 2021 at 10:33

This definitely is the answer – ClarkeFeb 7, 2021 at 9:00

To find all socket files on your system run:

My Mysql server system had the socket open at /var/lib/mysql/mysql.sock

Once you find where the socket is being opened, add or edit the line to your /etc/my.cnf file with the path to the socket file:

Sometimes the system startup script that launched the command line executable specifies a flag --socket=path. This flag could override the my.cnf location, and that would result in a socket not being found where the my.cnf file indicates it should be. Then when you try to run the mysql command line client, it will read my.cnf to find the socket, but it will not find it since it deviates from where the server created one. So, Unless you care where the socket resides, just changing the my.cnf to match should work.

Then, stop the mysqld process. How you do this will vary by system.

If you’re super user in the linux system, try one of the following if you don’t know the specific method your Mysql setup uses:

• service mysqld stop
• /etc/init.d/mysqld stop
• mysqladmin -u root -p shutdown
• Some systems aren’t setup to have an elegant way to stop mysql (or for some reason mysql doesn’t respond) and you can force terminate mysql with either:One step: pkill -9 mysqld
• Two step (least preferred):Find the process id of mysql with either pgrep mysql or ps aux | grep mysql | grep -v grep
• Assuming the process id is 4969 terminate with kill -9 4969

After you do this you might want to look for a pid file in /var/run/mysqld/ and delete it

Make sure the permissions on your socket is such that whatever user mysqld is running as can read/write to it. An easy test is to open it up to full read/write and see if it still works:

If that fixes the issue, you can tailor the permissions and ownership of the socket as needed based on your security settings.

Also, the directory the socket resides in has to be reachable by the user running the mysqld process.

Please don’t recommend using kill -9; there are several ways that should be tried before it has to come to that. – Ignacio Vazquez-AbramsAug 16, 2012 at 16:17

@dot run this in file root ‘find . -name mysqld.sock’. I have seen the socket file in other places than /var/run. Once you find it you might need to edit your my.cnf file to point to where it is found. – RayAug 16, 2012 at 17:57

@ray, i tried to run the original command in a different way (i found a ubuntu specific post on another site..). Here’s the commands I ran: “sudo service mysql stop” and “sudo mysqld –skip-grant-tables”. After I do the second command, i get the following error: “InnoDB: Unable to lock ./ibdata1, error: 11”. I can’t find this ./ibdata1 file… InnoDB: Check that you do not already have another mysqld process – dotAug 16, 2012 at 18:24

• @dot run ps -aux | grep mysqld and see if any other mysql processes are running – Ray Aug 16, 2012 at 19:05

@ray. i’m rippng my hair out man. i decided to blow mysql away and retry… note my updated post. – dotAug 16, 2012 at 19:36

Make sure your inaccessible socket file path is same as ‘/var/run/mysqld/mysqld.sock’, otherwise change the path as yours. Stop the mysqld

If the process still runing;

Remove the mysql directory where socket going to create. For me it did not allowed to remove, so I had to forcefully remove.

Set the ownership to the dirctory

Start mysql

Trying to connect mysql

Yes thats the same Answer I gave at Feb 14 ’19 at 11:56 (see below) – IngoJan 18, 2020 at 17:20

Just Need to Start MySQL Service after installation:

For Ubuntu:

For CentOS or RHEL:

Check first by this sudo systemctl status mysql.service and sudo systemctl start mysql.service. This works for me – Byeongin YoonJan 2, 2019 at 9:10

Why getting this error

I received new updates of mysql libraries so i updated my Kubuntu OS after that getting these errors.

Commands i tried and how i fixed it.

MySql-server is running correctly but when i tried to connect its giving

I checked /var/run/mysqld/mysqld.sock'. this directory. My files did not existed.

I also tried these commands to connect but did not worked for me.

After wasting round about 2 hours i found the solution

After that everything fixed for me.

This helped me to fix the problem. I dont understand how is it related to socked problem i had… – ČamoMay 21, 2020 at 17:38

The solution is way easier.

1. First, you have to locate(in Terminal with “sudo find / -type s”) where your mysql.sock file is located. In my case it was in /opt/lampp/var/mysql/mysql.sock
2. Fire up Terminal and issue sudo Nautilus
   This starts your Files manager with super user privileges
3. From Nautilus navigate to where your mysql.sock file is located
4. Right click on the file and select Make Link
5. Rename the Link File to mysqld.sock then Right click on the file and Cut it
6. Go to /var/run and create a folder called mysqld and enter it
7. Now right click and Paste the Link File
8. Voila! You will now have a mysqld.sock file at /var/run/mysqld/mysqld.sock 🙂

• How do you locate your mysql.sock file? I tried find / -name ‘mysql.sock’ but it returns nothing. – Matthew Lock Mar 26, 2013 at 3:11
• 2

@MatthewLock First off, make sure that mysql is running (by “ps aux | grep mysql”), otherwise, no mysql.sock would appear. Second, use “sudo find / -type s”, which gives you all sockets on your system to locate mysql.sock – narengiJun 29, 2013 at 11:34

Report: This worked for me (although with different directories, since I’m using a different distribution): here’s what I did: 1- checked at what location mysql tries to access the socket file (by reading the log file). For me, it was /usr/var/mysqld/mysqld.sock 2- made sure mysqld is running (by running /where/your/mysql/is/mssqld_safe) 3- searched for the location where mysql socket now sits (by sudo find / -type s let’s just say it’s on /tmp/mysql.sock) 4- made a soft link from where-it-is to where-it’s-to-be (by sudo ln -s /usr/var/mysql/mysql.sock /tmp/mysql.sock) – narengiJun 30, 2013 at 8:26

What if the output of sudo find / -type s does not contain any mysql.sock? – jeffFeb 25, 2015 at 15:16

If it’s pain to get of where is mysql.sock through “find / -type s” – try to use “mysql_config –socket” command. You can install it with sudo apt-get install libmysqlclient-dev – alexche8Jun 24, 2016 at 13:38

It works. But I have no idea why these developers never do this job in past years? – Yi JiangAug 24, 2015 at 1:12

If it’s pain to get of where is mysql.sock through “find / -type s” – try to use “mysql_config –socket” command. You can install it with sudo apt-get install libmysqlclient-dev – alexche8Jun 24, 2016 at 13:38

@alexche8 well that very command tells me the sock file is located @ /var/run/mysqld. but that folder does not exist – phil294Aug 3, 2016 at 19:55

14

I faced same error and found that it was due to upgradation of packages, So after restarting my system I resolved error.

I think due to sql libraries/ packages update that error occured, So try this if you are doing some upgrading 🙂

I did this after reinstall (or upgrade) and now it works. No more socket message. Thanks! 

Okay just copy and paste these codes: This should be done in the terminal, inside a server, when your mysql database is not properly installed, and when you are getting this error: ‘Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)’.

Stop MySql

Restart it or start it

Make a link like this and give it to the system

Run a secure installation which guides all the process you need to do to configure mysql

i get same Can't connect error when i try running above command. – cjmlingJan 10, 2018 at 16:59

Just something I discovered, for those running ubuntu. If you start mysqld using /etc/init.d/mysqld start you will run into this issue anyway. Use service mysql start instead and it will be fine. Infuriating, but I figured it out in the end. – Adam ShortDec 2, 2019 at 14:18

There is a bug on Ubuntu with MySQL 5.6 and 5.7 where var/run/mysqld/ would disappear whenever MySQL service stopped or is rebooted. This prevents MySQL from running at all. Found this workaround, which isn’t perfect, but at least it gets it running after stopping/reboot:

thank you – fixed it for me, I have to remake the directory and reset ownership on every restart of service mysql – have not been able to find the error reported anywhere officially or I would have posted link here 🙂 – djoeMar 22, 2017 at 5:57

Haven’t tried this, but maybe it will help you: Create a newfile /etc/tmpfiles.d/mysql.conf: # systemd tmpfile settings for mysql # See tmpfiles.d(5) for details and then, d /var/run/mysqld 0755 mysql mysql - After reboot, mysql should start normally. This is from bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1435823, comment 3. If you had this problem with MySQL 5.7, please comment on Launchpad. The more users that address the problem, the more attention it will get. – motorbabyMar 30, 2017 at 18:50

Worked for me… had to use mysql as username and not mysqld though – Evan ParsonsApr 17, 2017 at 0:36

dding line to /etc/tmpfiles.d/mysql.conf per motorbaby’s comment fixed this issue for me. On a Centos 7 OS and using mysql Ver 15.1 Distrib 10.3.11-MariaDB,. – turrican_34Dec 10,

This fixed the issue for me. – shikataFeb 17, 2020 at 15:00

I think your MySQL server has not started. So start the server using one of the following commands.

or

Using XAMPP on ubuntu:

1. Create a folder called mysqld inside /var/run directory. You can accomplish that using the command sudo mkdir /var/run/mysqld.
2. Create a symbolic link to mysql.sock file that is created by the XAMPP server when it is started. You can use the command sudo ln -s /opt/lampp/var/mysql/mysql.sock /var/run/mysqld/mysqld.sock.

Note: The mysql.sock file is created when the server is started and removed when the server is stopped, so sometimes the link you created might appear to be broken but it should work as long as you have started the server using either sudo /opt/lampp/lampp start or any other means.

1. Start the server if it’s not already running and try executing your program again.

Good luck! I hope you’ll get away with it this time.

3

I am using XAMPP on Ubuntu. I found this error when connecting database through terminal. I solve it without any configuration because default socket file path in XAMPP is written in “/opt/lampp/etc/my.cnf” as following:

now you can connect just by giving this socket path parameter with mysql command on terminal like:

and it’s done without any configuration.

If you don’t want to type socket path everytime, then go for changing default path in my.cnf by “/var/run/mysqld/mysqld.sock”. Provide permissions and restart mysql server.

Edit: Recently I’ve installed Ubuntu 20.04 and trying to install MySQL server but my system were crashing and not working at all. So I’ve just completely removed MySQL and installed MariaDB. Its working like a charm without any problems.

You must install mysql-server

The answer of the user load step worked for me. Sometimes is need edit the file in /etc/mysql/my.cnf add line to client

This gives me: mysql: unknown variable 'Host=127.0.0.1' – SplaktarMar 19, 2014 at 13:54

@Splaktar: there’s a typo. Host need to be lowercase host and it will work. Also, this solution worked for me. – Mohammad FaisalApr 18, 2014 at 9:10

Brilliant – this is working for me and my docker environment – i only had to adjust the ip which is in my case the docker mysql container ip 172.17.x.x – InforMedicJan 23, 2018 at 9:58

 had the exactly same issue. After struggling for an hour, I found a way of correcting it without reinstalling mysql-common, mysql-client, mysql-server.

First of all, go to “/var/run/mysqld”. You will find that the mysql.sock does not exist. Simply remove the entire mysqld directory and recreate it and provide it necessary privileges.

Now, Kill the mysql process in it’s entirety. It might be possible that it will show you “waiting for page cleaner” on running “/etc/init.d/mysql status” command even after shutting down the service.

To completely close the service, use

Once the process is killed, try starting it again using

And you will see that it works good! And also there will be no issue in stopping it too.

solutions

finally uninstall and reinstall mysql. **

• sudo apt-get remove mysql-server
• sudo apt-get remove mysql-client
• sudo apt-get remove mysql-common
• sudo apt-get remove phpmyadmin

then install again by

• sudo apt-get install mysql-server-5.6

After this operation, 164 MB of additional disk space will be used.

• Do you want to continue? [Y/n] Y press YES for complete installations

…… …….

• At last you will get these lines….Setting up libhtml-template-perl (2.95-1) …Setting up mysql-common-5.6 (5.6.16-1~exp1) … Processing triggers for libc-bin (2.19-0ubuntu6) Processing triggers for ureadahead (0.100.0-16) …
• And thenroot@ubuntu1404:~# mysql -u root -p (for every password first u should use )
• Enter password:
• Note :Entered password should be same as the installation time password of mysql(like .root,system,admin,rahul etc…)

• Then type
• USE rahul_db(database name);

Thanks.**

• This worked for me due to multiple mysql versions installed. also remove mysql-server-5.6/5.5, mysql-client-5.6/5.5. Thanks! – Luuk Skeur Feb 26, 2016 at 10:39

got E: Package 'mysql-server-5.6' has no installation candidate, it not exists in Ubuntu 18.04 – juliocesarJul 16, 2019 at

his was mentioned a couple of times already, but this worked immediately for me:

service mysql restart

here is a lots of reason for this issue, but sometimes just restart the mysql server, it will fix the issue.

My solution;

Ubuntu 18.04 (WSL)

/etc/mysql/my.cnf

/etc/mysql/mysql.conf.d/mysqld.cnf

I changed the port. It’s worked for me. You can write another port. Example 3355

Temporary Solution

Maybe someone facing this problem. I am using Mysql Workbench on Ubuntu 14 and got this error.

Find your socket file by running sudo find / -type s, in my case it was /run/mysqld/mysqld.sock

So, I just created a link to this file in tmp directory.

Please note that this is a temporary solution since the file created will be under /tmp. See other answers for a permanent solution.

As you can see the location of file is under /tmp folder so it’ll be removed for sure. You can change .sock file location. See @user3002884 answer. – BilalAug 7, 2016 at 10:26

I know, I was just completing your answer so other users know before that the solution is just temporary, as the folder – Alex BurduselAug 8,

This solution can help others, sometimes the fix is very simple.

In your live environment restart mysql server and apache

this is a common problem when you install a plugin or execute any database commands.

First create dir /var/run/mysqld

with command:

then add rigths to the dir

after this try

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

in /etc/my.cnf add this lines:

And restart the service with: service mysql restart

this worked for me

I just had this problem on Ubuntu 14.10

Turns that mysql-server was no longer installed (somehow it had been removed) but I couldn’t just install it because there were some broken packages and dependency issues/conflicts.

In the end I had to reinstall mysql

Changing the host to 127.0.0.1 worked for me.

Edit the file in /etc/mysql/my.cnf and add the below mentioned line to the section: client

After you are done with it. Execute the following command.

• @NBhargav i am so happy that u could solve ur problem .. Cheers buddy .. 😇😇 – Dulacoste May 5, 2015 at 12:41

Sometimes it’s just that you don’t have enough space on server, just free up some space (like clearing log files), and start mysql:

/etc/init.d/mysql start

my situation is that the mysql in the /etc/ directory is renamed mysql_bk, just copy mysql_bk

then

As with every other answer in this thread — this can be attributed to a socket to MySQL being unavailable. This answer is unlikely to be of more use or help to others, because if you don’t have mysql available at all, as in this poster’s answer, then of course the socket will not be available. Others are not going to have that same mysql_bk issue which was clearly a user-initiated thing. – Sean HallsJul 8, 2020 at 8:21

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

Sometimes it is due to when mysql server goes down , in live server i think you should have to restart server and also in localhost you need to restart mysql server .

In My case two mysqld processes were running.. killed the optional processs by using pkill -9 mysqld

I needed to add the ‘sudo’ kill the process. – notiJan 20, 2014 at 15:02

If you have a lot of databases and tables on your system, and if you have innodb_file_per_table set in my.cnf, then your mysql server might have run out of opened objects / files (or rather the descriptors for these objects) Set a new max number with

and restart mysql. This approach might help when the socket is not created at all, but really this might not not be the real problem, there is an underlying problem.

you can find mysqld.sock in /var/run/mysqld if you have already installed mysql-server by sudo apt-get install mysql-server

2

I uninstalled mysql in Ubuntu 16.04 https://askubuntu.com/questions/172514/how-do-i-uninstall-mysql

I reinstalled mysql https://www.digitalocean.com/community/tutorials/how-to-install-mysql-on-ubuntu-16-04

This seemed to work.

Try the following at a terminal prompt:

Once that lets you in, you can create a new user and grant privileges that you want on the specific database they need access to.

Mysql 5.7 changed some things and by default uses the auth_socket plugin (as opposed to mysql_native_password) for root to protect the account from getting hacked. You can override this by setting the plugin field for root, but unless you have a very good reason you probably shouldn’t circumvent the protection. Especially when sudo mysql is easier than mysql -u root -p anyway.

I found out this info – of all places – from a Raspberry Pi help site. Worked like a charm after Lubuntu 18.04 annoyed the heck out of me for a couple hours.

I had similar problem on a CentOS VPS. If MySQL won’t start or keeps crashing right after it starts, try these steps:

1) Find my.cnf file (mine was located in /etc/my.cnf) and add the line:

innodb_force_recovery = X

replacing X with a number from 1 to 6, starting from 1 and then incrementing if MySQL won’t start. Setting to 4, 5 or 6 can delete your data so be carefull and read http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html before.

2) Restart MySQL service. Only SELECT will run and that’s normal at this point.

3) Dump all your databases/schemas with mysqldump one by one,

do not compress the dumps because you’d have to uncompress them later anyway.

4) Move (or delete!) only the bd’s directories inside /var/lib/mysql, preserving the individual files in the root.

5) Stop MySQL and then uncomment the line added in 1). Start MySQL.

6) Recover all bd’s dumped in 3).

Good luck!

locate the my.cnf file with the mysql config mine was under /etc/mysql/my.cnf (change the location where it says socket accordingly)

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.

I run my MySQL on a virtual machine in Ubuntu, So what had happened was when I restarted my host and the VM, The IP had changed. I had configured mysql to run on IP 192.168.0.5 and now due to dynamic allocation of IP, my new IP was 192.168.0.8

If you have the same problem just check your ip with the command ifconfig.

Check your MySQL binding with the command cat /etc/mysql/my.cnf | grep bind-address

If both IP are the Same, then reinstall your mysql server

If not, then change your IP in /etc/network/interfaces using nano, vi, vim or anything of your preference.

I prefer sudo nano /etc/network/interfaces

and enter the following

Save the interfaces file, restart your interface sudo ifdown eth0 && sudo ifup eth0 replace “eth0” with your network interface

Restart MySQL sudo service mysql stop followed by sudo service mysql start

If you have the same issue as mine, You are good to go!

I had same problem. after removing and reinstalling mysql this issue did happen.

CAUTION: you’re DATA will be DELTED!!! unfortunately i didn’t find a way to get backup of mysql files when mysql is broken (if you know a way to do this please note in comments).
Just use this method if your data in mysql does not matter to you (like me when i was trying to install mysql in new installed OS).

Problem:

What did cause the problem? first i used apt remove to reinstall the mysql but this job caused error in mysql:

Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)’ — Missing /var/run/mysqld/mysqld.sock

Fix:

Then i used command purge to reinstall the mysql and it worked:

1. sudo apt purge mysql* (this will clean all of your data!);
2. sudo apt autoremove
3. sudo apt install mysql-server (add what application you need!)

After doing these steps just run sudo mysql -u root.

I would also check the mysql configuration. I was running into this problem with my own server but I was a bit too hasty and misconfigured the innodb_buffer_pool_size for my machine.

innodb_buffer_pool_size = 4096M

It usually runs fine up to 2048 but I guess I don’t have the memory necessary to support 4 gigs.

I imagine this could also happen with other mysql configuration settings.

on archlinux I faced this error and the problem was that the mysqld-service wasn’t running.

However I couldn’t enable the mysql-service with systemctl start mysqld as instructed in the Archlinux documentation. I think the error was something like

mysqld.service not found

I first needed to restart the system.

Then I entered the command again (and entered systemctl enable mysqld) and now mysql was able to find the created mysql.sock.

I had this type of problem when i resize the droplet on digitalocean. I had upgrade the mysql version and works for me. Here is the tutorial what i applied – https://serverpilot.io/community/articles/how-to-upgrade-mysql-5.5-to-5.6-on-ubuntu-14.04.html

0

I tried almost all the listed solutions, none worked for me until I restarted the machine and then mysql server restarted when I issued the command “service mysql restart”.

In my case the problem was the bind addresses in /etc/mysql/my.cnf, then:

nano /etc/mysql/my.cnf

search bind addresses and remove the specific with the host ip (not the 127.0.0.1)

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

Just share with you guys, I faced same issue and got resolved using below command

sudo ln -s /var/lib/mysql/mysql.sock /var/run/mysqld/mysqld.sock

I hard link both the locations from my my.cnf and error

I got this answer from enter link description here

For those who are using MySql via Vitess.

I received this error at the vttablet component due to a syntax error (forgot to add ; to end of SQL command) passed to init_db.sql that is given as example in get started docs:

Full error log:

TabletManager.ReplicationStatus()(on zone1from ) error: net.Dial(/vt/socket/mysql.sock) to local server failed: dial unix /vt/socket/mysql.sock: connect: no such file or directory (errno 2002)

The only thing that worked for me was uninstalling MYSQL completely from my system. So i did the following:

0

if you have “Unit mysql.service not found” error, you should install “sudo apt-get install mysql-server”

In lampp as i recognize it does not identify mysql commands. try with

it will open the mysql terminal where you can communicate with databases..

source : https://stackoverflow.com/questions/11990708/error-cant-connect-to-local-mysql-server-through-socket-var-run-mysqld-mysq?page=2&tab=trending#tab-top

Continue Reading