[debian-mysql] Bug#900398: mariadb-server-10.1: postinst fails since official rebuild

[Paul Gevers]

Hi Faustin,

On 13-06-18 18:52, Faustin Lammler wrote:
> So regarding our issue, I guess that the DB crashed or the tc.log file
> got corrupt (or both).

All I can say is that that file was empty.

paul at testavoira ~ $ ll /var/lib/mysql/tc.log.org
-rw-rw---- 1 mysql mysql 0 apr  9 18:14 /var/lib/mysql/tc.log.org

Interesting to look at that date, it seems that MariaDB crashed before I
updated (which happened on 2018-05-18 20:56:49 according to my apt
history) and I just didn't notice.

> Do you know how to reproduce this? Do you have any steps that I could
> try?

I have no idea what happened on 9 April that would have caused this. I
don't rule out that I ran out of space on that disk (happens occasionally).

So I guess this bug should be re-titled to something like "during
startup mariadb-server should handle corrupt tc.log more gracefully". An
empty tc.log appears to me as save to ignore as it doesn't contain
useful information anyways apart from its timestamp.

Paul

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-mysql-maint/attachments/20180613/cde3b97d/attachment.sig>