Sometimes, after a service restart, my full history Ripple server shows an incorrect complete ledger range. Version: 2.2.0-b3

[PaulMoney]

Issue Description

When I restart my Rippled service and check the status with the server_info command, my full history node shows an incorrect complete ledger range. However, when I make a curl request to check if older ledgers persist on my node, the request outputs older ledger history results.

Steps to Reproduce

1. Restart Rippled service.

Expected Result

1. Backfill and show the correct complete ledger range.

Actual Result

1. There is a mismatch between the complete ledger range shown in the server_info command and the actual curl request output for older ledger history on that node.