taskbroker crashing: no more data ingested

[Mika56]

Self-Hosted Version

25.9.0

CPU Architecture

x86_64

Docker Version

28.0.4

Docker Compose Version

2.34.0

Machine Specification

• My system meets the minimum system requirements of Sentry

Steps to Reproduce

Updated last week to 25.9.0. Worked fine for a few days, including after daily backups. Stopped working last night after a backup (which stops Sentry and start it again).

Expected Result

N/A

Actual Result

Taskbroker crashes almost immediately, without any relevant logs:

taskbroker-1  | taskbroker starting
taskbroker-1  | version: 66748f21df47b6dd36d8cf13bbfba608874b0f06
taskbroker-1  | 2025-09-25T15:45:10.255763Z  INFO taskbroker: Running full vacuum on database
taskbroker-1  | 2025-09-25T15:45:10.263871Z  INFO taskbroker: Full vacuum completed.
taskbroker-1  | 2025-09-25T15:45:10.264030Z  INFO taskbroker: GRPC server listening on 0.0.0.0:50051
taskbroker-1  | taskbroker starting
taskbroker-1  | version: 66748f21df47b6dd36d8cf13bbfba608874b0f06
taskbroker-1  | 2025-09-25T15:46:12.738914Z  INFO taskbroker: Running full vacuum on database
taskbroker-1  | 2025-09-25T15:46:12.742990Z  INFO taskbroker: Full vacuum completed.
taskbroker-1  | 2025-09-25T15:46:12.743935Z  INFO taskbroker: GRPC server listening on 0.0.0.0:50051
taskbroker-1  | taskbroker starting
taskbroker-1  | version: 66748f21df47b6dd36d8cf13bbfba608874b0f06
taskbroker-1  | 2025-09-25T15:47:15.271108Z  INFO taskbroker: Running full vacuum on database
taskbroker-1  | 2025-09-25T15:47:15.275580Z  INFO taskbroker: Full vacuum completed.
taskbroker-1  | 2025-09-25T15:47:15.275719Z  INFO taskbroker: GRPC server listening on 0.0.0.0:50051
taskbroker-1  | taskbroker starting
taskbroker-1  | version: 66748f21df47b6dd36d8cf13bbfba608874b0f06
taskbroker-1  | 2025-09-25T15:48:17.862434Z  INFO taskbroker: Running full vacuum on database
taskbroker-1  | 2025-09-25T15:48:17.867148Z  INFO taskbroker: Full vacuum completed.
taskbroker-1  | 2025-09-25T15:48:17.867402Z  INFO taskbroker: GRPC server listening on 0.0.0.0:50051

SDK are sending events and receive a message id, but no new data is available on Sentry

Event ID

No response

[Mika56]

Looks like taskbroker-activations.sqlite got corrupted. I renamed it to .bak (also .sqlite-shm and .sqlite-wal files) and its ingesting properly now. Not sure how the database got corrupted. Maybe when the backup process ran docker composer down, taskbroker took too long and was force killed?

Anyway, I think taskbroker should at least crash with an error message :)

[aldy505]

@InterstellarStella Hi, can you help transfer this to taskbroker repo and change the title to "Taskbroker should crash with an error message"? Thank you!