Could not serialize access due to read/write dependencies among transactions

This error is appearing in my systemd log.

May 21 06:36:37 redbox.tankie.tube peertube[7954]: Committing transaction f6815ddb-c2c7-43a8-8f42-503e922ed0b8 failed with error "could not serialize access due to read/write dependencies among transactions". We are killing its connection as it is now in an undetermined state.
May 21 06:37:43 redbox.tankie.tube peertube[7954]: Committing transaction 9791db50-7ecb-4682-a496-636e159fc0df failed with error "could not serialize access due to read/write dependencies among transactions". We are killing its connection as it is now in an undetermined state.
May 21 06:40:49 redbox.tankie.tube peertube[7954]: Committing transaction a1a0ba10-33d3-4aba-a062-a48581285d22 failed with error "could not serialize access due to read/write dependencies among transactions". We are killing its connection as it is now in an undetermined state.

What does it mean? Is it cause for concern?

If all is working as intended then please pardon my curiosity.

Hi,

This is an expected behaviour so PeerTube will retry the transaction. But I’m surprised you see this log: how did you install peertube?

1 Like

I followed the production guide. I haven’t seen the errors in quite a while; they happened right after I did a server migration. I was also restarting the peertube service a lot while trying to get SMTP working.

Glad to know it’s expected; thank you for the reassurance!

What kind of transaction is it talking about? A database transaction? I have terminal curiousity, sorry.

Yes, a database (postgresql) transaction. See PostgreSQL: Documentation: 16: 13.2. Transaction Isolation

1 Like