Forums before death by AOL, social media and spammers... "We can't have nice things"
|    linux.debian.bugs.dist    |    Ohh some weird Debian bug report thing    |    28,835 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 26,919 of 28,835    |
|    Ben Morris to All    |
|    Bug#1127431: [debian-mysql] Processed: m    |
|    09 Feb 26 16:40:01    |
      From: bugs@benmorris.org.uk              This is a multi-part message in MIME format.       On 09/02/2026 01:56, Otto Kekäläinen wrote:       > In both cases seems MariaDB is doing crash recovery and then crashing again.              This is just because Akonadi keeps trying to restart. I'll attach a log       showing the first crash after upgrade, without the crash recovery attempt.              > The latter log has this line:       > 2026-02-09 0:54:21 0 [ERROR] Can't open and lock privilege tables: Table       > 'mysql.servers' doesn't exist       >       > But there is no way to tell if this is the cause or a symptom of the crash.              I don't know why that is happening on my machine but not on Matthias's       machine, but it may be unrelated to this bug. That message also appears       when using the old version, which apparently works fine. I'll attach a       log of that too, for comparison.              For both logs, I've set log_warnings=10 in       ~/.local/share/akonadi/mysql.cnf and disabled AppArmor enforcement. It       doesn't look like there is a meaningful difference in the log files       before the signal handler is invoked.              I'm not sure why the included backtrace only goes as far as the signal       handler. I've added core_file to mysql.cnf and obtained a more       interesting backtrace with gdb.              "gdb-full.bt" is the backtrace as recommended by       https://mariadb.com/docs/server/reference/product-development/ma       iadb-fault-finding/how-to-produce-a-full-stack-trace-for-mariadb       #getting-backtraces-with-gdb-on-linux              Frankly, I can't comprehend that file, so I've also included a simple       backtrace for Thread 1, as "gdb.bt"              There does seem to be some hint of a cause in the backtrace - in 11.8.5,       get_schema_privileges_for_show() didn't call acl_get_all3(). See Thread       1, frames #9 and #10.                     Ben       [SoupGate killed MIME-encoded file mysql-sad.err (6909 bytes)]       [SoupGate killed MIME-encoded file mysql-happy.err (3019 bytes)]       [SoupGate killed MIME-encoded file gdb-full.bt (102651 bytes)]       [SoupGate killed MIME-encoded file gdb.bt (5449 bytes)]              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca