On 05/26/2013 02:41 AM, Gary E. Miller wrote:
And got an error:
Database backend is exceedingly busy => Terminating (requesting
retry).
What you are seeing is a timeout trying to get the lock. I've had that
problem in spades. Someone posted a patch to improve that which works
for me, but it has not been accepted yet.
Thanks for the info Gary. I Tried a bit later and did not get the error
again. However, I wonder why I got the error in the first place. I am
not even putting this in cron yet. Running it manually for testing so
there wasn't another instance running.
> Check the email archives for it.
Will try searching the mailing list. I did search on the web and that is
how I found about the lock-timeout parameter.
How about the lock-timeout parameter? Shouldn't that help? Any idea on
the correct syntax for it?
I didn't install from source to patch. I used apt-get in Ubuntu.
Is there a list somewhere of what is new in the coming version? I saw it
is in RC2. Is it stable yet for production?
_______________________________________________
Csync2 mailing list
Csync2@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/csync2
