Update:
In the Argentum Data Dir:
Create a file called "DB_CONFIG"
In this file place the following:
Once saved, Delete and resync the arg blockchain after backup the wallet.dat
You should now be good to go
In the Argentum Data Dir:
Create a file called "DB_CONFIG"
In this file place the following:
Code:
set_lk_max_locks 537000
set_lk_max_objects 537000
Once saved, Delete and resync the arg blockchain after backup the wallet.dat
You should now be good to go
Thanks for posting back. Looks like it's because 4.8 version libs were used.
Nope, 5.3.
The error is due to berkerly db being used which has a restriction called "locks". The block where clients forked meant that there wernt enough locks for the block to be processed therefore leading to the fork. By switching to leveldb this scenario could be avoided in the future.
PS. for anyone doubting me. Look into the bitcoin fork between v0.7 bdb clients and v0.8 level db clients.
So to be clear, EVERYONE running an Argentum client is going to experience this issue, unless they explicitly configure the DB_CONFIG parameters that Ahmed was kind enough to post. This means the wallet will be unusable for anyone who simply downloads the client from the website and has never heard of Bitcointalk.
Baritus, fix this, kill ARG, or hand it over to someone else.
I'm already looking for a solution.
