We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
Can't connect to MySQL anymore
Can't connect to MySQL anymore
Hello,
I can't connect to MySQL anymore, without having done anything. Maybe it's an automatic update?
I have this error:
#2002 - No such file or directory — The server is not responding (or the local server's socket is not correctly configured).
my.cnf
I will really appreciate your help.
Thanks
I can't connect to MySQL anymore, without having done anything. Maybe it's an automatic update?
I have this error:
#2002 - No such file or directory — The server is not responding (or the local server's socket is not correctly configured).
my.cnf
Code: Select all
[client]
port=3306
socket=/var/run/mysqld/mysqld.sock
[mysqld_safe]
socket=/var/run/mysqld/mysqld.sock
[mysqld]
user=mysql
pid-file=/var/run/mysqld/mysqld.pid
socket=/var/run/mysqld/mysqld.sock
port=3306
basedir=/usr
datadir=/var/lib/mysql
tmpdir=/tmp
lc-messages-dir=/usr/share/mysql
log_error=/var/log/mysql/error.log
symbolic-links=0
skip-external-locking
key_buffer_size = 16M
max_allowed_packet = 16M
table_open_cache = 64
sort_buffer_size = 512K
net_buffer_length = 8K
read_buffer_size = 256K
read_rnd_buffer_size = 512K
myisam_sort_buffer_size = 8M
#innodb_use_native_aio = 0
innodb_file_per_table
max_connections=70
max_user_connections=30
wait_timeout=10
interactive_timeout=50
long_query_time=5
!includedir /etc/mysql/conf.d/
Thanks
Re: Can't connect to MySQL anymore
What's about service status?
Code: Select all
service mysql status
Re: Can't connect to MySQL anymore
Code: Select all
● mariadb.service - MariaDB database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2018-02-20 11:26:53 CET; 45min ago
Process: 13369 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
Process: 13280 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
Process: 13274 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 13273 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
Main PID: 13369 (code=exited, status=1/FAILURE)
Feb 20 11:26:53 XXXXXX.fr systemd[1]: Starting MariaDB database server...
Feb 20 11:26:53 XXXXXX.fr mysqld[13369]: 2018-02-20 11:26:53 140639039488576 [Note] /usr/sbin/mysqld (mysqld 10.1.26-MariaDB-0+deb9u1) starting as process 13369 ...
Feb 20 11:26:53 XXXXXX.fr systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Feb 20 11:26:53 XXXXXX.fr systemd[1]: Failed to start MariaDB database server.
Feb 20 11:26:53 XXXXXX.fr systemd[1]: mariadb.service: Unit entered failed state.
Feb 20 11:26:53 XXXXXX.fr systemd[1]: mariadb.service: Failed with result 'exit-code'.
Re: Can't connect to MySQL anymore
What's error log in /var/log say?