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
Is your feature request related to a problem? Please describe.
we are using filelog receiver to collect logs and file_storage extension to persist read states, we have a large number of collectors running and occasionally we saw collectors are crashing while opening the DB, not sure why and how it ran into this state, at the mean time, should we add recover to prevent collector from crashing because of this?
@newly12 I agree that we should have a way to recover from this.
I'm keen to reproduce this. Is it possible to share the corrupted DB file?
If it contains confidential data, then can you share some hints to reproduce this? I can give that a shot
The error I posted in description is for the compaction phase, I also find another example for opening DB, please check receiver_filelog_.tgz, it is sort of an empty and no sensitive data.
$ bbolt check receiver_filelog_
panic: freepages: failed to get all reachable pages (page 2: invalid type: freelist (stack: [2]))
goroutine 6 [running]:
go.etcd.io/bbolt.(*DB).freepages.func2()
/Users/xxx/go/pkg/mod/go.etcd.io/bbolt@v1.3.8/db.go:1202 +0x8c
created by go.etcd.io/bbolt.(*DB).freepages in goroutine 1
/Users/xxx/go/pkg/mod/go.etcd.io/bbolt@v1.3.8/db.go:1200 +0x13c
$ strings receiver_filelog_
default
Component(s)
extension/storage/filestorage
Is your feature request related to a problem? Please describe.
we are using
filelog
receiver to collect logs andfile_storage
extension to persist read states, we have a large number of collectors running and occasionally we saw collectors are crashing while opening the DB, not sure why and how it ran into this state, at the mean time, should we add recover to prevent collector from crashing because of this?(masked receiver name)
Describe the solution you'd like
recover on DB error
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: