Update to version 6.11 failing: tc_actions is already a hypertable

Maarten Ureela day ago

Version 6.11 is not starting on my Docker swarm:

Running Changeset: changelog-6.11.0::changelog-6.11.0-timescale::author
extension "timescaledb" already exists, skipping
constraint "tc_actions_pkey" of relation "tc_actions" does not exist, skipping
UPDATE SUMMARY
Run:                          0
Previously run:              28
Filtered out:                 0
-------------------------------
Total change sets:           31
ERROR: Exception Details
ERROR: Exception Primary Class:  PSQLException
ERROR: Exception Primary Reason:  ERROR: table "tc_actions" is already a hypertable
ERROR: Exception Primary Source:  PostgreSQL 17.5 (Ubuntu 17.5-1.pgdg22.04+1)

I have now fixed my tag to 6.10 and that remains to work.

Any tips?

The problem is that you upgraded to 6.11.0 first, which had an issue. You should restore the database and upgrade directly to 6.11.1.

Maarten Ureela day ago

Oops.. no manual fix possible? I am running just the latest tag and it happened automatically.
I do not have a backup of the previous version...

If it's not possible to fix manually I will just remove and recreate the database, I am still evaluating / testing Traccar and devices.

You can fix it manually. You need to recreate the tc_actions as a normal table.

Maarten Ureela day ago

I tried but that did not help me. So I just destroyed the database, recreated an empty one, but using the latest docker tag I still get the same error.

Also explicitly using 6.11.1 as docker tag results in the same error.

So essentially I now get this error on a fresh install of 6.11.1.

I know for a fact that a clean TimescaleDB database works correctly with 6.11.1 because we already deployed quite of few servers with this version.

Maarten Ureela day ago

OK; I started it with a new seperate postgres container instead of using my existing cluster and it worked. So there is probably something left in the database that is not deleted. I'll figure it out.

Thanks!