seaweedfs readDeleted=true: 500 Internal Server Error

[teankie]

After upgrtade sentry to 25.0.9 we see after restarts of sentry some 500 errors in de GUI based on events.
Looking at the logs of seaweedfs we see the followin errors:

E1007 14:00:06.859328 common.go:316 ProcessRangeRequest: read chunk: http://127.0.0.1:8080/13,0e0e2b673b0be2?readDeleted=true: 500 Internal Server Error
E1007 14:00:07.050929 needle_read.go:46 /tmp/nodestore_13.dat read 0 dataSize 176 offset 142629064 fileSize 8: EOF
E1007 14:00:07.052286 filer_server_handlers_read.go:269 request_id:07531fd1-59fd-430f-aaf6-36662e54de9c failed to stream content /buckets/nodestore/nodestore/e-g-f:439add904280a726b0f58f94b6e645d8: read chunk: http://127.0.0.1:8080/13,0e0e2b673b0be2?readDeleted=true: 500 Internal Server Error
E1007 14:00:07.052305 common.go:316 ProcessRangeRequest: read chunk: http://127.0.0.1:8080/13,0e0e2b673b0be2?readDeleted=true: 500 Internal Server Error

Can someone tell us why is there a corruption on seaweedfs nodestores?

[linear]

ENG-5671

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[mjonasz]

same issue, solved by: getsentry/self-hosted#3991

until next release, you can patch docker-compose.yml or add docker-compose.override.yml with corrected command for seaweedfs