Major issue updating to v2.5.0 about runtipi HOT 17 CLOSED

It means please look into the file state/settings.json for a potential storage path value which is set to runtipi/app-data which is wrong

FYI the documentation lists runtipi/app-data as the default value for storagePath.

I found this issue when looking for a reason why the default config per the documentation differed from my own. I'm guessing runtipi/app-data was the default at some point in time but that's no longer the case? It would explain the issues @anantone was having.

from runtipi.

This is from error.log.history

`worker: 2024-01-18T10:16:01.049Z - ^[[31merror^[[39m > Error: connect ECONNREFUSED 172.23.0.2:5432

worker: 2024-01-18T10:20:44.494Z - ^[[31merror^[[39m > Error: connect ECONNREFUSED 172.23.0.12:5432

worker: 2024-01-18T10:24:53.881Z - ^[[31merror^[[39m > Error: connect EHOSTUNREACH 172.23.0.4:5432

worker: 2024-01-18T10:31:27.289Z - ^[[31merror^[[39m > Error: connect ECONNREFUSED 172.23.0.11:5432
`

I was running tailscale in runtipi and did not turn it off before updating... Could that be my sin?

from runtipi.

This is app.log

`cli: 2024-01-18T15:13:11.455Z - ^[[32minfo^[[39m > Logs flushed

cli: 2024-01-18T15:13:11.475Z - ^[[32minfo^[[39m > Copying system files...

cli: 2024-01-18T15:13:11.475Z - ^[[32minfo^[[39m > Copying file docker-compose.yml

cli: 2024-01-18T15:13:11.477Z - ^[[32minfo^[[39m > Copying file VERSION

cli: 2024-01-18T15:13:11.479Z - ^[[32minfo^[[39m > Generating system env file...

cli: 2024-01-18T15:13:11.483Z - ^[[32minfo^[[39m > Reloading env variables...

cli: 2024-01-18T15:13:11.484Z - ^[[32minfo^[[39m > Pulling new images...

cli: 2024-01-18T15:13:11.563Z - ^[[32minfo^[[39m > Starting containers...
`

from runtipi.

If I try to manually start an app with the cli, there is error.log

cli: 2024-01-18T16:33:41.707Z - error > uncaughtException: [ { "code": "invalid_type", "expected": "string", "received": "undefined", "path": [ "APPS_REPO_ID" ], "message": "Required" }, { "code": "invalid_type", "expected": "string", "received": "undefined", "path": [ "POSTGRES_USERNAME" ], "message": "Required" }, { "code": "invalid_type", "expected": "string", "received": "undefined", "path": [ "POSTGRES_DBNAME" ], "message": "Required" } ] ZodError: [ { "code": "invalid_type", "expected": "string", "received": "undefined", "path": [ "APPS_REPO_ID" ], "message": "Required" }, { "code": "invalid_type", "expected": "string", "received": "undefined", "path": [ "POSTGRES_USERNAME" ], "message": "Required" }, { "code": "invalid_type", "expected": "string", "received": "undefined", "path": [ "POSTGRES_DBNAME" ], "message": "Required" } ] at get error [as error] (/snapshot/runtipi/packages/cli/dist/index.js:3635:8435) at gn.parse (/snapshot/runtipi/packages/cli/dist/index.js:3635:10520) at jf (/snapshot/runtipi/packages/cli/dist/index.js:3637:2817) at zo.getQueue (/snapshot/runtipi/packages/cli/dist/index.js:3647:747) at zo.startApp (/snapshot/runtipi/packages/cli/dist/index.js:3647:1617) at t.<anonymous> (/snapshot/runtipi/packages/cli/dist/index.js:3661:145) at t.r [as _actionHandler] (/snapshot/runtipi/packages/cli/dist/index.js:13:497) at /snapshot/runtipi/packages/cli/dist/index.js:16:2971 at t._chainOrCall (/snapshot/runtipi/packages/cli/dist/index.js:16:1610) at t._parseCommand (/snapshot/runtipi/packages/cli/dist/index.js:16:2947)

from runtipi.

Hello, from which version did you try to update?

Please do the following steps:

1. Navigate to the runtipi directory
2. Run sudo ./runtipi-cli start
3. Post the logs as well as the result of docker ps

from runtipi.

Hi, I believe from the previous version, was keeping up to date.

➜ runtipi ./runtipi-cli start
Welcome to Tipi CLI ✨
✓ User allowed to run docker commands
✓ System files copied
✓ System env file generated
✓ Images pulled
✓ Containers started

╔════════════════════════ Tipi successfully started 🎉 ════════════════════════╗
║ ║
║ Visit: http://5.250.177.249:80 to access the dashboard ║
║ ║
║ Find documentation and guides at: https://runtipi.io ║
║ ║
║ Tipi is entirely written in TypeScript and we are looking for ║
║ contributors! ║
║

app.log

cli: 2024-01-18T20:47:36.560Z - ^[[32minfo^[[39m > Logs flushed cli: 2024-01-18T20:47:36.582Z - ^[[32minfo^[[39m > Copying system files... cli: 2024-01-18T20:47:36.582Z - ^[[32minfo^[[39m > Copying file docker-compose.yml cli: 2024-01-18T20:47:36.584Z - ^[[32minfo^[[39m > Copying file VERSION cli: 2024-01-18T20:47:36.585Z - ^[[32minfo^[[39m > Generating system env file... cli: 2024-01-18T20:47:36.589Z - ^[[32minfo^[[39m > Reloading env variables... cli: 2024-01-18T20:47:36.590Z - ^[[32minfo^[[39m > Pulling new images... cli: 2024-01-18T20:47:36.673Z - ^[[32minfo^[[39m > Starting containers...

error.log is empty

docker ps is empty

from runtipi.

I think you didn't run the start command with sudo from what I see

from runtipi.

I am root and don't have sudo installed. Same as before, with previous versions of runtipi.

from runtipi.

Please run this command manually, copy and paste exactly into the runtipi folder

docker compose --env-file ./.env up --detach --remove-orphans --build

You may not have the docker compose plugin. If it's the case please follow the instructions here

from runtipi.

Thanks. The command returns:
service "tipi-worker" refers to undefined volume runtipi/app-data: invalid compose project

I have docker compose v2.21.0

from runtipi.

You probably have a wrong custom storagePath configured in your settings.json

from runtipi.

from runtipi.

It means please look into the file state/settings.json for a potential storage path value which is set to runtipi/app-data which is wrong

from runtipi.

Thanks. Yes, that value is indeed runtipi/app-data

Not that I have changed it, not knowing about it...

from runtipi.

Good, so this was our issue! Does it work now? You probably changed it in the settings tab of your Dashboard by mistake. You can remove this value if you don't have a custom storage path

from runtipi.

Aaaah... Yes, I had changed it from the Dashboard to a custom path, then wanted to change it back to default, and actually typed in the default... Cool. Small mistake, large consequences. Thank you for your help. All working now!

from runtipi.

Aaaah... Yes, I had changed it from the Dashboard to a custom path, then wanted to change it back to default, and actually typed in the default... Cool. Small mistake, large consequences. Thank you for your help. All working now!

Cool glad you managed to make it run again! Next time you can leave the field empty before saving to reset to default

from runtipi.