Shutdown delayed by mysql stop job

[laidlaws]

Running sta 2. Mysql is given 4 minutes and 12 seconds to shut down. It takes up every second then gets killed. This delays shutdown/rebooting. Looking around other forums, it is an upstream bug in systemd. The fix seems to be to set a shorter time limit. But is that still the current thinking?

[doktor5000]

It would help if you could at least provide some logs what mysql is doing during the shutdown ...

Code: Select all

journalctl -ab-1 -u mysql.service

should show the complete logs of the last boot (-b-1)

[filip]

Running sta 2.

Hm, sta2 is not released yet and I didn't notice this question on QA ML where I guess it belongs. Anyway, good luck with the fix.

[laidlaws]

"sudo journalctl -ab-1 -u mysql.service" gives no results. /var/log/mysqld/mysqld.log compressed and attached.

[laidlaws]

Command should have been:
sudo journalctl -ab-1 -u mysqld.service

Output of that command attached. The named service does not exist, but systemd didn't check.

Mysql is not running, so can't be stopped. A common problem on a fresh install.

Who said hooray for systemd?

[laidlaws]

From mysql's own log, the immediate problem seems to be that /etc/krb5.keytab (all over the Web) or /etc/krb5.keymap (in the log) does not exist. That file is created by heimdal-libs, which was not installed. Installing the package did not create the file.

[bittwister]

Running sta 2.

Hm, sta2 is not released yet and I didn't notice this question on QA ML where I guess it belongs. Anyway, good luck with the fix.

It is not a sta2 problem. It showed up on the mariadb-10.1.21-1.mga6 package update.

[laidlaws]

@ filip: No, the delay in shutting down was not a fault in itself. It was due to a bug in the mariadb package.
Added myself to Bug 20143 with a link to this thread.

[filip]

@laidlaws: Thx.