Hi ChristianEhrhardt, I went through the bug reports you mention, but this does not seem to apply to what we are experiencing.
We also tried many approaches thinking there was some problem with the data at first. The only thing we did not try yet is to recreate the ibdata/ib_log files because it seems like an overkill. Especially knowing the fact that we double checked the data and that, after a restart of the mysql service and fixing the replication status, queries actually seem to work and not make the server crash ... I believe this is somehow contextual, but I am at loss of ideas as to how to approach this. What I do know though is that it has to be somehow reproducible because the timeframe within which it happens is the same every day. Thanks in advance for any help, it would be more than welcome. On a side note, if there exists a way to elegantly rollback to version 5.7.19, I would be more than happy to hear about it too. Best regards, Eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729536 Title: InnoDB: Failing assertion: sym_node->table != NULL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1729536/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
