ramana_sharma@ramana:~$ mysql --version mysql Ver 14.14 Distrib 5.7.26, for Linux (x86_64) using EditLine wrapper ramana_sharma@ramana:~$ mysql -uroot -proot0 mysql: [Warning] Using a password on the command line interface can be insecure. ERROR 2002 (HY000): Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2) ramana_sharma@ramana:~$ mysql -u root -p Enter password: ERROR 2002 (HY000): Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2) ramana_sharma@ramana:~$ services mysql start No command ‘services’ found, did you mean: Command ‘service’ from package ‘init-system-helpers’ (main) services: command not found ramana_sharma@ramana:~$ /etc/init.d/mysql start bash: /etc/init.d/mysql: No such file or directory ramana_sharma@ramana:~$ #/usr/sbin/mysqld --defaults-file=/etc/mysql/my.cnf --basedir=/usr --datadir=/var/lib/mysql --pid-file=/var/run/mysqld/mysqld.pid --socket=/var/run/mysqld/mysqld.sock ramana_sharma@ramana:~$ /etc/init.d/mysql start bash: /etc/init.d/mysql: No such file or directory ramana_sharma@ramana:~$ sudo service mysql restart [sudo] password for ramana_sharma: Failed to restart mysql.service: Unit mysql.service not found. ramana_sharma@ramana:~$ sudo nano /etc/mysql/my.cnf ramana_sharma@ramana:~$ systemctl enable mysql Failed to execute operation: No such file or directory
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Accepted Answer
Can you try to examine the server logs in order to track down more detailed information bout the issue?
On Ubuntu systems, the default location for MySQL is /var/log/mysql/error.log In many cases, the error logs are most easily read with the less program, a command line utility that allows you to view files but not edit them:
- sudo less /var/log/mysql/error.log
If MySQL isn’t behaving as expected, you can obtain more information about the source of the trouble by running this command and diagnosing the error based on the log’s contents.
You can also use the journalctl command
The innodb_force_recovery is added to the my.cnf file in case of InnoDB corruption, but you need to use that as a last resort option.
Regards
mysql -h 127.0.0.1 -P 3306 -u root -p Enter password: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 12 Server version: 8.0.16 MySQL Community Server - GPL
Copyright © 2000, 2019, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
Type ‘help;’ or ‘\h’ for help. Type ‘\c’ to clear the current input statement.
mysql> show databases; ±-------------------+ | Database | ±-------------------+ | information_schema | | kataragamaKiosk | | mysql | | performance_schema | | sys | ±-------------------+ 5 rows in set (0.63 sec)
mysql>
Hi there @ramanakarasarma,
It sounds like possibly you only have the mysql client installed and not the server:
This should be able to be solved by installing mysql-server, so make sure that you have installed the mysql-server, not the mysql-client or something else.
The error you are seeing means that the file /var/run/mysqld/mysqld.sock doesn’t appear to exist, if you didn’t install mysql-server, then the file would not exist.
You should be able to quickly verify if the mysql server is running locally by doing the following two things:
First, attempt to login to the server with the localhost IP and specific mysql port:
mysql -h 127.0.0.1 -P 3306 -u root -p <database>
You can also use telnet to see if anything is being served locally on the mysql port at all:
telnet 127.0.0.1 3306
If those don’t work, it is very likely that mysql-server isn’t installed or running. You can install it by using sudo apt-get install mysql-server or similar depending on the linux distro you are using.
However, if the mysql-server is already installed and is running, then you need to check the config files to ensure they are looking for the right sock file:
/etc/my.cnf
/etc/mysql/my.cnf
/var/lib/mysql/my.cnf
In /etc/my.cnf, the socket file may be configured to use /tmp/mysql.sock or similar, but in the /etc/mysql/my.cnf file, the socket file may be set to /var/run/mysqld/mysqld.sock.
So you may also be able to resolve this by removing or renaming /etc/mysql/my.cnf, which will then let mysql use /etc/my.cnf instead.
Hope that helps! - Matt.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.