Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error -2 #29

Closed
jjj092353 opened this issue Jul 15, 2016 · 3 comments
Closed

error -2 #29

jjj092353 opened this issue Jul 15, 2016 · 3 comments
Labels

Comments

@jjj092353
Copy link

jjj092353 commented Jul 15, 2016

resynched with new wallet:

root@smh-us-stratum:/usr/local/bin# casinocoind getblockcount
1578164
root@smh-us-stratum:/usr/local/bin# casinocoind getblockhash
error: {"code":-2,"message":"Safe mode: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."}
root@smh-us-stratum:/usr/local/bin# casinocoind getbalance
error: {"code":-2,"message":"Safe mode: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."}
root@smh-us-stratum:/usr/local/bin# casinocoind getbalance
error: {"code":-2,"message":"Safe mode: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."}
root@smh-us-stratum:/usr/local/bin# ^C
root@smh-us-stratum:/usr/local/bin# 
@ajochems
Copy link

There are some nodes that report the same problem. We got those solved by executing the following steps, you might try the same:

  • Download a full copy of the blockchain from the main seed from http://api.casinocoin.org/downloads/csc-blockchain.tar.gz
  • Create a backup of the blocks and chainstate directories in your daemon data directory.
  • Create a backup of your wallet.dat file
  • Then after the backup delete those two directories and extract the downloaded file in your datadir with: tar xvzf csc-blockchain.tar.gz
  • Restart your daemon with the -rescan option. If you run a full tx index you may need to run with the -reindex option instead, just look at the debug.log file when starting.
  • If your daemon is up to speed again stop and restart it without the -rescan option

@ajochems
Copy link

Has your issue been resolved?

@kepoly kepoly added the bug label Jul 18, 2016
@ajochems
Copy link

Guess it has as there is no response!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants