Corrupt chronicle logs after dev machine crash

I’m running a cb server in a docker container for development.

My machine brutally crashed and when I tried to start the container again, I had this error in the error.log file :

[chronicle:error,2025-02-07T12:18:49.275Z,ns_1@cb.local:chronicle_agent<0.252.0>:chronicle_storage:open_logs:210]Failed to read log “/opt/couchbase/var/lib/couchbase/config/chronicle/logs/721.log”: {corrupt_log,
{bad_entry,
48746}}
[chronicle:error,2025-02-07T12:18:49.275Z,ns_1@cb.local:chronicle_agent<0.252.0>:chronicle_storage:open_current_log:239]Failed to open log “/opt/couchbase/var/lib/couchbase/config/chronicle/logs/722.log”: {corrupt_log,
bad_header}

Is there a way to recover from this ?
It’s a dev container so I can just trash it and pop a new one but I’m curious.

After checking when chronicle is, I removed the corrupted log files.
Now there is no error but the server doesn’t start anymore (as I suspected).
I can share the debug logs if needed.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.