Upgrade to PeerTube v5.0.0 failure

wadejbeckett · Décembre 14, 2022, 5:12

Hi there,
I trust you are well.

My PeerTube instance won’t start after upgrade. I don’t know where to start debugging this. I’d appreciate any assistance.

Dec 14 17:07:54 noiz peertube[961]: at Object. (/var/www/peertube/versions/peertube-v5.0.0/dist/server/helpers/logger.js:12:18)
Dec 14 17:07:54 noiz peertube[961]: at Module._compile (node:internal/modules/cjs/loader:1155:14)
Dec 14 17:07:55 noiz systemd[1]: peertube.service: Main process exited, code=exited, status=1/FAILURE
Dec 14 17:07:55 noiz systemd[1]: peertube.service: Failed with result ‹ exit-code ›.
Dec 14 17:07:55 noiz systemd[1]: peertube.service: Scheduled restart job, restart counter is at 5.
Dec 14 17:07:55 noiz systemd[1]: Stopped PeerTube daemon.
Dec 14 17:07:55 noiz systemd[1]: peertube.service: Start request repeated too quickly.
Dec 14 17:07:55 noiz systemd[1]: peertube.service: Failed with result ‹ exit-code ›.
Dec 14 17:07:55 noiz systemd[1]: Failed to start PeerTube daemon.
Dec 14 17:08:40 noiz systemd[1]: Started PeerTube daemon.
Dec 14 17:08:41 noiz peertube[982]: /var/www/peertube/versions/peertube-v5.0.0/node_modules/config/lib/config.js:179
Dec 14 17:08:41 noiz peertube[982]: throw new Error(‹ Configuration property " › + property + ‹ " is not defined ›);
Dec 14 17:08:41 noiz peertube[982]: ^
Dec 14 17:08:41 noiz peertube[982]: Error: Configuration property « object_storage.upload_acl.public » is not defined
Dec 14 17:08:41 noiz peertube[982]: at Config.get (/var/www/peertube/versions/peertube-v5.0.0/node_modules/config/lib/config.js:179:11)
Dec 14 17:08:41 noiz peertube[982]: at Object. (/var/www/peertube/versions/peertube-v5.0.0/dist/server/initializers/config.js:117:28)
Dec 14 17:08:41 noiz peertube[982]: at Module._compile (node:internal/modules/cjs/loader:1155:14)
Dec 14 17:08:41 noiz peertube[982]: at Object.Module._extensions…js (node:internal/modules/cjs/loader:1209:10)
Dec 14 17:08:41 noiz peertube[982]: at Module.load (node:internal/modules/cjs/loader:1033:32)
Dec 14 17:08:41 noiz peertube[982]: at Function.Module._load (node:internal/modules/cjs/loader:868:12)
Dec 14 17:08:41 noiz peertube[982]: at Module.require (node:internal/modules/cjs/loader:1057:19)
Dec 14 17:08:41 noiz peertube[982]: at require (node:internal/modules/cjs/helpers:103:18)
Dec 14 17:08:41 noiz peertube[982]: at Object. (/var/www/peertube/versions/peertube-v5.0.0/dist/server/helpers/logger.js:12:18)
Dec 14 17:08:41 noiz peertube[982]: at Module._compile (node:internal/modules/cjs/loader:1155:14)
Dec 14 17:08:41 noiz systemd[1]: peertube.service: Main process exited, code=exited, status=1/FAILURE

JohnLivingston · Décembre 14, 2022, 6:41

I had the same error on one of my instance.
Even if you are not using S3 storage, just copy and overwrite this block of configuration from the production.yml.example file to your production.yml:

github.com

Chocobozzz/PeerTube/blob/ce502d09a9c44b4972712a899f19eb4afda8b01d/config/production.yaml.example#L145-L190

      
        
            object_storage:
              enabled: false
            
            
  # Without protocol, will default to HTTPS
              endpoint: '' # 's3.amazonaws.com' or 's3.fr-par.scw.cloud' for example
            
            
  region: 'us-east-1'
            
            
  upload_acl:
                # Set this ACL on each uploaded object of public/unlisted videos
                public: 'public-read'
                # Set this ACL on each uploaded object of private/internal videos
                # PeerTube can proxify requests to private objects so your users can access them
                private: 'private'
            
            
  proxy:
                # If private files (private/internal video files) have a private ACL, users can't access directly the ressource
                # PeerTube can proxify requests between your object storage service and your users
                # If you disable PeerTube proxy, ensure you use your own proxy that is able to access the private files
                # Or you can also set a public ACL for private files in object storage if you don't want to use a proxy

This file has been truncated. show original

Note: if you are using S3 storage, don’t overwrite, but compare your current config with the expected one.

JohnLivingston · Décembre 14, 2022, 6:43

To be more specific, I think the exact error is this change, that has to be made (even if you are not using S3):

wadejbeckett · Décembre 14, 2022, 7:19

I found the solution. I copied the production.yaml.example into the production folder, edited it appropriately and made it live. Issue resolved.

wadejbeckett · Décembre 15, 2022, 11:01

I managed to resolve the original issue, however the ‹ channels › are no longer displaying in the GUI. Any ideas?