Error: Transaction log needs to be enabled in the cluster

Created by Steve Place, Modified on Mon, 05 Jun 2023 at 12:11 PM by Steve Place

This error occurs when the transaction.logging property is set to false in one or more of your databases. You check this property with stardog-admin metadata get -o transaction.logging {dbname}. Once you have your list of databases with this property disabled, run the following steps:

stardog-admin db offline {dbname}
stardog-admin metadata set -o transaction.logging=true -- {dbname}
stardog-admin db online {dbname}
# repeat lines 1-3 for all databases where `transaction.logging` was set to false
stardog-admin cluster stop
# wait for all nodes to shutdown and verify
# start the cluster, one node at a time


After that setting is fixed for the cluster, the cluster will recreate the transaction log file when the nodes start.


Setting transaction.logging=true in your stardog.properties will not override any databases where transaction.logging is set to false. That is why you have to perform the above steps.

For more on transaction logging, see the docs.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article