segfault after unexpected server reboot #680
Labels
No Label
AdminAPI
Bug
Check AWS
CI
Correctness
Critical
Documentation
Ideas
Improvement
Low priority
Newcomer
Performance
S3 Compatibility
Testing
Usability
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#680
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi,
After an unexpected server reboot,
garage
failed to start with a segfault error.garage
version isSee included log file generated with
RUST_LOG=garage=trace garage -c ./disaster.toml server
.My config is a single garage node.
Running
mdb_stat -a -e -f db.lmdb
gives no error.Could it be a garage bug or a lmdb corruption?
If you need more info or trace, just ask for.
Thanks.
Laurent
segfault after server crashto segfault after unexpected server rebootDo you think you could launch Garage with gdb to obtain a stack trace at the time of the segfault ?
Closing for inactivity.