'move-to-object-storage' jobs failing after upgrade to v6.x

Reply to 'move-to-object-storage' jobs failing after upgrade to v6.x on Fri, 05 Jan 2024 12:10:17 GMT

girish — Fri, 05 Jan 2024 12:10:17 GMT

@shrey great work figuring the root cause! I have published a new package now that highlights the breaking changes in 6.0 .

For others reading, the main issue was that some of the configuration keys have changed in peertube 6. See https://github.com/Chocobozzz/PeerTube/blob/develop/CHANGELOG.md#v600 for more information. For example, if you use object storage to store videos, the storage paths have changed.

Reply to 'move-to-object-storage' jobs failing after upgrade to v6.x on Fri, 05 Jan 2024 03:57:55 GMT

shrey — Fri, 05 Jan 2024 03:57:55 GMT

@girish
Thanks for this tip!

Reply to 'move-to-object-storage' jobs failing after upgrade to v6.x on Thu, 04 Jan 2024 12:32:35 GMT

girish — Thu, 04 Jan 2024 12:32:35 GMT

I think since I suspect this might take a bit to fix is to roll back the app to previous release and play around with a clone of the app instead.

Reply to 'move-to-object-storage' jobs failing after upgrade to v6.x on Thu, 04 Jan 2024 12:32:06 GMT

girish — Thu, 04 Jan 2024 12:32:06 GMT

@shrey I think upstream dev is asking you to test a code change. If you want to try this on Cloudron:

Put the app in recovery mode (in the repair section of app)
Now , you can open a web terminal and then run the command that the author wanted
After this, start the app with /app/pkg/start.sh .

Note that changes will be lost when you remove the recovery mode. Also, see https://docs.cloudron.io/troubleshooting/#unresponsive-app

Reply to 'move-to-object-storage' jobs failing after upgrade to v6.x on Thu, 04 Jan 2024 09:45:40 GMT

nebulon — Thu, 04 Jan 2024 09:45:40 GMT

Since those npm packages are part of the app code as dependencies, this wont work on Cloudron as those are in the read-only portion of the filesystem by design. I guess for that we have to wait for upstream to update the dependencies with a release. Blindly updating libraries an app is using can have all kinds of side-effects.

Reply to 'move-to-object-storage' jobs failing after upgrade to v6.x on Thu, 04 Jan 2024 09:44:20 GMT

shrey — Thu, 04 Jan 2024 09:44:20 GMT

Hi.

This release is continuing to experience the aforementioned issues.

As per the upstream-maintainer, it is recommended to try an upgrade to the underlying s3 related packages.

Ref: https://github.com/Chocobozzz/PeerTube/issues/6149#issuecomment-1876710960

But when i try to run the provided command in the app Terminal:
yarn upgrade --latest @aws-sdk/client-s3 @aws-sdk/lib-storage @aws-sdk/s3-request-presigner @smithy/node-http-handler

i receive the following errors:

root@1a096a10-f841-480a-be1f-4e93cd2053b3:/app/code/server# yarn upgrade --latest @aws-sdk/client-s3 @aws-sdk/lib-storage @aws-sdk/s3-request-presigner @smithy/node-http-handler
yarn upgrade v1.22.19
warning Skipping preferred cache folder "/usr/local/share/.cache/yarn" because it is not writable.
warning Selected the next writable cache folder in the list, will be "/tmp/.yarn-cache-0".
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
error Could not write file "/app/code/server/yarn-error.log": "EROFS: read-only file system, open '/app/code/server/yarn-error.log'"
error An unexpected error occurred: "EROFS: read-only file system, unlink '/app/code/server/node_modules/.yarn-integrity'".
info Visit https://yarnpkg.com/en/docs/cli/upgrade for documentation about this command.
root@1a096a10-f841-480a-be1f-4e93cd2053b3:/app/code/server#

How do i go about this now?

PS: Without resolving this issue, the PeerTube v6.0.2 version in Cloudron is practically broken/useless.