Events won't load in issues

[opiper]

Self-Hosted Version

25.9.0

CPU Architecture

x86_64

Docker Version

28.5.1

Docker Compose Version

2.40.0

Machine Specification

• My system meets the minimum system requirements of Sentry

Steps to Reproduce

1. Have a reported error
2. Open error details
3. Wait for event to never load

Expected Result

Expected to see details events page

Actual Result

Continually loading events page that results in a server error 500 response

XHRGET
http://10.10.10.207:9000/api/0/organizations/sentry/issues/21/events/recommended/?collapse=fullRelease
[HTTP/1.1 500 Internal Server Error 27557ms]

I can see this error in the nginx logs

nginx-1  | 2025/10/15 14:44:19 [error] 31#31: *286 upstream prematurely closed connection while reading response header from upstream, client: 10.10.10.125, server: , request: "GET /api/0/organizations/sentry/issues/21/events/recommended/?collapse=fullRelease HTTP/1.1", upstream: "http://172.20.0.25:9000/api/0/organizations/sentry/issues/21/events/recommended/?collapse=fullRelease", host: "10.10.10.207:9000", referrer: "http://10.10.10.207:9000/organizations/sentry/issues/21/?project=2&query=is%3Aunresolved%20issue.priority%3A%5Bhigh%2C%20medium%5D&referrer=issue-stream"

Here is an image of the unfound event:

One thing of note, I nuked the installation to fix another error, deleted all files, all docker images, all docker volumes, etc and yet settings and data remained? I got the welcome tutorial but my accounts, projects, teams, and errors all remained. Are these under another directory that I missed?

Event ID

No response

[spotler-stefan]

I experience the same issue in an existing instance upgraded to 25.10.0.

When requesting the details of an issue I see a lot of these in the logs in the seaweed container:

seaweedfs-1 | I1016 06:59:22.590124 filechunk_manifest.go:162 request_id:d1b8f524-8e4b-43b7-94af-08f59dd462a7 read http://127.0.0.1:8080/8,0eb96cc2fc9357 failed, err: http://127.0.0.1:8080/8,0eb96cc2fc9357?readDeleted=true: 404 Not Found: not found
seaweedfs-1 | E1016 06:59:22.590161 filer_server_handlers_read.go:269 request_id:d1b8f524-8e4b-43b7-94af-08f59dd462a7 failed to stream content /buckets/nodestore/nodestore/73ff9e22e235fbebde789933098cedbb: read chunk: http://127.0.0.1:8080/8,0eb96cc2fc9357?readDeleted=true: 404 Not Found: not found
seaweedfs-1 | E1016 06:59:22.590177 common.go:316 ProcessRangeRequest: read chunk: http://127.0.0.1:8080/8,0eb96cc2fc9357?readDeleted=true: 404 Not Found: not found

And also errors from the web container:

web-1 | 07:12:59 [ERROR] sentry_sdk.errors: Internal error in sentry_sdk
web-1 | 07:12:59 [INFO] sentry.access.api: api.access (method='GET' view='sentry.issues.endpoints.group_event_details.GroupEventDetailsEndpoint' response='500' user_id='18' is_app='False' is_frontend_request='True' organization_id='1' path='/api/0/organizations/<org-slug>/issues/48660/events/latest/' caller_ip='178.226.116.49' user_agent='Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Safari/537.36' rate_limited='False' request_duration_seconds='5.602529287338257' rate_limit_type='DNE')
web-1 | 07:12:59 [ERROR] django.request: Internal Server Error: /api/0/organizations/<org-slug>/issues/48660/events/latest/ (status_code=500 request=<WSGIRequest: GET '/api/0/organizations/<org-slug>/issues/48660/events/latest/?collapse=fullRelease&query=runtime%3A%22php%208.%2A%22'>)

[opiper]

I experience the same issue in an existing instance upgraded to 25.10.0.

When requesting the details of an issue I see a lot of these in the logs in the seaweed container:

seaweedfs-1 | I1016 06:59:22.590124 filechunk_manifest.go:162 request_id:d1b8f524-8e4b-43b7-94af-08f59dd462a7 read http://127.0.0.1:8080/8,0eb96cc2fc9357 failed, err: http://127.0.0.1:8080/8,0eb96cc2fc9357?readDeleted=true: 404 Not Found: not found
seaweedfs-1 | E1016 06:59:22.590161 filer_server_handlers_read.go:269 request_id:d1b8f524-8e4b-43b7-94af-08f59dd462a7 failed to stream content /buckets/nodestore/nodestore/73ff9e22e235fbebde789933098cedbb: read chunk: http://127.0.0.1:8080/8,0eb96cc2fc9357?readDeleted=true: 404 Not Found: not found
seaweedfs-1 | E1016 06:59:22.590177 common.go:316 ProcessRangeRequest: read chunk: http://127.0.0.1:8080/8,0eb96cc2fc9357?readDeleted=true: 404 Not Found: not found

