Yes, I did run using valgrind, while it reported some uninitialized variables,
not really any memory corruptions. Attached, the log from node0. Similarly,
Well, uninitialised variables are exactly what I would expect could lead to
things looking like you have shown so far. So if you have Valgrind errors, you
should definitely start by fixing them.
However, I see no messages from Valgrind in the log you attached?!?
So please, repeat the exact problem you get (assertion during rollback) while
running with Valgrind. Provide the exact command you used to get the error in
this particular run, and the correct log that shows the Valgrind errors about
uninitialised variables, and I can give more suggestions for how to fix.
debug=+d did not help. Where I should add some output to narrow down the place
where the corruption happens.
It did produce the output, not yet found the reason, some of the
output just before corruption