getrawtransaction fails/behaves differently on command line and rpc #3298

Hey,

what I am trying to do it pretty simple: poll for new, unconfirmed transactions and stick them into a database. My problem is that sometimes, I can't get the raw transaction using the getrawtransaction RPC call. This is the error:

{u'message': u'No information available about transaction', u'code': -5}

I am running bitcoind 0.8.5 with txindex=1 set, and I used reindex for rebulding the db long time ago. I also verified this on two different machines, one mainnet, one testnet.

This happens a few times a day. When it does, it fails continuously for a few minutes for one specific transaction. Some of these transactions have been created by myself, so no chance that they are orphaned. (or is a transaction that uses the input of an orphaned transaction orphaned itself?)

Even if they are orphaned, I do not understand why (sometimes) I cannot retrieve the transaction using the RPC call, while I can get the raw transaction from the command line. Shouldn't use this the same internal calls?

I cannot retrieve the transaction using the RPC call, while I can get the raw transaction from the command line

With command line you mean bitcoind / bitcoin-cli? Yes, that uses the RPC interface, and should give exactly the same result for the same command.

I meant the bitcoind command line. Should not give different results, but it does for me. Hence this report. :)

The only possible explanation for that would be that you're not sending exactly the same RPC command as the command-line client is. Or maybe some problem with your JSON RPC implementation.

Either that or some randomness/race condition is involved in the server, but that wouldn't result in a consistent behavior difference.

There is not enough information to troubleshoot this, also the report relates to an ancient version, so closing.