Title: bitcoin-cli error code -28 Post by: sanoplay on March 04, 2019, 05:43:58 PM Hello,
I've started running a Bitcoin full node on my AWS instance (t2.micro, ubuntu 18.04). Everything worked fine, it successfuly downloaded about 360000 blocks. But one day my instance stopped for some time (i don't know why), but i fix it. And after this crash i can't use any bitcoin-cli commands. e.g If i type Code: bitcoin-cli getblockcount Code: bitcoin-cli -getinfo error code: -28 error message: Pruning blockstore... I didin't find anything about it and i really don't know what to do Thank you in advance! Title: Re: bitcoin-cli error code -28 Post by: darosior on March 04, 2019, 06:20:42 PM -28 usually means your client (Bitcoin Core) is still starting/warming-up, but looks like the message says otherwise. Your first command throw error because you forget to add - though. No need to add `-` before cli calls, actually passing calls with it will faill.It would be great if you could share your debug.log file, so we'd have easier time identifying the problem Title: Re: bitcoin-cli error code -28 Post by: sanoplay on March 04, 2019, 06:33:38 PM -28 usually means your client (Bitcoin Core) is still starting/warming-up, but looks like the message says otherwise. Your first command throw error because you forget to add - though. It would be great if you could share your debug.log file, so we'd have easier time identifying the problem When i run cat debug.log i recived this. 2019-03-03T17:46:42Z Bitcoin Core version v0.17.1 (release build) 2019-03-03T17:46:42Z InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1 2019-03-03T17:46:42Z Assuming ancestors of block 0000000000000000002e63058c023a9a1de233554f28c7b21380b6c9003f36a8 have valid signatures. 2019-03-03T17:46:42Z Setting nMinimumChainWork=0000000000000000000000000000000000000000028822fef1c230963535a90d 2019-03-03T17:46:42Z Prune configured to target 600MiB on disk for block and undo files. 2019-03-03T17:46:42Z Using the 'sse4(1way),sse41(4way),avx2(8way)' SHA256 implementation 2019-03-03T17:46:42Z Using RdRand as an additional entropy source 2019-03-03T17:46:42Z Default data directory /home/ubuntu/.bitcoin 2019-03-03T17:46:42Z Using data directory /home/ubuntu/.bitcoin 2019-03-03T17:46:42Z Using config file /home/ubuntu/.bitcoin/bitcoin.conf 2019-03-03T17:46:42Z Using at most 12 automatic connections (1024 file descriptors available) 2019-03-03T17:46:42Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements 2019-03-03T17:46:42Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements 2019-03-03T17:46:42Z Using 0 threads for script verification 2019-03-03T17:46:42Z scheduler thread start 2019-03-03T17:46:42Z HTTP: creating work queue of depth 16 2019-03-03T17:46:42Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation. 2019-03-03T17:46:42Z HTTP: starting 4 worker threads 2019-03-03T17:46:42Z Using wallet directory /home/ubuntu/.bitcoin 2019-03-03T17:46:42Z init message: Verifying wallet(s)... 2019-03-03T17:46:43Z Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2019-03-03T17:46:43Z Using wallet wallet.dat 2019-03-03T17:46:43Z BerkeleyEnvironment::Open: LogDir=/home/ubuntu/.bitcoin/database ErrorFile=/home/ubuntu/.bitcoin/db.log 2019-03-03T17:46:43Z Cache configuration: 2019-03-03T17:46:43Z * Using 2.0MiB for block index database 2019-03-03T17:46:43Z * Using 8.0MiB for chain state database 2019-03-03T17:46:43Z * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space) 2019-03-03T17:46:43Z init message: Loading block index... 2019-03-03T17:46:43Z Opening LevelDB in /home/ubuntu/.bitcoin/blocks/index 2019-03-03T17:46:43Z Opened LevelDB successfully 2019-03-03T17:46:43Z Using obfuscation key for /home/ubuntu/.bitcoin/blocks/index: 0000000000000000 2019-03-03T17:46:46Z LoadBlockIndexDB: last block file = 302 2019-03-03T17:46:46Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=22, size=15558622, heights=365574...365643, time=2015-07-16...2015-07-17) 2019-03-03T17:46:46Z Checking all blk files are present... 2019-03-03T17:46:46Z LoadBlockIndexDB(): Block files have previously been pruned 2019-03-03T17:46:46Z Wiping LevelDB in /home/ubuntu/.bitcoin/chainstate 2019-03-03T17:46:46Z Opening LevelDB in /home/ubuntu/.bitcoin/chainstate 2019-03-03T17:46:46Z Opened LevelDB successfully 2019-03-03T17:46:46Z Wrote new obfuscate key for /home/ubuntu/.bitcoin/chainstate: 56aab2d849f3053f 2019-03-03T17:46:46Z Using obfuscation key for /home/ubuntu/.bitcoin/chainstate: 56aab2d849f3053f 2019-03-03T17:46:46Z init message: Rewinding blocks... 2019-03-03T17:46:48Z block index 5207ms 2019-03-03T17:46:48Z init message: Loading wallet... 2019-03-03T17:46:48Z [default wallet] nFileVersion = 170100 2019-03-03T17:46:48Z [default wallet] Keys: 2001 plaintext, 0 encrypted, 2001 w/ metadata, 2001 total. Unknown wallet records: 1 2019-03-03T17:46:48Z [default wallet] Wallet completed loading in 39ms 2019-03-03T17:46:48Z [default wallet] setKeyPool.size() = 2000 2019-03-03T17:46:48Z [default wallet] mapWallet.size() = 0 2019-03-03T17:46:48Z [default wallet] mapAddressBook.size() = 0 2019-03-03T17:46:48Z Unsetting NODE_NETWORK on prune mode 2019-03-03T17:46:48Z init message: Pruning blockstore... 2019-03-03T17:46:48Z Imported mempool transactions from disk: 0 succeeded, 0 failed, 0 expired, 0 already there 2019-03-03T20:48:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 10856 seconds ago) 2019-03-03T20:58:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 11486 seconds ago) 2019-03-03T21:09:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 12116 seconds ago) 2019-03-03T21:19:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 12746 seconds ago) 2019-03-03T21:30:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 13376 seconds ago) 2019-03-03T21:40:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 14006 seconds ago) 2019-03-03T21:51:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 14636 seconds ago) 2019-03-03T22:01:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 15266 seconds ago) 2019-03-03T22:12:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 15896 seconds ago) Title: Re: bitcoin-cli error code -28 Post by: darosior on March 04, 2019, 07:25:09 PM -28 usually means your client (Bitcoin Core) is still starting/warming-up, but looks like the message says otherwise. Your first command throw error because you forget to add - though. It would be great if you could share your debug.log file, so we'd have easier time identifying the problem When i run cat debug.log i recived this. 2019-03-03T17:46:42Z Bitcoin Core version v0.17.1 (release build) 2019-03-03T17:46:42Z InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1 2019-03-03T17:46:42Z Assuming ancestors of block 0000000000000000002e63058c023a9a1de233554f28c7b21380b6c9003f36a8 have valid signatures. 2019-03-03T17:46:42Z Setting nMinimumChainWork=0000000000000000000000000000000000000000028822fef1c230963535a90d 2019-03-03T17:46:42Z Prune configured to target 600MiB on disk for block and undo files. 2019-03-03T17:46:42Z Using the 'sse4(1way),sse41(4way),avx2(8way)' SHA256 implementation 2019-03-03T17:46:42Z Using RdRand as an additional entropy source 2019-03-03T17:46:42Z Default data directory /home/ubuntu/.bitcoin 2019-03-03T17:46:42Z Using data directory /home/ubuntu/.bitcoin 2019-03-03T17:46:42Z Using config file /home/ubuntu/.bitcoin/bitcoin.conf 2019-03-03T17:46:42Z Using at most 12 automatic connections (1024 file descriptors available) 2019-03-03T17:46:42Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements 2019-03-03T17:46:42Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements 2019-03-03T17:46:42Z Using 0 threads for script verification 2019-03-03T17:46:42Z scheduler thread start 2019-03-03T17:46:42Z HTTP: creating work queue of depth 16 2019-03-03T17:46:42Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation. 2019-03-03T17:46:42Z HTTP: starting 4 worker threads 2019-03-03T17:46:42Z Using wallet directory /home/ubuntu/.bitcoin 2019-03-03T17:46:42Z init message: Verifying wallet(s)... 2019-03-03T17:46:43Z Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2019-03-03T17:46:43Z Using wallet wallet.dat 2019-03-03T17:46:43Z BerkeleyEnvironment::Open: LogDir=/home/ubuntu/.bitcoin/database ErrorFile=/home/ubuntu/.bitcoin/db.log 2019-03-03T17:46:43Z Cache configuration: 2019-03-03T17:46:43Z * Using 2.0MiB for block index database 2019-03-03T17:46:43Z * Using 8.0MiB for chain state database 2019-03-03T17:46:43Z * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space) 2019-03-03T17:46:43Z init message: Loading block index... 2019-03-03T17:46:43Z Opening LevelDB in /home/ubuntu/.bitcoin/blocks/index 2019-03-03T17:46:43Z Opened LevelDB successfully 2019-03-03T17:46:43Z Using obfuscation key for /home/ubuntu/.bitcoin/blocks/index: 0000000000000000 2019-03-03T17:46:46Z LoadBlockIndexDB: last block file = 302 2019-03-03T17:46:46Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=22, size=15558622, heights=365574...365643, time=2015-07-16...2015-07-17) 2019-03-03T17:46:46Z Checking all blk files are present... 2019-03-03T17:46:46Z LoadBlockIndexDB(): Block files have previously been pruned 2019-03-03T17:46:46Z Wiping LevelDB in /home/ubuntu/.bitcoin/chainstate 2019-03-03T17:46:46Z Opening LevelDB in /home/ubuntu/.bitcoin/chainstate 2019-03-03T17:46:46Z Opened LevelDB successfully 2019-03-03T17:46:46Z Wrote new obfuscate key for /home/ubuntu/.bitcoin/chainstate: 56aab2d849f3053f 2019-03-03T17:46:46Z Using obfuscation key for /home/ubuntu/.bitcoin/chainstate: 56aab2d849f3053f 2019-03-03T17:46:46Z init message: Rewinding blocks... 2019-03-03T17:46:48Z block index 5207ms 2019-03-03T17:46:48Z init message: Loading wallet... 2019-03-03T17:46:48Z [default wallet] nFileVersion = 170100 2019-03-03T17:46:48Z [default wallet] Keys: 2001 plaintext, 0 encrypted, 2001 w/ metadata, 2001 total. Unknown wallet records: 1 2019-03-03T17:46:48Z [default wallet] Wallet completed loading in 39ms 2019-03-03T17:46:48Z [default wallet] setKeyPool.size() = 2000 2019-03-03T17:46:48Z [default wallet] mapWallet.size() = 0 2019-03-03T17:46:48Z [default wallet] mapAddressBook.size() = 0 2019-03-03T17:46:48Z Unsetting NODE_NETWORK on prune mode 2019-03-03T17:46:48Z init message: Pruning blockstore... 2019-03-03T17:46:48Z Imported mempool transactions from disk: 0 succeeded, 0 failed, 0 expired, 0 already there 2019-03-03T20:48:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 10856 seconds ago) 2019-03-03T20:58:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 11486 seconds ago) 2019-03-03T21:09:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 12116 seconds ago) 2019-03-03T21:19:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 12746 seconds ago) 2019-03-03T21:30:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 13376 seconds ago) 2019-03-03T21:40:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 14006 seconds ago) 2019-03-03T21:51:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 14636 seconds ago) 2019-03-03T22:01:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 15266 seconds ago) 2019-03-03T22:12:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 15896 seconds ago) |