And also errors from the web container:

web-1 | 07:12:59 [ERROR] sentry_sdk.errors: Internal error in sentry_sdk
web-1 | 07:12:59 [INFO] sentry.access.api: api.access (method='GET' view='sentry.issues.endpoints.group_event_details.GroupEventDetailsEndpoint' response='500' user_id='18' is_app='False' is_frontend_request='True' organization_id='1' path='/api/0/organizations/<org-slug>/issues/48660/events/latest/' caller_ip='178.226.116.49' user_agent='Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Safari/537.36' rate_limited='False' request_duration_seconds='5.602529287338257' rate_limit_type='DNE')
web-1 | 07:12:59 [ERROR] django.request: Internal Server Error: /api/0/organizations/<org-slug>/issues/48660/events/latest/ (status_code=500 request=<WSGIRequest: GET '/api/0/organizations/<org-slug>/issues/48660/events/latest/?collapse=fullRelease&query=runtime%3A%22php%208.%2A%22'>)

Same errors I get that I posted in my previous issue.

Seaweedfs:

seaweedfs-1  | E1016 07:42:27.484256 stream.go:107 request_id:ed78b97f-f128-4750-b30a-bd9b3e95e4f3operation LookupFileId 3,49d7d8b8fa failed, err: urls not found
seaweedfs-1  | E1016 07:42:27.484324 filer_server_handlers_read.go:262 request_id:ed78b97f-f128-4750-b30a-bd9b3e95e4f3 failed to prepare stream content /buckets/nodestore/nodestore/316f9c565ad8a580c8419d966a644084: operation LookupFileId 3,49d7d8b8fa failed, err: urls not found
seaweedfs-1  | E1016 07:42:27.484353 common.go:310 ProcessRangeRequest: operation LookupFileId 3,49d7d8b8fa failed, err: urls not found

Web:

web-1  | 07:42:27 [ERROR] sentry_sdk.errors: Internal error in sentry_sdk
web-1  | 07:42:27 [INFO] sentry.access.api: api.access (method='GET' view='sentry.issues.endpoints.group_event_details.GroupEventDetailsEndpoint' response='500' user_id='1' is_app='False' is_frontend_request='True' organization_id='1' path='/api/0/organizations/sentry/issues/21/events/recommended/' caller_ip='10.10.10.125' user_agent='Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:143.0) Gecko/20100101 Firefox/143.0' rate_limited='False' request_duration_seconds='25.647229433059692' rate_limit_type='DNE')
web-1  | 07:42:27 [ERROR] django.request: Internal Server Error: /api/0/organizations/sentry/issues/21/events/recommended/ (status_code=500 request=<WSGIRequest: GET '/api/0/organizations/sentry/issues/21/events/recommended/?collapse=fullRelease'>)

The web error is always preceeded by what was decided as unrelated.
#3998 (comment)

[longwave]

Possibly related to #3991 - if you were on 25.9.0 and seaweedfs was restarted you may have lost the event data.

[opiper]

Possibly related to #3991 - if you were on 25.9.0 and seaweedfs was restarted you may have lost the event data.

So, I had an issue come through yesterday with no event data (checked as soon as it was logged and previous errors from the application used to have event data). I then put some errors in this morning (that had event data) and just restarted the entire server but those event data has remained. Still on 25.9.0.

[PharaohTomb]

Possibly related to #3991 - if you were on 25.9.0 and seaweedfs was restarted you may have lost the event data.

This indeed is the case looks like.

Similar happened to my own Sentry instance, all past events are lost, and checking work instance that's still on 25.9.0 before updating I see that all the files are in /tmp as described.

[opiper]

Closing as the consensus is that it is #3991

[saibotk]

Ouh, @aldy505 can we maybe add this to the release notes as a warning for people that do not yet have restarted their container?

Though that would also mean to maybe provide some minimal guidance on where to find the files to possibly recover them (/tmp and copying them manually from the internal container storage...

Just got hit by this unexpectedly and wished i knew about this earlier.