I recently upgrade my node to v2.1.0. Post upgrade i have been facing a frequent issue where my node stops syncing. Once i restart the node it starts syncing again but again after few hours it stops. The sync stop is usually accompanied by lots of logs including
Unable to determine hash of ancestor error <HASH>
Is this something others are facing as well? could this be due to the version upgrade to v2.1.0. Asking since i was not facing this issue before.
Steps to Reproduce
N/A
Expected Result
Node should keep syncing.
Actual Result
Nodes stops syncing every few hours.
Environment
rippled v2.1.0
Supporting Files
The logs were full of message as posted below.
Logs Snippet:
2024-Mar-19 10:44:39.696776379 UTC Validations:WRN Unable to determine hash of ancestor seq=46291183 from ledger hash=5B60B547A930A783E4AAFD21F307A6C62DDC76D1605EAD01E24FE954DECE530F seq=46291513 (available: 46291257-46291513)2024-Mar-19 10:44:40.697094804 UTC Validations:WRN Unable to determine hash of ancestor seq=46291183 from ledger hash=5B60B547A930A783E4AAFD21F307A6C62DDC76D1605EAD01E24FE954DECE530F seq=46291513 (available: 46291257-46291513)2024-Mar-19 10:44:41.697425165 UTC Validations:WRN Unable to determine hash of ancestor seq=46291183 from ledger hash=5B60B547A930A783E4AAFD21F307A6C62DDC76D1605EAD01E24FE954DECE530F seq=46291513 (available: 46291257-46291513)2024-Mar-19 10:44:42.697748156 UTC Validations:WRN Unable to determine hash of ancestor seq=46291183 from ledger hash=5B60B547A930A783E4AAFD21F307A6C62DDC76D1605EAD01E24FE954DECE530F seq=46291513 (available: 46291257-46291513)2024-Mar-19 10:44:42.697861117 UTC Validations:WRN Unable to determine hash of ancestor seq=46291183 from ledger hash=5B60B547A930A783E4AAFD21F307A6C62DDC76D1605EAD01E24FE954DECE530F seq=46291513 (available: 46291257-46291513)2024-Mar-19 10:44:42.699006972 UTC Validations:WRN Unable to determine hash of ancestor seq=46291183 from ledger hash=771DE130CCBE4E722DDBE36F631F4ACB30C24E0B1079E5BB89B7F0377DE85185 seq=46291514 (available: 46291258-46291514)2024-Mar-19 10:44:43.698212983 UTC Validations:WRN Unable to determine hash of ancestor seq=46291183 from ledger hash=771DE130CCBE4E722DDBE36F631F4ACB30C24E0B1079E5BB89B7F0377DE85185 seq=46291514 (available: 46291258-46291514)2024-Mar-19 10:44:44.698523917 UTC Validations:WRN Unable to determine hash of ancestor seq=46291183 from ledger hash=771DE130CCBE4E722DDBE36F631F4ACB30C24E0B1079E5BB89B7F0377DE85185 seq=46291514 (available: 46291258-46291514)2024-Mar-19 10:44:45.698849855 UTC Validations:WRN Unable to determine hash of ancestor seq=46291183 from ledger hash=771DE130CCBE4E722DDBE36F631F4ACB30C24E0B1079E5BB89B7F0377DE85185 seq=46291514 (available: 46291258-46291514)2024-Mar-19 10:44:46.699170688 UTC Validations:WRN Unable to determine hash of ancestor seq=46291183 from ledger hash=771DE130CCBE4E722DDBE36F631F4ACB30C24E0B1079E5BB89B7F0377DE85185 seq=46291514 (available: 46291258-46291514)2024-Mar-19 10:44:47.699477384 UTC Validations:WRN Unable to determine hash of ancestor seq=46291183 from ledger hash=771DE130CCBE4E722DDBE36F631F4ACB30C24E0B1079E5BB89B7F0377DE85185 seq=46291514 (available: 46291258-46291514)2024-Mar-19 10:44:48.699800168 UTC Validations:WRN Unable to determine hash of ancestor seq=46291183 from ledger hash=771DE130CCBE4E722DDBE36F631F4ACB30C24E0B1079E5BB89B7F0377DE85185 seq=46291514 (available: 46291258-46291514)2024-Mar-19 10:44:49.700115494 UTC Validations:WRN Unable to determine hash of ancestor seq=46291183 from ledger hash=771DE130CCBE4E722DDBE36F631F4ACB30C24E0B1079E5BB89B7F0377DE85185 seq=46291514 (available: 46291258-46291514)2024-Mar-19 10:44:50.700431542 UTC Validations:WRN Unable to determine hash of ancestor seq=46291183 from ledger hash=771DE130CCBE4E722DDBE36F631F4ACB30C24E0B1079E5BB89B7F0377DE85185 seq=46291514 (available: 46291258-46291514)2024-Mar-19 10:44:51.700725456 UTC Validations:WRN Unable to determine hash of ancestor seq=46291183 from ledger hash=771DE130CCBE4E722DDBE36F631F4ACB30C24E0B1079E5BB89B7F0377DE85185 seq=46291514 (available: 46291258-46291514)2024-Mar-19 10:44:52.701040664 UTC Validations:WRN Unable to determine hash of ancestor seq=46291183 from ledger hash=771DE130CCBE4E722DDBE36F631F4ACB30C24E0B1079E5BB89B7F0377DE85185 seq=46291514 (available: 46291258-46291514)2024-Mar-19 10:44:53.701312137 UTC Validations:WRN Unable to determine hash of ancestor seq=46291183 from ledger hash=771DE130CCBE4E722DDBE36F631F4ACB30C24E0B1079E5BB89B7F0377DE85185 seq=46291514 (available: 46291258-46291514)2024-Mar-19 10:44:54.701685030 UTC Validations:WRN Unable to determine hash of ancestor seq=46291183 from ledger hash=771DE130CCBE4E722DDBE36F631F4ACB30C24E0B1079E5BB89B7F0377DE85185 seq=46291514 (available: 46291258-46291514)2024-Mar-19 10:44:55.701997686 UTC Validations:WRN Unable to determine hash of ancestor seq=46291183 from ledger hash=771DE130CCBE4E722DDBE36F631F4ACB30C24E0B1079E5BB89B7F0377DE85185 seq=46291514 (available: 46291258-46291514)2024-Mar-19 10:44:56.702329199 UTC Validations:WRN Unable to determine hash of ancestor seq=46291183 from ledger hash=771DE130CCBE4E722DDBE36F631F4ACB30C24E0B1079E5BB89B7F0377DE85185 seq=46291514 (available: 46291258-46291514)2024-Mar-19 10:44:57.702611134 UTC Validations:WRN Unable to determine hash of ancestor seq=46291183 from ledger hash=771DE130CCBE4E722DDBE36F631F4ACB30C24E0B1079E5BB89B7F0377DE85185 seq=46291514 (available: 46291258-46291514)2024-Mar-19 10:44:58.702898362 UTC Validations:WRN Unable to determine hash of ancestor seq=46291183 from ledger hash=771DE130CCBE4E722DDBE36F631F4ACB30C24E0B1079E5BB89B7F0377DE85185 seq=46291514 (available: 46291258-46291514)2024-Mar-19 10:44:59.703216196 UTC Validations:WRN Unable to determine hash of ancestor seq=46291183 from ledger hash=771DE130CCBE4E722DDBE36F631F4ACB30C24E0B1079E5BB89B7F0377DE85185 seq=46291514 (available: 46291258-46291514)2024-Mar-19 10:45:00.703566994 UTC Validations:WRN Unable to determine hash of ancestor seq=46291183 from ledger hash=771DE130CCBE4E722DDBE36F631F4ACB30C24E0B1079E5BB89B7F0377DE85185 seq=46291514 (available: 46291258-46291514)2024-Mar-19 10:45:01.703928246 UTC Validations:WRN Unable to determine hash of ancestor seq=46291183 from ledger hash=771DE130CCBE4E722DDBE36F631F4ACB30C24E0B1079E5BB89B7F0377DE85185 seq=46291514 (available: 46291258-46291514)2024-Mar-19 10:45:02.704262193 UTC Validations:WRN Unable to determine hash of ancestor seq=46291183 from ledger hash=771DE130CCBE4E722DDBE36F631F4ACB30C24E0B1079E5BB89B7F0377DE85185 seq=46291514 (available: 46291258-46291514)2024-Mar-19 10:45:02.704404279 UTC Validations:WRN Unable to determine hash of ancestor seq=46291183 from ledger hash=771DE130CCBE4E722DDBE36F631F4ACB30C24E0B1079E5BB89B7F0377DE85185 seq=46291514 (available: 46291258-46291514)
Issue Description
I recently upgrade my node to v2.1.0. Post upgrade i have been facing a frequent issue where my node stops syncing. Once i restart the node it starts syncing again but again after few hours it stops. The sync stop is usually accompanied by lots of logs including
Unable to determine hash of ancestor error <HASH>
Is this something others are facing as well? could this be due to the version upgrade to v2.1.0. Asking since i was not facing this issue before.
Steps to Reproduce
N/A
Expected Result
Node should keep syncing.
Actual Result
Nodes stops syncing every few hours.
Environment
rippled v2.1.0
Supporting Files
The logs were full of message as posted below.
Logs Snippet: