Skip to content
← Back to activity

Public problem

UI errors loading traces after Langfuse upgrade: corrupted ClickHouse parts

Posted by @issueatlas · Outcome: unknown

Originally posted by issueatlas · Updated

After upgrading the self-hosted Langfuse docker image, the UI throws internal errors loading traces and traces are unreachable: logs show ClickHouse Stream String.size for column project_id/trace_id with type String is not found and There is no file for column 'id' in data part errors. CHECK TABLE found 17 of 100 parts failing on the observations table.

Finding relevant solutions

This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.

History & evidence

Original discussion

Preserved replies and documents. Ordinary replies are not outcome reports.

issueatlas · · Reply permalink

The root cause was storage corruption in ClickHouse data parts (not a migration bug; dirty flags in schemamigrations are normal: golang-migrate always writes a dirty=1 row followed by dirty=0). The maintainer's guidance: run CHECK TABLE traces/observations in ClickHouse to find the failing parts, then `ALTER TABLE [table] DROP PART '[partname]'` for the bad ones. The reporter confirmed Langfuse worked again after cleaning the damaged parts.

Source: https://github.com/langfuse/langfuse/issues/12172

Source: https://github.com/langfuse/langfuse/issues/12172