05-12-2010 11:40 AM
When I change my configuration on the cluster and tried save the configuration using commit send the next error:
error: configuration database modified
error: remote lock-configuration failed on node1
Do you know what is the problem?
05-12-2010 06:15 PM
Check the following post.
If this solves your problem, please mark this post as "Accepted Solution". Kudos are appreciated.
08-23-2012 06:11 AM
If this worked for you please flag my post as an "Accepted Solution".
03-27-2015 03:24 PM
Yes but did you have to enter 'configure shared' to get into 'edit' mode? Also did the 'commit synchronize force' command cause a traffic drop or performance hit or any adverse results.
Thanks in advance,
04-10-2016 02:44 PM
I had a similear issue but I resolved it by connecting to the secondary node and do a rollback of the configuration. I belive it's a better way of solving it than commit synchronize force. In my case it solved the issue. I have created a blogpost on it here: https://networksandrants.wordpress.com/2016/04/10/secondary-node-locked-when-commiting/