Failed to start MariaDB 10.1.38 database server.

[stevenjwilliams83]

expedition@pan-expedition:~$ service mysql status

● mariadb.service - MariaDB 10.1.38 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 Thu 2019-04-18 17:46:00 CDT; 31min ago

     Docs: man:mysqld(8)

           https://mariadb.com/kb/en/library/systemd/

Main PID: 1544 (code=exited, status=1/FAILURE)

   Status: "MariaDB server is down"

Apr 18 17:45:58 pan-expedition mysqld[1544]: 2019-04-18 17:45:58 140143676705024 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.42-84

Apr 18 17:45:58 pan-expedition mysqld[1544]: 2019-04-18 17:45:58 140142706677504 [Note] InnoDB: Dumping buffer pool(s) not yet started

Apr 18 17:45:58 pan-expedition mysqld[1544]: 2019-04-18 17:45:58 140143676705024 [Note] Plugin 'FEEDBACK' is disabled.

Apr 18 17:45:58 pan-expedition mysqld[1544]: 2019-04-18 17:45:58 140143676705024 [Note] Recovering after a crash using tc.log

Apr 18 17:45:58 pan-expedition mysqld[1544]: 2019-04-18 17:45:58 140143676705024 [ERROR] Can't init tc log

Apr 18 17:45:58 pan-expedition mysqld[1544]: 2019-04-18 17:45:58 140143676705024 [ERROR] Aborting

Apr 18 17:46:00 pan-expedition systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE

Apr 18 17:46:00 pan-expedition systemd[1]: Failed to start MariaDB 10.1.38 database server.

Apr 18 17:46:00 pan-expedition systemd[1]: mariadb.service: Unit entered failed state.

Apr 18 17:46:00 pan-expedition systemd[1]: mariadb.service: Failed with result 'exit-code'.

lines 1-20/20 (END)

Whats going on here? I have rebooted many times, I am on the latest beta. 

[stevenjwilliams83]

expedition@pan-expedition:~$ sudo mysqlcheck auto-repair

mysqlcheck: Got error: 2002: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2 "No such file or directory") when trying to connect

expedition@pan-expedition:~$ service mysqld start

==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===

Authentication is required to start 'mariadb.service'.

Authenticating as: expedition,,, (expedition)

Password:

==== AUTHENTICATION COMPLETE ===

Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details.

expedition@pan-expedition:~$

[stevenjwilliams83]

root@pan-expedition:/home/expedition# journalctl -xe

Apr 19 15:32:33 pan-expedition systemd[1]: Failed to start MariaDB 10.1.38 database server.

-- Subject: Unit mariadb.service has failed

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- Unit mariadb.service has failed.

--

-- The result is failed.

Apr 19 15:32:33 pan-expedition systemd[1]: mariadb.service: Unit entered failed state.

Apr 19 15:32:33 pan-expedition systemd[1]: mariadb.service: Failed with result 'exit-code'.

Apr 19 15:32:57 pan-expedition systemd[1]: Time has been changed

-- Subject: Time change

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- The system clock has been changed to REALTIME microseconds after January 1st, 1970.

Apr 19 15:32:57 pan-expedition systemd-journald[379]: Forwarding to syslog missed 26 messages.

-- Subject: One or more messages could not be forwarded to syslog

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- One or more messages could not be forwarded to the syslog service

-- running side-by-side with journald. This usually indicates that the

-- syslog implementation has not been able to keep up with the speed of

-- messages queued.

Apr 19 15:32:57 pan-expedition systemd[49748]: Time has been changed

-- Subject: Time change

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- The system clock has been changed to REALTIME microseconds after January 1st, 1970.

Apr 19 15:33:31 pan-expedition systemd[1]: Time has been changed

-- Subject: Time change

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- The system clock has been changed to REALTIME microseconds after January 1st, 1970.

Apr 19 15:33:31 pan-expedition systemd-journald[379]: Forwarding to syslog missed 2 messages.

-- Subject: One or more messages could not be forwarded to syslog

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

[stevenjwilliams83]

Anyone?

[dgildelaig · Accepted solution]

Check the bottom of this other post.

It may be the same case:

https://live.paloaltonetworks.com/t5/Expedition-Discussions/Incorrect-User-or-Password-from-GUI/m-p/...

[stevenjwilliams83]

So the issue was the tc log. So after I found that on a general Linux site, it started working. Thanks for the follow up.