starred/planka
1
0
Fork 0
mirror of https://github.com/plankanban/planka.git synced 2026-07-16 05:53:57 +03:00
Code Issues 396 Packages Projects Releases 21 Wiki Activity

Unable to restore from backup (column "stopwatch" doesn't exist) #297

New Issue
Closed
opened 2026-02-04 18:26:15 +03:00 by OVERLORD · 2 comments
OVERLORD commented 2026-02-04 18:26:15 +03:00
Owner
Copy Link

Originally created by @james-smith-za on GitHub (Mar 8, 2023).

Hi there! Great project, have loved using it for the last few days.

Tried to migrate from running on my desktop to a more permanent home on a VPS. I did this by doing a backup / restore.

Everything seems to be running, I can log in and see my boards etc. but when I open a project / board, then it gets stuck with a spinning circle where the lists / cards should be.

image

If I do docker logs planka_planka_1, then I get this:

2023-03-08 07:42:40 [E] Sending 500 ("Server Error") response: 
 Unexpected error from database adapter: column "stopwatch" does not exist

I've reached the limits of my knowledge now. How would one go about debugging this?

Originally created by @james-smith-za on GitHub (Mar 8, 2023). Hi there! Great project, have loved using it for the last few days. Tried to migrate from running on my desktop to a more permanent home on a VPS. I did this by doing a backup / restore. Everything seems to be running, I can log in and see my boards etc. but when I open a project / board, then it gets stuck with a spinning circle where the lists / cards should be. ![image](https://user-images.githubusercontent.com/10864691/223652345-8728066d-cc73-43a0-9edb-04ad007176df.png) If I do `docker logs planka_planka_1`, then I get this: ``` 2023-03-08 07:42:40 [E] Sending 500 ("Server Error") response: Unexpected error from database adapter: column "stopwatch" does not exist ``` I've reached the limits of my knowledge now. How would one go about debugging this?
OVERLORD commented 2026-02-04 18:26:26 +03:00
Author
Owner
Copy Link

@meltyshev commented on GitHub (Mar 8, 2023):

Hi! Hmm, I think I figured out what the problem might be. A newer version of Planka was installed on the new server, where there was a small change in the database, but the data in the backup didn't have these changes. But when Planka starts up, it should migrate the database automatically...

Please try to run this command:
docker exec --user postgres -t planka-postgres-1 psql -d planka -c "SELECT * FROM migration"

At the bottom there should be a line 20230227170557_rename_timer_to_stopwatch.js.

If it's there, delete it:
docker exec --user postgres -t planka-postgres-1 psql -d planka -c "DELETE FROM migration WHERE name = '20230227170557_rename_timer_to_stopwatch.js'"

Then start the migration again (even if that line wasn't there):
docker exec -t planka-planka-1 npm run db:migrate

Then restart the container.

Note: do not forget to replace the name of the container in the commands.

@meltyshev commented on GitHub (Mar 8, 2023): Hi! Hmm, I think I figured out what the problem might be. A newer version of Planka was installed on the new server, where there was a small change in the database, but the data in the backup didn't have these changes. But when Planka starts up, it should migrate the database automatically... Please try to run this command: `docker exec --user postgres -t planka-postgres-1 psql -d planka -c "SELECT * FROM migration"` At the bottom there should be a line `20230227170557_rename_timer_to_stopwatch.js`. If it's there, delete it: `docker exec --user postgres -t planka-postgres-1 psql -d planka -c "DELETE FROM migration WHERE name = '20230227170557_rename_timer_to_stopwatch.js'"` Then start the migration again (even if that line wasn't there): `docker exec -t planka-planka-1 npm run db:migrate` Then restart the container. _Note: do not forget to replace the name of the container in the commands._
OVERLORD commented 2026-02-04 18:26:33 +03:00
Author
Owner
Copy Link

@james-smith-za commented on GitHub (Mar 8, 2023):

Thanks @meltyshev, working perfectly now! My sincerest gratitude.
I did wonder if there may have been a version update causing issues, but I wasn't quite sure how to check.

The line 20230227170557_rename_timer_to_stopwatch.js wasn't in the output, but the migration that you suggested did the trick.

@james-smith-za commented on GitHub (Mar 8, 2023): Thanks @meltyshev, working perfectly now! My sincerest gratitude. I did wonder if there may have been a version update causing issues, but I wasn't quite sure how to check. The line `20230227170557_rename_timer_to_stopwatch.js` wasn't in the output, but the migration that you suggested did the trick.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
documentation
documentation
duplicate
enhancement
good first issue
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/planka#297
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?