Hi again, Here are the more detailed files and info regarding your questions. The attachments contain the non-truncated output from the systemctl and the journalctl commands. The attachment 2020-05-08..... contains the content of the my.cnf files. It looks like no special options were given here, all is pretty standard - as I never changed anything in these files. db At least not as I am aware of, since I installed mariadb last year and no problems sinces yesterday... Further to your question on the repo, I am using the CENTOS8 packages, version 10.3 :

[root@server1 Documents]# rpm -qa | grep maria mariadb-server-utils-10.3.17-1.module_el8.1.0+257+48736ea6.x86_64 mariadb-backup-10.3.17-1.module_el8.1.0+257+48736ea6.x86_64 mariadb-connector-c-3.0.7-1.el8.x86_64 mariadb-gssapi-server-10.3.17-1.module_el8.1.0+257+48736ea6.x86_64 mariadb-connector-c-config-3.0.7-1.el8.noarch mariadb-10.3.17-1.module_el8.1.0+257+48736ea6.x86_64 mariadb-errmsg-10.3.17-1.module_el8.1.0+257+48736ea6.x86_64 mariadb-server-10.3.17-1.module_el8.1.0+257+48736ea6.x86_64 mariadb-common-10.3.17-1.module_el8.1.0+257+48736ea6.x86_64 [root@server1 Documents]#

Regarding ulimit, to my knowledge, I have never changed anything here since I installed mariadb.... The only thing I can find on this is the executable at /usr/bin/ulimit As said, my biggest question and concern is: how could this suddenly happen yesterday, without me doing any changes/updates in the server in the last 2 weeks? I am very grateful for any comments/hints to solve this. Could a forced re-installl of the above packages help to put everything back to"standard"? /Ralf On Sunday 17/05/2020 at 16:15, Gordan Bobic wrote:

There are several obvious issues in what you posted, to so with ulimit. You need to look at your service scripts and make sure that they set suitable limits for what you are configuring in my.cnf. Are you using the CentOS 8 bundled MariaDB 10.3 or the packages from the MariaDB repositories?

Your journalctl output seems incomplete. systemctl status output may also be useful (make sure neither is truncated in width).

Comment out all of your tuning options and see if it starts then. Unless you know _exactly_ what you are doing or had somebody who _really_ knows what they are doing change any options other than innodb_buffer_pool_size, you should probably leave them at defaults.

On Sun, May 17, 2020 at 3:00 PM Ralf Hartings <ralf@hartings.se> wrote:

...

Hi

My up-to-date Wordpress website running with mariadb 10.3 on CentOS8 (up to date) has been running for a long time without any issues. Suddenly, yesterday, my server became unreachable and did not respond to anything. Only power off/on helped to get it to respond again, but the website is down. I did not update the server in the last 2 weeks. No changes whatsoever.

The logs show the mariadb server is restarting and crashing continuously. I switched off the mariadb.service to avoid any possible further issues, as I run a mailserver on the same machine (which runs just fine now).

Please look at my post in the CentOS forum: https://forums.centos.org/viewtopic.php?f=54&t=74436&p=313469#p313469 The people there are great experts in CentOS, but probably no experts in mariadb in the same way as you are, and I really would like to get my site up again ASAP.

Thanks a lot for reading this post and helping me out on this!

/Ralf

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