#maria Log v0.1

logs Catalogue

This page loads from the db, refresh as and when. It displays 24 hrs
For older data http://marialog.archivist.info/previous.php, logs go back to 2009-01-18
Some user stats
Table logs
2017-12-17 09:58:36
Hi there! So I've just upgraded from mysql to mariadb in debian and the painless upgrade process just broke my system. Could anybody link me a troubleshoot guide to find out what went wrong?
2017-12-17 10:05:34
bodom: Broke? There may be differences your applications might not like.
2017-12-17 10:06:11
bodom: Did the updated server not restart properly?
2017-12-17 10:06:19
Xgc: yep, the main difference they don't like is the daemon does not start at all
2017-12-17 10:07:38
bodom: This might be a question for the debian package manager / maintainer. Not sure if someone here matches that criteria. Without that, look for the error log.
2017-12-17 10:08:37
Xgc: looks like it's empty
2017-12-17 10:10:18
bodom: If you can find out how debian starts the server, you could try that by hand... or just start the server normally by hand. Then check for errors.
2017-12-17 10:11:51
Xgc: it uses systemd. If i just "sudo -u mysql mysqld", then it apparently starts correctly
2017-12-17 10:11:52
bodom: Some systems use a system logger to handle some messages. These would not be found in the normal database log files.
2017-12-17 15:50:23
galera docs say of multi-master conflict
2017-12-17 15:50:25
When two transactions come into conflict, the later of the two is rolled back by the cluster. The client application registers this rollback as a deadlock error. Ideally, the client application should retry the deadlocked transaction, but not all client applications have this logic built in.
2017-12-17 15:51:17
when implementing such a retry mechanism in the client, is there any value in waiting for a short time before trying again?