← Back to team overview

maria-discuss team mailing list archive

  1. maria-discuss team
  2. Mailing list archive
  3. Message #06375

Re: Maria-db refuses to start

  Thread Previous • Date Previous • • Thread Next 
Op 10-11-2022 om 13:39 schreef Reindl Harald:



Am 10.11.22 um 12:06 schrieb Jogchum Reitsma:

Op 08-11-2022 om 22:54 schreef Daniel Black:

On Wed, Nov 9, 2022 at 12:01 AM Jogchum Reitsma
<jogchum.reitsma@xxxxxxxxx>  wrote:

<...>
The directory /var/run/mysql doesn't exist
2022-11-08 13:37:33 0 [ERROR] Do you already have another server running on socket: /var/run/mysql/mysql.sock ? 
This guess of an error should be fixed.
Well, in the meantime I have a running database, thanks to all the help I get here. 

But I'm not quite out of trouble yet.
The last problem with starting /usr/local/mariadb-10.6.10-linux-systemd-x86_64/bin/mariadbd was solved by chmod 777 /var/run/mysql; this was needed because I start mariadb as a plain user for the moment. chmod on /var/log/msql gave me logging > 
Once again I'm at a loss here - what causes mysqld not to start?

Any further help dearly appreciated....
either "in the meantime I have a running database" or "what causes mysqld not to start" are possible 

Maybe I did not express myself clearly enough:
1) "in the meantime I have a running database": I can have a running database, but only by sarting an older version (10.6.10) in an unorthodox way, i.e. by issuing /usr/local/mariadb-10.6.10-linux-systemd-x86_64/bin/mariadbd as a normal user. Of course that's not what I want as a definitive solution, but this way I can get to my data.
2) "what causes mysqld not to start": starting the mariadb version that is supplied by my distro, thedefault way, i.e. by issuing systemctl start mariadb.service, des not work, and gives the errors I pasted in my previous message. 

I hope this clarifies the what I meant to say.


and when it comes to "chmod on /var/log/msql gave me logging" show them
for the sake of god open "/usr/lib/systemd/system/mariadb.service" and remove or comment out the "ExecStartPre" until your problems are solved
"ExecStartPre=/usr/libexec/mysql/mysql-systemd-helper upgrade (code=exited, status=1/FAILURE)" is some distribution sepcific nonsense
I have no idea what these "install" and "upgrade " ExecStartPre do, but I commented them  out, did a systemctl daemon-reload, and issued systemctl start mariadb.service again. 

Again with no luck:

systemctl status mariadb.service
×mariadb.service - MariaDB database server
    Loaded: loaded (/usr/lib/systemd/system/mariadb.service; disabled; preset: disabled) 
   Drop-In: /etc/systemd/system/mariadb.service.d
            └─override.conf
    Active: failed(Result: exit-code) since Thu 2022-11-10 20:22:35 CET; 17s ago 
      Docs: man:mysqld(8)
https://mariadb.com/kb/en/library/systemd/
   Process: 35754 ExecStart=/usr/libexec/mysql/mysql-systemd-helper start (code=exited, status=1/FAILURE) 
  Main PID: 35754 (code=exited, status=1/FAILURE)
    Status: "MariaDB server is down"

       CPU: 80ms

##############################################################################################################

journalctl -xeu mariadb.service

