Can't start mysql server on linux - mysql

I just installed mysql on Manjaro and when I try to start it using systemctl start mysql.service I get
Job for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xeu mariadb.service" for details.
So, I used the command systemctl status mysql.service I get
mariadb.service - MariaDB 10.9.3 database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; preset: disabled)
Active: failed (Result: exit-code) since Wed 2022-10-26 21:16:06 EET; 1min 51s ago
Docs: man:mariadbd(8)
https://mariadb.com/kb/en/library/systemd/
Process: 392 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 400 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl se>
Process: 441 ExecStart=/usr/bin/mariadbd $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
Main PID: 441 (code=exited, status=1/FAILURE)
Status: "MariaDB server is down"
CPU: 218ms
Oct 26 21:16:05 abomosa-latitudee6530 mariadbd[441]: 2022-10-26 21:16:05 0 [Note] InnoDB: Buffer pool(s) load completed at 221026 21:16:05
Oct 26 21:16:05 abomosa-latitudee6530 mariadbd[441]: 2022-10-26 21:16:05 0 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
Oct 26 21:16:06 abomosa-latitudee6530 mariadbd[441]: 2022-10-26 21:16:06 0 [Note] Server socket created on IP: '0.0.0.0'.
Oct 26 21:16:06 abomosa-latitudee6530 mariadbd[441]: 2022-10-26 21:16:06 0 [Note] Server socket created on IP: '::'.
Oct 26 21:16:06 abomosa-latitudee6530 mariadbd[441]: 2022-10-26 21:16:06 0 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.db' doesn't exist
Oct 26 21:16:06 abomosa-latitudee6530 mariadbd[441]: 2022-10-26 21:16:06 0 [ERROR] Aborting
Oct 26 21:16:06 abomosa-latitudee6530 mariadbd[441]: Warning: Memory not freed: 280
Oct 26 21:16:06 abomosa-latitudee6530 systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Oct 26 21:16:06 abomosa-latitudee6530 systemd[1]: mariadb.service: Failed with result 'exit-code'.
Oct 26 21:16:06 abomosa-latitudee6530 systemd[1]: Failed to start MariaDB 10.9.3 database server.

Related

MySQL Workbench error: Lost connection to MySQL server; Terminal error: Error: 13 (Permission denied)

