After update to 2.1.2/2.1.3, Plausible is stuck in crash-loop with migrations error #4636
-
Past Issues Searched
Issue is a Bug Report
Using official Plausible Cloud hosting or self-hosting?Self-hosting Describe the bugAfter updating Plausible to the latest version (2.1.3), the application isn't starting up and is stuck in a crash loop:
Not sure if it is relevant, but this setup has been running for a while (at least a few years). This issue happened with 2.1.2 and 2.1.3. Rolling back to 2.1.1 worked. Expected behaviorPlausible should start up ScreenshotsNo response Environment- OS: Linux
- Platform: Podman
- Plausible: 2.1.2 and 2.1.3
- Clickhouse: `clickhouse/clickhouse-server:24.3.3.102-alpine` |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 2 replies
-
Thank you for the report! Seems similar to (now fixed) #4161 but in a different migration. Failing migration: https://github.com/plausible/analytics/blob/v2.1.3/priv/ingest_repo/migrations/20240709181437_populate_location_data.exs Failing step: https://github.com/plausible/analytics/blob/v2.1.3/lib/plausible/data_migration/locations_sync.ex#L117-L121 Failing query: https://github.com/plausible/analytics/blob/master/priv/data_migrations/LocationsSync/sql/update-location-data-dictionary.sql.eex |
Beta Was this translation helpful? Give feedback.
-
According to https://clickhouse.com/docs/en/engines/database-engines/atomic "Atomic" engine is used by default, and the error says that you use a different database engine.
This seems relevant. Maybe you started using ClickHouse and created |
Beta Was this translation helpful? Give feedback.
-
I'll move this to discussions since it's unlikely to be a problem with Plausible itself. |
Beta Was this translation helpful? Give feedback.
-
ClickHouse/ClickHouse#39933 is one way to resolve this issue. |
Beta Was this translation helpful? Give feedback.
ClickHouse/ClickHouse#39933 is one way to resolve this issue.