nov 10 20:20:51 linux-mkay systemd[1]: Starting MariaDB database server...
░░ Subject: A start job for unit mariadb.service has begun execution
░░Defined-By: systemd
░░Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░A start job for unit mariadb.service has begun execution.
░░
░░The job identifier is 702208.
nov 10 20:20:51 linux-mkay mysql-systemd-helper[35509]: Checking MySQL configuration for obsolete options... nov 10 20:20:51 linux-mkay mysql-systemd-helper[35509]: Trying to run upgrade of MySQL databases... nov 10 20:20:51 linux-mkay mysql-systemd-helper[35509]: Stale files from previous upgrade detected, cleaned them up nov 10 20:20:51 linux-mkay mysql-systemd-helper[35509]: Running protected MySQL... nov 10 20:20:51 linux-mkay mysql-systemd-helper[35509]: Waiting for MySQL to start nov 10 20:20:51 linux-mkay mysql-systemd-helper[35533]: 2022-11-10 20:20:51 0 [Note] /usr/sbin/mysqld (server 10.9.3-MariaDB) starting as process 35533 ... 
nov 10 20:21:51 linux-mkay mysql-systemd-helper[35509]: MySQL is still dead
nov 10 20:21:51 linux-mkay mysql-systemd-helper[35509]: MySQL didn't start, can't continue nov 10 20:21:51 linux-mkay systemd[1]: mariadb.service: Control process exited, code=exited, status=1/FAILURE 
░░ Subject: Unit process exited
░░Defined-By: systemd
░░Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░An ExecStartPre= process belonging to unit mariadb.service has exited.
░░
░░The process' exit code is 'exited' and its exit status is 1.
nov 10 20:21:51 linux-mkay systemd[1]: mariadb.service: Failed with result 'exit-code'. 
░░ Subject: Unit failed
░░Defined-By: systemd
░░Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░The unit mariadb.service has entered the 'failed' state with result 'exit-code'. nov 10 20:21:51 linux-mkay systemd[1]: Failed to start MariaDB database server. 
░░ Subject: A start job for unit mariadb.service has failed
░░Defined-By: systemd
░░Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░A start job for unit mariadb.service has finished with a failure.
░░
░░The job identifier is 702208 and the job result is failed.
nov 10 20:22:34 linux-mkay systemd[1]: Starting MariaDB database server...
░░ Subject: A start job for unit mariadb.service has begun execution
░░Defined-By: systemd
░░Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░A start job for unit mariadb.service has begun execution.
░░
░░The job identifier is 702738.
nov 10 20:22:34 linux-mkay mysql-systemd-helper[35754]: 2022-11-10 20:22:34 0 [Note] /usr/sbin/mysqld (server 10.9.3-MariaDB) starting as process 35754 ... nov 10 20:22:35 linux-mkay systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE 
░░ Subject: Unit process exited
░░Defined-By: systemd
░░Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░An ExecStart= process belonging to unit mariadb.service has exited.
░░
░░The process' exit code is 'exited' and its exit status is 1.
nov 10 20:22:35 linux-mkay systemd[1]: mariadb.service: Failed with result 'exit-code'. 
░░ Subject: Unit failed
░░Defined-By: systemd
░░Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░The unit mariadb.service has entered the 'failed' state with result 'exit-code'. nov 10 20:22:35 linux-mkay systemd[1]: Failed to start MariaDB database server. 
░░ Subject: A start job for unit mariadb.service has failed
░░Defined-By: systemd
░░Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░A start job for unit mariadb.service has finished with a failure.
░░
░░The job identifier is 702738 and the job result is failed.

##########################################################################################################################

The log from this failure (/var/log/mysqld.log):

2022-11-10 20:22:34 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2022-11-10 20:22:34 0 [Note] InnoDB: Number of transaction pools: 1
2022-11-10 20:22:34 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2022-11-10 20:22:34 0 [Note] InnoDB: Using Linux native AIO
2022-11-10 20:22:34 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB 2022-11-10 20:22:34 0 [Note] InnoDB: Completed initialization of buffer pool 
2022-11-10 20:22:34 0 [ERROR] InnoDB: File ./ib_logfile0 was not found
2022-11-10 20:22:34 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error 
2022-11-10 20:22:34 0 [Note] InnoDB: Starting shutdown...
2022-11-10 20:22:35 0 [ERROR] Plugin 'InnoDB' init function returned error.
2022-11-10 20:22:35 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 
2022-11-10 20:22:35 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-11-10 20:22:35 0 [Warning] 'innodb-file-format' was removed. It does nothing now and exists only for compatibility with old my.cnf files. 
2022-11-10 20:22:35 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2022-11-10 20:22:35 0 [ERROR] Aborting

##############################################################################################################################

No idea how to solve this, again...

regards, Jogchum







_______________________________________________
Mailing list: https://launchpad.net/~maria-discuss
Post to     : maria-discuss@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp

Follow ups

References

  Thread Previous • Date Previous • • Thread Next