You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was synchronizing the old version (v20.0.2) of Stellar-core until the day before yesterday, but because the protocol version was old, synchronization stopped at number 50457424.
Therefore, I made a new version (v20.2.0) and started synchronization on the same disk, but the block hash of number 50457424 seems to be different from what I expected, so I can't synchronize.
I have a question!
How can I synchronize again using the same disk in this situation?
I think I need to take the number 50457424 again and overwrite it in the database, but I don't know how.
I would be happy if you could let me know
stellar-core logs
$ stellar-core run --conf /opt/stellar/core/etc/stellar-core.cfg
2024-02-22T03:12:42.504 [default INFO] Config from /opt/stellar/core/etc/stellar-core.cfg
2024-02-22T03:12:42.505 [default INFO] Generated QUORUM_SET: {
"t": 5,
"v": [
{
"t": 2,
"v": [
"Blockdaemon_Validator_1",
"Blockdaemon_Validator_2",
"Blockdaemon_Validator_3"
]
},
{
"t": 2,
"v": [ "sdf_3", "sdf_1", "sdf_2" ]
},
{
"t": 2,
"v": [ "coinqvest_finland", "coinqvest_hong_kong", "coinqvest_germany" ]
},
{
"t": 2,
"v": [ "satoshipay_iowa", "satoshipay_singapore", "satoshipay_frankfurt" ]
},
{
"t": 2,
"v": [ "FT_SCV_1", "FT_SCV_3", "FT_SCV_2" ]
},
{
"t": 3,
"v": [
"lobstr_5_australia",
"lobstr_4_asia",
"lobstr_1_europe",
"lobstr_2_europe",
"lobstr_3_north_america"
]
},
{
"t": 2,
"v": [ "hercules", "lyra", "bootes" ]
}
]
}
2024-02-22T03:12:42.505 [default INFO] Assigning calculated value of 2 to FAILURE_SAFETY
2024-02-22T03:12:42.505 GA24L [default INFO] Starting stellar-core v20.2.0
2024-02-22T03:12:42.507 GA24L [Database INFO] Connecting to: postgresql://dbname=core host=localhost user=stellar password=********
2024-02-22T03:12:42.529 GA24L [SCP INFO] LocalNode::LocalNode@GA24L qSet: b4cccf
2024-02-22T03:12:42.531 GA24L [Database INFO] DB schema is in current version
2024-02-22T03:12:42.533 GA24L [default INFO] Listening on 0.0.0.0:11626 for HTTP requests
2024-02-22T03:12:42.533 GA24L [default INFO] Connection effective settings:
2024-02-22T03:12:42.533 GA24L [default INFO] TARGET_PEER_CONNECTIONS: 8
2024-02-22T03:12:42.533 GA24L [default INFO] MAX_ADDITIONAL_PEER_CONNECTIONS: 64
2024-02-22T03:12:42.533 GA24L [default INFO] MAX_PENDING_CONNECTIONS: 500
2024-02-22T03:12:42.533 GA24L [default INFO] MAX_OUTBOUND_PENDING_CONNECTIONS: 56
2024-02-22T03:12:42.533 GA24L [default INFO] MAX_INBOUND_PENDING_CONNECTIONS: 444
2024-02-22T03:12:42.533 GA24L [History INFO] Archive 'Blockdaemon_Validator_1' has 'get'command only, will not be written
2024-02-22T03:12:42.533 GA24L [History INFO] Archive 'Blockdaemon_Validator_2' has 'get'command only, will not be written
2024-02-22T03:12:42.533 GA24L [History INFO] Archive 'Blockdaemon_Validator_3' has 'get'command only, will not be written
2024-02-22T03:12:42.533 GA24L [History INFO] Archive 'FT_SCV_1' has 'get'command only, will not be written
2024-02-22T03:12:42.533 GA24L [History INFO] Archive 'FT_SCV_2' has 'get'command only, will not be written
2024-02-22T03:12:42.533 GA24L [History INFO] Archive 'FT_SCV_3' has 'get'command only, will not be written
2024-02-22T03:12:42.533 GA24L [History INFO] Archive 'bootes' has 'get'command only, will not be written
2024-02-22T03:12:42.533 GA24L [History INFO] Archive 'coinqvest_finland' has 'get'command only, will not be written
2024-02-22T03:12:42.533 GA24L [History INFO] Archive 'coinqvest_germany' has 'get'command only, will not be written
2024-02-22T03:12:42.533 GA24L [History INFO] Archive 'coinqvest_hong_kong' has 'get'command only, will not be written
2024-02-22T03:12:42.533 GA24L [History INFO] Archive 'hercules' has 'get'command only, will not be written
2024-02-22T03:12:42.533 GA24L [History INFO] Archive 'lobstr_1_europe' has 'get'command only, will not be written
2024-02-22T03:12:42.533 GA24L [History INFO] Archive 'lobstr_2_europe' has 'get'command only, will not be written
2024-02-22T03:12:42.533 GA24L [History INFO] Archive 'lobstr_3_north_america' has 'get'command only, will not be written
2024-02-22T03:12:42.533 GA24L [History INFO] Archive 'lobstr_4_asia' has 'get'command only, will not be written
2024-02-22T03:12:42.533 GA24L [History INFO] Archive 'lobstr_5_australia' has 'get'command only, will not be written
2024-02-22T03:12:42.533 GA24L [History INFO] Archive 'lyra' has 'get'command only, will not be written
2024-02-22T03:12:42.533 GA24L [History INFO] Archive 'satoshipay_frankfurt' has 'get'command only, will not be written
2024-02-22T03:12:42.533 GA24L [History INFO] Archive 'satoshipay_iowa' has 'get'command only, will not be written
2024-02-22T03:12:42.533 GA24L [History INFO] Archive 'satoshipay_singapore' has 'get'command only, will not be written
2024-02-22T03:12:42.533 GA24L [History INFO] Archive 'sdf_1' has 'get'command only, will not be written
2024-02-22T03:12:42.533 GA24L [History INFO] Archive 'sdf_2' has 'get'command only, will not be written
2024-02-22T03:12:42.533 GA24L [History INFO] Archive 'sdf_3' has 'get'command only, will not be written
2024-02-22T03:12:42.533 GA24L [History WARNING] No writable archives configured, history will not be written.
2024-02-22T03:12:42.534 GA24L [Ledger INFO] Last closed ledger (LCL) hash is 00bc2e385db22bf847308c068ab6e08bf04d06d3c315a5a1c8303d831bf0dd3b
2024-02-22T03:12:42.535 GA24L [Ledger INFO] Loaded LCL header from database: [seq=50457424, hash=00bc2e]
2024-02-22T03:12:42.536 GA24L [Ledger INFO] Starting up application
2024-02-22T03:12:42.536 GA24L [Ledger INFO] Last closed ledger (LCL) hash is 00bc2e385db22bf847308c068ab6e08bf04d06d3c315a5a1c8303d831bf0dd3b
2024-02-22T03:12:42.536 GA24L [Ledger INFO] Loaded LCL header from database: [seq=50457424, hash=00bc2e]
2024-02-22T03:12:42.537 GA24L [Ledger ERROR] 28 buckets are missing from bucket directory 'buckets'
current exception: std::runtime_error("Bucket directory is corrupt")
Cannot provide readable stack trace. Use ParseDump.py to translate stack.
stellar-core() [0x87652a]
stellar-core() [0x78588e]
/lib/x86_64-linux-gnu/libc++abi.so.1(+0x25973) [0x7f9adb0f5973]
/lib/x86_64-linux-gnu/libc++abi.so.1(+0x28786) [0x7f9adb0f8786]
/lib/x86_64-linux-gnu/libc++abi.so.1(+0x2870d) [0x7f9adb0f870d]
stellar-core() [0x63d60e]
stellar-core() [0x6bdac3]
stellar-core() [0x6c885c]
stellar-core() [0x72d609]
stellar-core() [0x6f3bee]
stellar-core() [0x716543]
stellar-core() [0x71e34e]
stellar-core() [0x7856ff]
/lib/x86_64-linux-gnu/libc.so.6(+0x29d90) [0x7f9adadc2d90]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80) [0x7f9adadc2e40]
stellar-core() [0x42ac9e]
Aborted (core dumped)
The text was updated successfully, but these errors were encountered:
Read before creating an issue
I was synchronizing the old version (v20.0.2) of Stellar-core until the day before yesterday, but because the protocol version was old, synchronization stopped at number 50457424.
Therefore, I made a new version (v20.2.0) and started synchronization on the same disk, but the block hash of number 50457424 seems to be different from what I expected, so I can't synchronize.
I have a question!
How can I synchronize again using the same disk in this situation?
I think I need to take the number 50457424 again and overwrite it in the database, but I don't know how.
I would be happy if you could let me know
stellar-core logs
The text was updated successfully, but these errors were encountered: