Open RaghavSood opened 5 years ago
Right, the server doesn't add the one-off ledger to its available history, and that's annoying. It should be better.
For now, you may be able to work around the issue by using transaction_entry with the ledger and transaction hash rather than using tx. (See also #2598 to add that functionality to tx so you don't have to use the deprecated transaction_entry command.)
I've already tried that, but I've had mixed results. transaction_entry
worked for me once, but now when I run rippled transaction_entry 89584DA17D646BE894DC1C17BEACC78B055144A8CB677BCB61800A2E26F9664A 43459471
after ledger_request
says the ledger is available, I just get ledgerNotFound
responses. I've tried with multiple transactions, and I'm not sure what changed.
We should reconsider the decision to not save a ledger that is explicitly requested via ledger_request
in the database.
While we're at it, consider fixing #1873 as well.
rippled 1.1.1
I'm running a rippled instance with a limited history, and would like to query past transactions. I have the transaction ID and the ledger index for the ledger it belongs to.
Expected Behaviour
Actual Behaviour
The ledger_request succeeds, but attempting to retrieve the transaction still returns
txnNotFound
. I have also tried to runledger_cleaner
with the given ledger to attempt to fix any missing nodes, and to import the ledger immediately before the one my tx is in, since the docs say you need a previous state to replay the tx. I have also then run ledger_cleaner again.However, in all scenarios, I consistently get
txnNotFound
.After all this, according to server info, I have:
The desired ledger of
43459471
is outside this range, although it is my understanding thatledger_request
should fetch it.