Recent easy corruption of nodes on latest/nightly/testing tag for sync & bucket corruption log for fresh sync
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- docker, postgresql, shell, sqlite
- Domain
- databases, devops, infrastructure
Research direction
Start with the reported failures and the backtrace locations in /wd/src/ledger/LedgerManagerImpl.cpp:550 and /wd/src/main/ApplicationImpl.cpp:805, then compare behavior across the nightly, latest, and testing images. Use the PostgreSQL and SQLite corruption messages to establish a reproducible sync failure; done means identifying the cause and confirming that a fresh sync completes without database or bucket corruption.
Written by the indexing model from the issue text.
Description
What version are you using?
multiple of
stellar/quickstart:nightly
stellar/quickstart:latest
stellar/quickstart:testing
at the moment being "Id": "sha256:e7f05fac9ce971eccaabfd528297380c682f39f0d687c02bc7547d273a360145",
What did you do?
nodes broken , reworked multiple times with different tags
What did you expect to see?
working
What did you see instead?
always have postgres broken
2026-03-02T06:18:44.085 [default INFO] Assigning calculated value of 2 to FAILURE_SAFETY
current exception: std::runtime_error("Bucket directory is corrupt")
backtrace:
0: stellar::printCurrentBacktrace()
at /wd/src/util/Backtrace.cpp:27:22
1: stellar::printBacktraceAndAbort()
at /wd/src/main/main.cpp:140:5
2: <unknown>
3: <unknown>
4: __cxa_throw
5: loadLastKnownLedgerInternal
at /wd/src/ledger/LedgerManagerImpl.cpp:550:9
6: start
at /wd/src/main/ApplicationImpl.cpp:805:21
7: runApp
at /wd/src/main/ApplicationUtils.cpp:117:10
8: operator()
at /wd/src/main/CommandLine.cpp:1638:20
__invoke<(lambda at main/CommandLine.cpp:1576:9) &>
at /usr/lib/llvm-20/bin/../include/c++/v1/__type_traits/invoke.h:179:25
__call<(lambda at main/CommandLine.cpp:1576:9) &>
at /usr/lib/llvm-20/bin/../include/c++/v1/__type_traits/invoke.h:243:12
__invoke_r<int, (lambda at main/CommandLine.cpp:1576:9) &>
at /usr/lib/llvm-20/bin/../include/c++/v1/__type_traits/invoke.h:273:10
operator()
at /usr/lib/llvm-20/bin/../include/c++/v1/__functional/function.h:167:12
operator()
at /usr/lib/llvm-20/bin/../include/c++/v1/__functional/function.h:319:10
9: operator()
at /usr/lib/llvm-20/bin/../include/c++/v1/__functional/function.h:436:12
operator()
at /usr/lib/llvm-20/bin/../include/c++/v1/__functional/function.h:995:10
runWithHelp
at /wd/src/main/CommandLine.cpp:479:12
10: run
at /wd/src/main/CommandLine.cpp:1570:12
2026-03-02T06:14:18.407 [default INFO] Assigning calculated value of 2 to FAILURE_SAFETY
current exception: std::runtime_error("sqlite3_statement_backend::loadOne: database disk image is malformed")
2026-03-02 06:15:19 UTC [120668-1607] stellar@horizon ERROR: could not read block 31756 in file "base/16384/16401": read only 0 of 8192 bytes
2026-03-02 06:15:19 UTC [120668-1608] stellar@horizon STATEMENT: SELECT COALESCE(MAX(sequence), 0) FROM history_ledgers
even re-sync with diff image tag still seeing this
- Dominant language
- Shell
- Stars
- 222
- Forks
- 236
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 12
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stellar/quickstart
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
stellar/quickstart#932 · 16 comments · 2 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 58/100
stellar/quickstart#923 · 2 comments ·
-
feature request
Difficulty 5/5 Over a week Newbie friendliness 35/100
stellar/quickstart#907 · 1 comment ·
-
feature request
Difficulty 5/5 Over a week Newbie friendliness 35/100
stellar/quickstart#906 · 3 comments ·
-
feature request
Difficulty 3/5 1-2 days Newbie friendliness 48/100
stellar/quickstart#900 · 2 comments ·
All issues in stellar/quickstart
Similar issues
-
Update Vish to 1.1.5 Openpackage-update
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oSoWoSo/vOid_Community_repOsitory#144 · 1 comment ·
-
help wanted new command
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
tldr-pages/tldr#24151 ·
-
PacReq: Rune IDE Openpackage request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
pacstall/pacstall-programs#9402 ·
-
[BUG] ci: the first prefetch-images.sh call runs before shard.txt exists, so it is always a no-op Openbug github-actions
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
update-request
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
msys2/MINGW-packages#31768 ·