Ledgers are processing slowly

rippled may show log messages like the ones below, and appear to be stuck.

ManifestCache:WRN Manifest: Revoked;Pk: [REDACTED_PK];Seq: 4294967295;
LedgerConsensus:WRN normal consensus, but stalled
TxQ:WRN Ledger 3 has 0 transactions. Ledgers are processing slowly. Expected transactions is currently 32 and multiplier is 128000
NetworkOPs:WRN We are not running on the consensus ledger
LedgerConsensus:WRN Need consensus ledger [REDACTED_HASH]
LedgerConsensus:WRN View of consensus changed during establish mode=wrongLedger, [REDACTED_HASH] to [REDACTED_HASH], {"account_hash":"[REDACTED_HASH]","close_flags":0,"close_time":804152870,"close_time_human":"2025-Jun-25 07:47:50.000000000 UTC","close_time_iso":"2025-06-25T07:47:50Z","close_time_resolution":10,"closed":true,"ledger_hash":"[REDACTED_HASH]","ledger_index":3,"parent_close_time":804152850,"parent_hash":"[REDACTED_HASH]","total_coins":"100000000000000000","transaction_hash":"[REDACTED_HASH]"}
LedgerConsensus:WRN Need consensus ledger [REDACTED_HASH]
NetworkOPs:WRN We are not running on the consensus ledger
LedgerConsensus:WRN View of consensus changed during establish mode=wrongLedger, [REDACTED_HASH] to [REDACTED_HASH], {"account_hash":"[REDACTED_HASH]","close_flags":0,"close_time":804152890,"close_time_human":"2025-Jun-25 07:48:10.000000000 UTC","close_time_iso":"2025-06-25T07:48:10Z","close_time_resolution":10,"closed":true,"ledger_hash":"[REDACTED_HASH]","ledger_index":4,"parent_close_time":804152870,"parent_hash":"[REDACTED_HASH]","total_coins":"100000000000000000","transaction_hash":"[REDACTED_HASH]"}
LedgerConsensus:WRN Need consensus ledger [REDACTED_HASH]
NetworkOPs:WRN We are not running on the consensus ledger
LedgerConsensus:WRN View of consensus changed during establish mode=wrongLedger, [REDACTED_HASH] to [REDACTED_HASH], {"account_hash":"[REDACTED_HASH]","close_flags":0,"close_time":804152891,"close_time_human":"2025-Jun-25 07:48:11.000000000 UTC","close_time_iso":"2025-06-25T07:48:11Z","close_time_resolution":10,"closed":true,"ledger_hash":"[REDACTED_HASH]","ledger_index":5,"parent_close_time":804152890,"parent_hash":"[REDACTED_HASH]","total_coins":"100000000000000000","transaction_hash":"[REDACTED_HASH]"}
LedgerConsensus:WRN Need consensus ledger [REDACTED_HASH]
NetworkOPs:WRN We are not running on the consensus ledger
NetworkOPs:WRN We are not running on the consensus ledger
LedgerConsensus:WRN View of consensus changed during establish mode=wrongLedger, [REDACTED_HASH] to [REDACTED_HASH], {"account_hash":"[REDACTED_HASH]","close_flags":0,"close_time":804152952,"close_time_human":"2025-Jun-25 07:49:12.000000000 UTC","close_time_iso":"2025-06-25T07:49:12Z","close_time_resolution":10,"closed":true,"ledger_hash":"[REDACTED_HASH]","ledger_index":16,"parent_close_time":804152951,"parent_hash":"[REDACTED_HASH]","total_coins":"100000000000000000","transaction_hash":"[REDACTED_HASH]"}
LedgerConsensus:WRN Need consensus ledger [REDACTED_HASH]
NetworkOPs:WRN We are not running on the consensus ledger
LedgerConsensus:WRN View of consensus changed during establish mode=wrongLedger, [REDACTED_HASH] to [REDACTED_HASH], {"account_hash":"[REDACTED_HASH]","close_flags":0,"close_time":804152960,"close_time_human":"2025-Jun-25 07:49:20.000000000 UTC","close_time_iso":"2025-06-25T07:49:20Z","close_time_resolution":10,"closed":true,"ledger_hash":"[REDACTED_HASH]","ledger_index":17,"parent_close_time":804152952,"parent_hash":"[REDACTED_HASH]","total_coins":"100000000000000000","transaction_hash":"[REDACTED_HASH]"}
LedgerConsensus:WRN Need consensus ledger [REDACTED_HASH]
NetworkOPs:WRN [REDACTED_HASH]: cached bad!
NetworkOPs:WRN [REDACTED_HASH]: cached bad!
NetworkOPs:WRN [REDACTED_HASH]: cached bad!
NetworkOPs:WRN [REDACTED_HASH]: cached bad!

The issue may have been exacerbated by having a mix of nodes with this patch (introduced in 2.5.0, therefore not present in 2.4.0): https://github.com/XRPLF/rippled/pull/4985

It has mostly gone away now that most of the network has upgraded to version 2.5.0 or higher.

Note, it's not necessarily unusual for a node to take 2 hours to sync with the network. However, faster hardware can help with this. In particular, avoid using EBS, since it is slow. Instead, use NVMe.

https://xrpl.org/docs/infrastructure/installation/system-requirements#recommended-specifications