Bitcoind Internal Server Error #8211

I'm trying to call bitcoind sendtoaddress with params :

18et8yw71yfxsQz99c5sHHEgYtR32kkfw 0.15161962

and there is an exception "(500) Internal Server Error."

The wallet has sufficient funds ~30 bitcoins The same call to different address works good The same call with different amount (0.001bitcoin) works good It started to fail with internal errors since 0.12.11 bitcoin core version and qt-5.5.0 I don't understand why only this call failed ?

I set the fee to 0.0002 before calling sendtoaddress , the problem is that the call sendtoaddress one time works and sometimes return internal error, Is there some kind of log ?

Is there some kind of log

Anything in debug.log? You can try running bitcoind/-qt with -debug=1 to get full debug output.

No problem here (I obviously tried with a wallet without funds):

$ src/bitcoin-cli -datadir=/store/tmp/testbtc sendtoaddress 18et8yw71yfxsQz99c5sHHEgYtR32kkfw 0.15161962
error code: -6
error message:
Insufficient funds

Note that bitcoind will never return an internal server error (grep for HTTP_INTERNAL_SERVER_ERROR) in RPC usage.

It could be a client-side timeout. Try running bitcoin-cli with -rpcclienttimeout=1000.

Can I set the debug to only log info for sending transactions ? I want it to log only when I invoke method "sendtoaddress"

Not using command line options. You could temporarily add extra logging in wallet/rpcwallet.cpp in the implementation of sendtoadress.

Output debugging information (default: 0, supplying <category> is optional). If <category> is not supplied or if <category> = 1, output all debugging information.<category> can be: addrman, alert, bench, coindb, db, lock, rand, rpc, selectcoins, mempool, mempoolrej, net, proxy, prune, http, libevent, tor, zmq, qt. should I use -debug=rpc ?

Yes you can use debug=rpc (what I suggested, debug=1 enables all categories including rpc) which does some logging per call. I doubt it will help you much with debugging this specific issue though.

I found that this addresses causing the problem "internal server error" 18et8yw71yfxsQz99c5sHHEgYtR32kkfw 1L9WbTM5XHYAwtpzcSV1gRuSK41aEu2MQg 1BPB3ZG9NJVJNeaAZnJ4itoUBVNEkGMS5c 13s5QivQPeeABXQUYhUxrucULbR4KaBLm6 16RE1uKkg1wH2a4q1r2DvWMg2p4CSXiJqr 191nZhtTosUBSDU6Qjr3A83ajeFV3Qc91g 1JeXoQ6bsHTW465aLBhFj2azRcim1ckYav 14PkPcCSY7iuFo4D21z57EAKygFfbk1QDF 1Ewwe4XuXn9XPCPQUFns9YsVBMFviahx8D 1LoB79zHbhbqMTcEwxWV7FDfUEXUYr6syG 19Yc4Ht9MdxEQ2rTN3hqGZXpDSdJq14xYJ 35JJ6dfGKAaW15SP2RLZbJUa9gZTPZBABq 1FjQm9zwEo5u8pMAbrwfRLMQWYkQUQGYV1 Does it help ?

@macdasi Any information in the relevant parts of debug.log (You may also use -printtoconsole)

@MarcoFalke , what should I look for ? the error happens on sendtoaddress call