Connection to the MySQL db was working fine 2 weeks ago, and without any editing or development activity it dropped out. I am using SQL Workbench to access. I can connect to the AWS EC2 instance via the AWS dashboard as well as SSH tunnel, can view/access files from filezilla connection.
The server is running WordPress application for a single website (https://farrahstribute.com/)
By examining past answers I tried:
(1) editing /etc/my.cnf and added this line
bind-address=0.0.0.0
after adding I rebooted server, however nothing changed, error with db persisting, so I removed the code I added
(2) editing /etc/hosts.allow and added these lines
mysqld: ALL : ALLOW
mysqld-max: ALL : ALLOW
after editing I rebooted server, however nothing changed, error with db persisting, so I removed the code that I added
From the terminal - this command systemctl status mysqld -l gave this result:
● mysqld.service - MySQL Server
Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2022-11-29 01:22:25 UTC; 14h ago
Docs: man:mysqld(8)
http://dev.mysql.com/doc/refman/en/using-systemd.html
Process: 3152 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS (code=exited, status=1/FAILURE)
Process: 2906 ExecStartPre=/usr/bin/mysqld_pre_systemd (code=exited, status=0/SUCCESS)
Main PID: 3152 (code=exited, status=1/FAILURE)
Status: "Server shutdown complete"
Error: 13 (Permission denied)
Nov 29 01:22:20 ip-172-31-28-111.ec2.internal systemd[1]: Starting MySQL Server...
Nov 29 01:22:25 ip-172-31-28-111.ec2.internal mysqld[3152]: 2022-11-29T01:22:25.558132Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.31) starting as process 3152
Nov 29 01:22:25 ip-172-31-28-111.ec2.internal mysqld[3152]: 2022-11-29T01:22:25.615516Z 0 [ERROR] [MY-010187] [Server] Could not open file '/var/log/mysqld.log' for error logging: Permission denied
Nov 29 01:22:25 ip-172-31-28-111.ec2.internal mysqld[3152]: 2022-11-29T01:22:25.615582Z 0 [ERROR] [MY-010119] [Server] Aborting
Nov 29 01:22:25 ip-172-31-28-111.ec2.internal mysqld[3152]: 2022-11-29T01:22:25.640431Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.31) MySQL Community Server - GPL.
Nov 29 01:22:25 ip-172-31-28-111.ec2.internal systemd[1]: mysqld.service: main process exited, code=exited, status=1/FAILURE
Nov 29 01:22:25 ip-172-31-28-111.ec2.internal systemd[1]: Failed to start MySQL Server.
Nov 29 01:22:25 ip-172-31-28-111.ec2.internal systemd[1]: Unit mysqld.service entered failed state.
Nov 29 01:22:25 ip-172-31-28-111.ec2.internal systemd[1]: mysqld.service failed.
Also from the terminal ran: systemctl status mysqld.service with output:
● mysqld.service - MySQL Server
Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2022-11-29 15:42:23 UTC; 2min 7s ago
Docs: man:mysqld(8)
http://dev.mysql.com/doc/refman/en/using-systemd.html
Process: 7247 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS (code=exited, status=1/FAILURE)
Process: 7220 ExecStartPre=/usr/bin/mysqld_pre_systemd (code=exited, status=0/SUCCESS)
Main PID: 7247 (code=exited, status=1/FAILURE)
Status: "Server shutdown complete"
Error: 13 (Permission denied)
Nov 29 15:42:22 ip-172-31-28-111.ec2.internal systemd[1]: Starting MySQL Server...
Nov 29 15:42:23 ip-172-31-28-111.ec2.internal mysqld[7247]: 2022-11-29T15:42:23.292440Z 0 [System] [MY-010116] [Server...7247
Nov 29 15:42:23 ip-172-31-28-111.ec2.internal mysqld[7247]: 2022-11-29T15:42:23.296242Z 0 [ERROR] [MY-010187] [Server]...nied
Nov 29 15:42:23 ip-172-31-28-111.ec2.internal mysqld[7247]: 2022-11-29T15:42:23.297482Z 0 [ERROR] [MY-010119] [Server]...ting
Nov 29 15:42:23 ip-172-31-28-111.ec2.internal mysqld[7247]: 2022-11-29T15:42:23.297889Z 0 [System] [MY-010910] [Server...GPL.
Nov 29 15:42:23 ip-172-31-28-111.ec2.internal systemd[1]: mysqld.service: main process exited, code=exited, status=1/FAILURE
Nov 29 15:42:23 ip-172-31-28-111.ec2.internal systemd[1]: Failed to start MySQL Server.
Nov 29 15:42:23 ip-172-31-28-111.ec2.internal systemd[1]: Unit mysqld.service entered failed state.
Nov 29 15:42:23 ip-172-31-28-111.ec2.internal systemd[1]: mysqld.service failed.
I also examined the error log /var/log/nginx/farrahstribute_error.log and found this error:
2022/11/29 00:55:06 [error] 3111#3111: *39 access forbidden by rule, client: 54.152.255.102, server: farrahstribute.com, request: "GET /.env HTTP/1.1", host: "34.199.116.152"
the issue is this line:
[ERROR] [MY-010187] [Server] Could not open file '/var/log/mysqld.log' for error logging: Permission denied
Which is supported by this error message:
Error: 13 (Permission denied)
So the issue is permissions to the /var/log/mysqld.log file. What is needed is to create permissions for mysql to access this file - running this command with a server reboot solved this issue:
$ sudo chown mysql:mysql /var/log/mysqld.log

Mariadb not starting

systemctl status mariadb:
root#server:/var/www/pterodactyl# systemctl status mariadb
● mariadb.service - MariaDB 10.7.3 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf
Active: failed (Result: exit-code) since Fri 2022-02-18 11:25:25 UTC; 8min ago
Docs: man:mariadbd(8)
https://mariadb.com/kb/en/library/systemd/
Process: 21815 ExecStartPost=/etc/mysql/debian-start (code=exited, status=203/EXEC)
Process: 21814 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 21802 ExecStart=/usr/sbin/mariadbd $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 21784 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status
Process: 21779 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 21771 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
Main PID: 21802 (code=exited, status=0/SUCCESS)
Status: "MariaDB server is down"
Feb 18 11:25:24 server.hostname.com mariadbd[21802]: 2022-02-18 11:25:24 0 [Note] InnoDB: FTS optimize thread exiting.
Feb 18 11:25:24 server.hostname.com mariadbd[21802]: 2022-02-18 11:25:24 0 [Note] InnoDB: Buffer pool(s) load aborted due to user instigated abort at 220218 11:25:24
Feb 18 11:25:24 server.hostname.com mariadbd[21802]: 2022-02-18 11:25:24 0 [Note] InnoDB: Dumping of buffer pool not started as load was incomplete
Feb 18 11:25:24 server.hostname.com mariadbd[21802]: 2022-02-18 11:25:24 0 [Note] InnoDB: Starting shutdown...
Feb 18 11:25:24 server.hostname.com mariadbd[21802]: 2022-02-18 11:25:24 0 [Note] InnoDB: Dumping of buffer pool not started as load was incomplete
Feb 18 11:25:25 server.hostname.com mariadbd[21802]: 2022-02-18 11:25:25 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
Feb 18 11:25:25 server.hostname.com mariadbd[21802]: 2022-02-18 11:25:25 0 [Note] InnoDB: Shutdown completed; log sequence number 8689222; transaction id 15019
Feb 18 11:25:25 server.hostname.com mariadbd[21802]: 2022-02-18 11:25:25 0 [Note] /usr/sbin/mariadbd: Shutdown complete
Feb 18 11:25:25 server.hostname.com systemd[1]: mariadb.service: Failed with result 'exit-code'.
Feb 18 11:25:25 server.hostname.com systemd[1]: Failed to start MariaDB 10.7.3 database server.
lines 1-26/26 (END)
Mariadb: 10.7.3
It stopped working when I installed and uninstalled DirectAdmin, reinstalling won't do anything

Transfering MySQL data from one system to the other

I've got all my files from my last MySQL(MariaDB InnoDB) Server and I just noticed I can't run those files on my new system. I don't have any .SQL backup of my server and my old system can't be booted to as far as I know.
I moved from Ubuntu Server 18.04 to CentOS 7 (and a RAID1 configuration), I cloned my original Ubuntu drive to a secondary drive.
Here are the files that I moved from my Ubuntu drive
/var/lib/mysql/ Files
[root#localhost ~]# systemctl status mariadb
● mariadb.service - MariaDB 10.2.32 database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf
Active: failed (Result: exit-code) since Thu 2020-07-09 20:20:46 PDT; 26s ago
Docs: man:mysqld(8)
https://mariadb.com/kb/en/library/systemd/
Process: 3281 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS --basedir=/usr $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
Process: 3132 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
Process: 3129 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Main PID: 3281 (code=exited, status=1/FAILURE)
Status: "MariaDB server is down"
Jul 09 20:20:46 localhost.localdomain systemd[1]: Starting MariaDB 10.2.32 database server...
Jul 09 20:20:46 localhost.localdomain mysqld[3281]: 2020-07-09 20:20:46 140603055900864 [Note] /usr/sbin/mysqld (mysqld 10.2.32-MariaDB-log) starting as process 3281 ...
Jul 09 20:20:46 localhost.localdomain mysqld[3281]: 2020-07-09 20:20:46 140603055900864 [Warning] Can't create test file /media/1TB/var/lib/mysql/localhost.lower-test
Jul 09 20:20:46 localhost.localdomain mysqld[3281]: [107B blob data]
Jul 09 20:20:46 localhost.localdomain mysqld[3281]: 2020-07-09 20:20:46 140603055900864 [ERROR] Aborting
Jul 09 20:20:46 localhost.localdomain systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
Jul 09 20:20:46 localhost.localdomain systemd[1]: Failed to start MariaDB 10.2.32 database server.
Jul 09 20:20:46 localhost.localdomain systemd[1]: Unit mariadb.service entered failed state.
Jul 09 20:20:46 localhost.localdomain systemd[1]: mariadb.service failed.
I'm not sure what I'm missing and why it won't start, I wish I would have kept the other system to export a SQL file which would have made my life so much easier.

Unable to start MariaDB - Ubuntu 18.04

I installed mariadb in my system. But I forgot the root password... I tried to reset root password by following "https://tecadmin.net/steps-to-reset-mariadb-root-password-in-linux/" and mysql official documentation.But no success.
But when I install fresh mariadb it is working. As per the official documention, while we installing mariadb it will ask root password. However in my case, it is never asking. However the server working on fresh install.
When i stop and restart server, it is keep on failing..
The error message I am getting is
mariadb.service - MariaDB 10.4.6 database server Loaded: loaded
(/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf Active: failed (Result: timeout) since Mon 2019-07-15 14:52:16 IST; 1min 46s ago
Docs: man:mysqld(8)
https://mariadb.com/kb/en/library/systemd/ Process: 10988 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER
$_WSREP_START_POSITION (code=exited, status=1/FAILURE) Process:
10829 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] &&
VAR= || VAR=/usr/bin/galera_recovery; [ $? -eq 0 ] && syst
Process: 10827 ExecStartPre=/bin/sh -c systemctl unset-environment
_WSREP_START_POSITION (code=exited, status=0/SUCCESS) Process: 10826 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d
/var/run/mysqld (code=exited, status=0/SUCCESS) Main PID: 10988
(code=exited, status=1/FAILURE) Status: "MariaDB server is down"
Jul 15 14:52:16 sonu mysqld[10988]: 2019-07-15 14:52:16 0 [Note]
InnoDB: Starting shutdown... Jul 15 14:52:16 sonu mysqld[10988]:
2019-07-15 14:52:16 0 [ERROR] Plugin 'InnoDB' init function returned
error. Jul 15 14:52:16 sonu mysqld[10988]: 2019-07-15 14:52:16 0
[ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. Jul
15 14:52:16 sonu mysqld[10988]: 2019-07-15 14:52:16 0 [Note] Plugin
'FEEDBACK' is disabled. Jul 15 14:52:16 sonu mysqld[10988]: 2019-07-15
14:52:16 0 [ERROR] Could not open mysql.plugin table. Some plugins may
be not loaded Jul 15 14:52:16 sonu mysqld[10988]: 2019-07-15 14:52:16
0 [ERROR] Failed to initialize plugins. Jul 15 14:52:16 sonu
mysqld[10988]: 2019-07-15 14:52:16 0 [ERROR] Aborting Jul 15 14:52:16
sonu systemd[1]: mariadb.service: Main process exited, code=exited,
status=1/FAILURE Jul 15 14:52:16 sonu systemd[1]: mariadb.service:
Failed with result 'timeout'. Jul 15 14:52:16 sonu systemd[1]: Failed
to start MariaDB 10.4.6 database server.
Please guide me towards resolution. Thanks for your time and waiting for your response.
Nagarajan S

Why MariaDB won't start on Fedora 20?

Here is the error i am getting
mariadb.service - MariaDB database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; disabled)
Active: failed (Result: exit-code) since Mon 2014-10-13 14:31:02 CEST; 10s ago
Process: 23609 ExecStartPost=/usr/libexec/mariadb-wait-ready $MAINPID (code=exited, status=1/FAILURE)
Process: 23608 ExecStart=/usr/bin/mysqld_safe --basedir=/usr (code=exited, status=0/SUCCESS)
Process: 23506 ExecStartPre=/usr/libexec/mariadb-prepare-db-dir %n (code=exited, status=0/SUCCESS)
Main PID: 23608 (code=exited, status=0/SUCCESS)
Oct 13 14:30:59 localhost.localdomain mariadb-prepare-db-dir[23506]: Support MariaDB development by buying support/new features from
Oct 13 14:30:59 localhost.localdomain mariadb-prepare-db-dir[23506]: SkySQL Ab. You can contact us about this at sales#skysql.com.
Oct 13 14:30:59 localhost.localdomain mariadb-prepare-db-dir[23506]: Alternatively consider joining our community based development effort:
Oct 13 14:30:59 localhost.localdomain mariadb-prepare-db-dir[23506]: http://mariadb.com/kb/en/contributing-to-the-mariadb-project/
Oct 13 14:30:59 localhost.localdomain mysqld_safe[23608]: 141013 14:30:59 mysqld_safe Logging to '/var/log/mariadb/mariadb.log'.
Oct 13 14:30:59 localhost.localdomain mysqld_safe[23608]: 141013 14:30:59 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
Oct 13 14:31:02 localhost.localdomain mysqld_safe[23608]: 141013 14:31:02 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
Oct 13 14:31:02 localhost.localdomain systemd[1]: mariadb.service: control process exited, code=exited status=1
Oct 13 14:31:02 localhost.localdomain systemd[1]: Failed to start MariaDB database server.
Oct 13 14:31:02 localhost.localdomain systemd[1]: Unit mariadb.service entered failed state.
THis is the mariadb.log file:
Im not really understanding this error, because the sock file has not been created and my server hasn't succesfully started...
141013 14:37:28 [ERROR] Can't start server : Bind on unix socket: Permission denied
141013 14:37:28 [ERROR] Do you already have another mysqld server running on socket: /var/run/mysql/mysql.sock ?
141013 14:37:28 [ERROR] Aborting
141013 14:37:28 InnoDB: Starting shutdown...
141013 14:37:29 InnoDB: Shutdown completed; log sequence number 1597945
141013 14:37:29 [Note] /usr/libexec/mysqld: Shutdown complete
I installed it fresh several times and I can't seem to figure out what the error is in the logs. I am running everything as root. Thanks.