What is the command for reindexing database?
I was asked to reindex today, after crashing last night, but I opted not to. Now I am getting a failure during transaction scanning and not connected.
./bitshares_client --rebuild-index
Quote from: Xeldal on November 29, 2014, 06:39:38 PM
./bitshares_client --rebuild-index
Ok I entered that exactly, but no success. What am I doing wrong?
Quote from: Carpet Ride on November 29, 2014, 06:55:18 PM
Quote from: Xeldal on November 29, 2014, 06:39:38 PM
./bitshares_client --rebuild-index
Ok I entered that exactly, but no success. What am I doing wrong?
>> ./bitshares_client --rebuild-index
Error: invalid command "./bitshares_client"
(Assuming Windows)
You can force it to reindex by temporarily changing the properties of the bitshares shortcut icon.
RightClick -> Properties
Target: "c:/.../BitShares.exe" just insert -rebuild-index "c:/.../BitShares.exe --rebuild-index"
Click OK then launch from that shortcut
Once started you can remove this change, otherwise it will try and rebuild every time you launch.
Quote from: Xeldal on November 29, 2014, 08:50:40 PM
(Assuming Windows)
You can force it to reindex by temporarily changing the properties of the bitshares shortcut icon.
RightClick -> Properties
Target: "c:/.../BitShares.exe" just insert -rebuild-index "c:/.../BitShares.exe --rebuild-index"
Click OK then launch from that shortcut
Once started you can remove this change, otherwise it will try and rebuild every time you launch.
I'm on a Mac, any help?
Quote from: Carpet Ride on November 30, 2014, 04:35:24 AM
I'm on a Mac, any help?
I just had this "failure during transaction scanning" and just doing the rebuild suggested. I'm on Linux but perhaps Mac is the same and has the bitshares_client in bitshares/programs/client or similar. So, change to that directory with cd and then try
./bitshares_client --rebuild-index
I was surprised not to see that as an option in the QT console too, as that might make it easier.
Try to make your wallet crash again.
Mine crashes every time i use the search market feature under the market tab.
Yuck..
I had hoped this would fix the simple "failure during transaction scanning" notification, as that appeared after my first try at selling a bitUSD. Unfortunately, instead I'm got into a worse mess.
./bitshares_client --rebuild-index
gives what I guess is expected:
QuoteClearing database index
Loading config from file: /home/davidpbrown/.BitShares/config.json
Initializing genesis state from built-in genesis file
Please be patient, this will take a few minutes...
Successfully re-indexed 1206245 blocks in 4740 seconds.
Blockchain size changed from 357MiB to 358MiB.
Not starting RPC server, use --server to enable the RPC interface
[1]+ Stopped ./bitshares_client --rebuild-index
then trying qt or qt with --reindex now barfs this error:
Quote
Initializing genesis state from built-in genesis file
Successfully re-indexed 0 blocks in 0 seconds.
Blockchain size changed from 0MiB to 0MiB.
terminate called after throwing an instance of 'fc::assert_exception'
[2]- Aborted ./BitShares --reindex
I'm still using 0.4.24 from a while back, so I don't know if this is a known problem.
???
Perhaps this follows on from an earlier problem I had selling the USD.. see https://bitsharestalk.org/index.php?topic=11271.msg148487#msg148487
Quote from: Xeldal on November 29, 2014, 08:50:40 PM
(Assuming Windows)
You can force it to reindex by temporarily changing the properties of the bitshares shortcut icon.
RightClick -> Properties
Target: "c:/.../BitShares.exe" just insert -rebuild-index "c:/.../BitShares.exe --rebuild-index"
Click OK then launch from that shortcut
Once started you can remove this change, otherwise it will try and rebuild every time you launch.
1) The bolded text should be: "C:\Program Files\BitSharesX\bin\BitShares.exe" --rebuild-index (quotation placement was incorrect)
2) I am having the same problem and this step did not work for me.
Interested in learning if there are other ways to fix these issues.
Everybody is having this. Somebody sent a transaction to an address with an invalid character in the public key and the blockchain apparently validated it.