What behavior did you expect?
- i call:
curl -u rpc:rpc -X POST -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","id":"1","method":"estimatesmartfee","params":[3]}' http://127.0.0.1:18332 - i get
{"result":{"errors":["Insufficient data or no feerate found"],"blocks":0},"error":null,"id":"1"}
How reliably can you reproduce the issue, what are the steps to do so?
- i wiped ALL bitcoin data i had except wallet on dev
- i ran a node with this config:
server=1
rpcuser=rpc
rpcpassword=rpc
onlynet=ipv4
testnet=1
rpcbind=127.0.0.1:18332
walletdir=/path/to/my/testnet/wallet/folder/
txindex=1
- data fully synced:
~/.bitcoin/testnet3# du -h
4.0K ./wallets
875M ./chainstate
2.4G ./indexes/txindex
2.4G ./indexes
291M ./blocks/index
24G ./blocks
27G .
as files[] i have
banlist.dat
bitcoind.pid
debug.log
.lock
peers.dat
What version of Bitcoin Core are you using, where did you get it (website, self-compiled, etc)?
bitcoin 0.18.0 (official website, already compiled, sha256 checked)
What type of machine are you observing the error on (OS/CPU and disk type)?
- dev server
Linux 4.9.0-9-amd64 [#1](/bitcoin-bitcoin/1/) SMP Debian 4.9.168-1 (2019-04-12) x86_64 GNU/Linux - 1270v3
- 2x 16ram
- 2x NVMe
This is normally the contents of a debug.log or config.log file. Raw text or a link to a pastebin type site are preferred.
- started at
2019-06-05T13:32:42Z grep estimate debug.logreturn nothinggrep mempool -A 3 -B 3 debug.logreturn:
2019-06-05T13:32:48Z * Using 2.0 MiB for block index database 2019-06-05T13:32:48Z * Using 56.0 MiB for transaction index database 2019-06-05T13:32:48Z * Using 8.0 MiB for chain state database 2019-06-05T13:32:48Z * Using 384.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space) 2019-06-05T13:32:48Z init message: Loading block index... 2019-06-05T13:32:48Z Opening LevelDB in /root/.bitcoin/testnet3/blocks/index 2019-06-05T13:32:48Z Opened LevelDB successfully
AND
2019-06-05T13:32:59Z [default wallet] mapWallet.size() = 282 2019-06-05T13:32:59Z [default wallet] mapAddressBook.size() = 725147 2019-06-05T13:32:59Z UpdateTip: new best=000000000933ea01ad0ee984209779baaec3ced90fa3f408719526f8d77f4943 height=0 version=0x00000001 log2_work=32.000022 tx=1 date='2011-02-02T23:16:42Z' progress=0.000000 cache=0.0MiB(0txo) 2019-06-05T13:32:59Z Failed to open mempool file from disk. Continuing anyway. 2019-06-05T13:32:59Z mapBlockIndex.size() = 1 2019-06-05T13:32:59Z nBestHeight = 0 2019-06-05T13:32:59Z torcontrol thread start
While estimaterawfee works:
curl -u rpc:rpc -X POST -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","id":"1","method":"estimaterawfee","params":[3]}' http://127.0.0.1:18332{"result":{"short":{"feerate":0.00001000,"decay":0.962,"scale":1,"pass":{"startrange":0,"endrange":1000,"withintarget":210.67,"totalconfirmed":210.67,"inmempool":0,"leftmempool":0}},"medium":{"feerate":0.00001000,"decay":0.9952,"scale":2,"pass":{"startrange":0,"endrange":1000,"withintarget":211.83,"totalconfirmed":211.83,"inmempool":0,"leftmempool":0}},"long":{"feerate":0.00001000,"decay":0.99931,"scale":24,"pass":{"startrange":0,"endrange":1e+99,"withintarget":300.95,"totalconfirmed":300.95,"inmempool":0,"leftmempool":0}}},"error":null,"id":"1"}
While estimaterawfee is WARNING: This interface is unstable and may disappear or change!, so i can't use it on dev or prod.
Running time is: ~1h 10min