This error should never happen on a healthy database. The only case I've debugged with such an issue was on a system that had a corrupted database due to an out-of-space situation.
The reason why this should never happen is clear in the code of the txn package: before anything is ever done with regards to a transaction, the document that represents that transaction is inserted into the database. Just after that will the id of the referred transaction be used to tag the documents that were affected by it. What the error is saying is that while attempting to flush pending transactions on an affected document it could find a reference to a transaction that does not exist. Things that might lead to such a situation include, for example: 1. A corrupted database 2. An abrupt shutdown on a database without a journal 3. A capped transaction collection that is eating its tail while old transactions are still in use -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318366 Title: jujud on state server panic misses transaction in queue To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1318366/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
