Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. PeerTube
  3. I update 3.2.1 to 3.3.0 error

I update 3.2.1 to 3.3.0 error

Scheduled Pinned Locked Moved PeerTube
5 Posts 4 Posters 864 Views 4 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Z Offline
      Z Offline
      zohupvn
      wrote on last edited by
      #1

      When I update it, it gives me this error, please help

      Aug 10 16:16:21 "column": 12,
      Aug 10 16:16:21 "file": "domain.js",
      Aug 10 16:16:21 "function": "IncomingMessage.EventEmitter.emit",
      Aug 10 16:16:21 "line": 467,
      Aug 10 16:16:21 "method": "emit",
      Aug 10 16:16:24 npm ERR! code ELIFECYCLE
      Aug 10 16:16:24 npm ERR! errno 1
      Aug 10 16:16:24 npm ERR! peertube@3.3.0 start: `node dist/server`
      Aug 10 16:16:24 npm ERR! Exit status 1
      Aug 10 16:16:24 npm ERR!
      Aug 10 16:16:24 npm ERR! Failed at the peertube@3.3.0 start script.
      Aug 10 16:16:24 npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
      Aug 10 16:16:24
      Aug 10 15:39:19 15:M 10 Aug 2021 08:39:19.764 # Server initialized
      Aug 10 15:39:19 15:M 10 Aug 2021 08:39:19.764 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
      Aug 10 15:39:19 Redis service endpoint listening on https://:::3000
      Aug 10 15:39:20 15:M 10 Aug 2021 08:39:20.481 * DB loaded from disk: 0.717 seconds
      Aug 10 15:39:20 15:M 10 Aug 2021 08:39:20.481 * Ready to accept connections
      Aug 10 15:39:21 2021-08-10 08:39:21,482 INFO success: redis entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
      Aug 10 15:39:21 2021-08-10 08:39:21,482 INFO success: redis-service entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
      Aug 10 15:41:22 [GET] /healthcheck
      
      girishG 1 Reply Last reply
      0
      • Z zohupvn

        When I update it, it gives me this error, please help

        Aug 10 16:16:21 "column": 12,
        Aug 10 16:16:21 "file": "domain.js",
        Aug 10 16:16:21 "function": "IncomingMessage.EventEmitter.emit",
        Aug 10 16:16:21 "line": 467,
        Aug 10 16:16:21 "method": "emit",
        Aug 10 16:16:24 npm ERR! code ELIFECYCLE
        Aug 10 16:16:24 npm ERR! errno 1
        Aug 10 16:16:24 npm ERR! peertube@3.3.0 start: `node dist/server`
        Aug 10 16:16:24 npm ERR! Exit status 1
        Aug 10 16:16:24 npm ERR!
        Aug 10 16:16:24 npm ERR! Failed at the peertube@3.3.0 start script.
        Aug 10 16:16:24 npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
        Aug 10 16:16:24
        Aug 10 15:39:19 15:M 10 Aug 2021 08:39:19.764 # Server initialized
        Aug 10 15:39:19 15:M 10 Aug 2021 08:39:19.764 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
        Aug 10 15:39:19 Redis service endpoint listening on https://:::3000
        Aug 10 15:39:20 15:M 10 Aug 2021 08:39:20.481 * DB loaded from disk: 0.717 seconds
        Aug 10 15:39:20 15:M 10 Aug 2021 08:39:20.481 * Ready to accept connections
        Aug 10 15:39:21 2021-08-10 08:39:21,482 INFO success: redis entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
        Aug 10 15:39:21 2021-08-10 08:39:21,482 INFO success: redis-service entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
        Aug 10 15:41:22 [GET] /healthcheck
        
        girishG Offline
        girishG Offline
        girish
        Staff
        wrote on last edited by
        #2

        @zohupvn I can't quite make out what the issue is. Do you have any logs about this error message?

        Z 1 Reply Last reply
        0
        • girishG girish

          @zohupvn I can't quite make out what the issue is. Do you have any logs about this error message?

          Z Offline
          Z Offline
          zohupvn
          wrote on last edited by
          #3

          my logs about this error message
          it shows the start , not the run
          @girish Aug 10 16:16:21 "column": 12,
          Aug 10 16:16:21 "file": "domain.js",
          Aug 10 16:16:21 "function": "IncomingMessage.EventEmitter.emit",
          Aug 10 16:16:21 "line": 467,
          Aug 10 16:16:21 "method": "emit",
          Aug 10 16:16:24 npm ERR! code ELIFECYCLE
          Aug 10 16:16:24 npm ERR! errno 1
          Aug 10 16:16:24 npm ERR! peertube@3.3.0 start: node dist/server
          Aug 10 16:16:24 npm ERR! Exit status 1
          Aug 10 16:16:24 npm ERR!
          Aug 10 16:16:24 npm ERR! Failed at the peertube@3.3.0 start script.
          Aug 10 16:16:24 npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

          nebulonN 1 Reply Last reply
          0
          • Z zohupvn

            my logs about this error message
            it shows the start , not the run
            @girish Aug 10 16:16:21 "column": 12,
            Aug 10 16:16:21 "file": "domain.js",
            Aug 10 16:16:21 "function": "IncomingMessage.EventEmitter.emit",
            Aug 10 16:16:21 "line": 467,
            Aug 10 16:16:21 "method": "emit",
            Aug 10 16:16:24 npm ERR! code ELIFECYCLE
            Aug 10 16:16:24 npm ERR! errno 1
            Aug 10 16:16:24 npm ERR! peertube@3.3.0 start: node dist/server
            Aug 10 16:16:24 npm ERR! Exit status 1
            Aug 10 16:16:24 npm ERR!
            Aug 10 16:16:24 npm ERR! Failed at the peertube@3.3.0 start script.
            Aug 10 16:16:24 npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

            nebulonN Offline
            nebulonN Offline
            nebulon
            Staff
            wrote on last edited by
            #4

            @zohupvn do you have a bit more log lines there? It looks like the end of a crash stacktrace, which could be very useful to get down to the issue.

            rmdesR 1 Reply Last reply
            0
            • nebulonN nebulon

              @zohupvn do you have a bit more log lines there? It looks like the end of a crash stacktrace, which could be very useful to get down to the issue.

              rmdesR Offline
              rmdesR Offline
              rmdes
              wrote on last edited by rmdes
              #5

              @nebulon Having the same here, I had to remove peertube-plugin-categories for the app to boot without issue.

              log part about this :
              Aug 18 09:17:27 [yourdomain.tld:443 peertube-plugin-categories] 2021-08-18 07:17:27.335 error: uncaughtException: Unexpected token < in JSON at position 0
              Aug 18 09:17:27 SyntaxError: Unexpected token < in JSON at position 0
              Aug 18 09:17:27 at JSON.parse (<anonymous>)
              Aug 18 09:17:27 at IncomingMessage.<anonymous> (/app/data/storage/plugins/node_modules/peertube-plugin-categories/src/server/api.js:26:24)
              Aug 18 09:17:27 at IncomingMessage.emit (events.js:327:22)
              Aug 18 09:17:27 at IncomingMessage.EventEmitter.emit (domain.js:467:12)
              Aug 18 09:17:27 at endReadableNT (internal/streams/readable.js:1327:12)
              Aug 18 09:17:27 at processTicksAndRejections (internal/process/task_queues.js:80:21) {
              Aug 18 09:17:27 "error": {
              Aug 18 09:17:27 "stack": "SyntaxError: Unexpected token < in JSON at position 0\n at JSON.parse (<anonymous>)\n at IncomingMessage.<anonymous> (/app/data/storage/plugins/node_modules/peertube-plugin-categories/src/server/api.js:26:24)\n at IncomingMessage.emit (events.js:327:22)\n at IncomingMessage.EventEmitter.emit (domain.js:467:12)\n at endReadableNT (internal/streams/readable.js:1327:12)\n at processTicksAndRejections (internal/process/task_queues.js:80:21)",
              Aug 18 09:17:27 "message": "Unexpected token < in JSON at position 0"

              I went to /app/data/storage/plugins/node_modules/ to remove it, the app boot log

              Aug 18 09:17:49 [yourdomain.tld:443] 2021-08-18 07:17:49.879 info: Registering plugin or theme peertube-plugin-categories.
              Aug 18 09:17:49 [yourdomain.tld:443] 2021-08-18 07:17:49.880 info: Unregister plugin peertube-plugin-categories.
              Aug 18 09:17:49 [yourdomain.tld:443] 2021-08-18 07:17:49.880 error: Cannot register plugin categories, skipping. {
              Aug 18 09:17:49 "err": {
              Aug 18 09:17:49 "stack": "Error: ENOENT: no such file or directory, open '/app/data/storage/plugins/node_modules/peertube-plugin-categories/package.json'",
              Aug 18 09:17:49 "message": "ENOENT: no such file or directory, open '/app/data/storage/plugins/node_modules/peertube-plugin-categories/package.json'",
              Aug 18 09:17:49 "errno": -2,
              Aug 18 09:17:49 "code": "ENOENT",
              Aug 18 09:17:49 "syscall": "open",
              Aug 18 09:17:49 "path": "/app/data/storage/plugins/node_modules/peertube-plugin-categories/package.json"
              Aug 18 09:17:49 }

              But then boot just fine, I'm going to try to reinstall this plugin from the front-end and see how it goes !

              edit : reinstall the plugin work just fine

              1 Reply Last reply
              1
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


                • Login

                • Don't have an account? Register

                • Login or register to search.
                • First post
                  Last post
                0
                • Categories
                • Recent
                • Tags
                • Popular
                • Bookmarks
                • Search