Open Silmerias opened 9 months ago
It seems like a non-existing channel was referenced. However, without a repro this is not really actionable for us and since the DB Backend has been entirely rewritten in #6263 I'll have to assume that the underlying issue has been fixed by that.
Ok, I'll update if this happen again.
@Krzmbrzl ok we found the issue, 100% reproductible.
Steps to reproduce:
I can not reproduce this with a 1.5.517 server/client and a Sqlite database.
So this issue either only occurs with the current mysql driver, or something else has to be true to trigger this bug.
I can not reproduce this with a 1.5.517 server/client and a Sqlite database.
SQLite doesn't enfore foreign key constraints by default due to backwards compatibility issues (iirc their first implementation had a bug that prevented checking and then they decided to keep it that way to not break existing tables). Thus, you'll never see a foreign key constraint error with Mumble's current DB implementation.
However, with the new implementation foreign key checks for SQLite are enabled as well.
@Silmerias thank you very much for the repro. I'll ensure that the issue will by fixed in the new DB impl!
I sould have mentioned this is happening with the MySQL driver.
Description
Murmur crashed with an SQL error after a while. It is related to channel listener see log.
QMYSQL3: Unable to execute statement Cannot add or update a child row: a foreign key constraint fails
Steps to reproduce
Mumble version
1.5.517
Mumble component
Server
OS
Linux
Reproducible?
Yes
Additional information
This is from a database that is 10 years old. Murmur did the SQL update at first startup.
Relevant log output
Screenshots
No response