XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. beber75
    B
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 1
    • Posts 5
    • Groups 0

    beber75

    @beber75

    0
    Reputation
    5
    Profile views
    5
    Posts
    0
    Followers
    0
    Following
    Joined
    Last Online

    beber75 Unfollow Follow

    Latest posts made by beber75

    • RE: xo-service not starting anymore after upgrade

      Hi,

      If I well remember it was 5.48.x
      Meanwhile I've installed a new vm from scratch so I could not reproduce the problem or dig further.

      If it happen again, I'll ask directly the maintainer of the script.

      Regards

      posted in Xen Orchestra
      B
      beber75
    • RE: xo-service not starting anymore after upgrade

      Thanks anyway, I'll check it

      posted in Xen Orchestra
      B
      beber75
    • RE: xo-service not starting anymore after upgrade

      I used:

      sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | sudo bash

      also tryed

      sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | sudo bash -s -- -f

      posted in Xen Orchestra
      B
      beber75
    • RE: xo-service not starting anymore after upgrade

      Ok, more informations, using a tail -f /var/log/syslog and trying to start the service again, I see some missing modules:

      deki@xoc:~$ tail -f /var/log/syslog
      May 22 13:12:28 xoc systemd[1]: Started XO Server.
      May 22 13:12:28 xoc xo-server[5861]: 2020-05-22T13:12:28.648Z xo:xo-server ERROR uncaught exception { error: { Error: Cannot find module 'memorystore'
      May 22 13:12:28 xoc xo-server[5861]: at Function.Module._resolveFilename (module.js:548:15)
      May 22 13:12:28 xoc xo-server[5861]: at Function.Module._load (module.js:475:25)
      May 22 13:12:28 xoc xo-server[5861]: at Module.require (module.js:597:17)
      May 22 13:12:28 xoc xo-server[5861]: at require (internal/module.js:11:18)
      May 22 13:12:28 xoc xo-server[5861]: at Object.<anonymous> (/opt/xen-orchestra/packages/xo-server/src/index.js:12:1)
      May 22 13:12:28 xoc xo-server[5861]: at Module._compile (module.js:653:30)
      May 22 13:12:28 xoc xo-server[5861]: at Object.Module._extensions..js (module.js:664:10)
      May 22 13:12:28 xoc xo-server[5861]: at Module.load (module.js:566:32)
      May 22 13:12:28 xoc xo-server[5861]: at tryModuleLoad (module.js:506:12)
      May 22 13:12:28 xoc xo-server[5861]: at Function.Module._load (module.js:498:3)
      May 22 13:12:28 xoc xo-server[5861]: at Module.require (module.js:597:17)
      May 22 13:12:28 xoc xo-server[5861]: at require (internal/module.js:11:18)
      May 22 13:12:28 xoc xo-server[5861]: at Object.<anonymous> (/opt/xen-orchestra/packages/xo-server/index.js:11:18)
      May 22 13:12:28 xoc xo-server[5861]: at Module._compile (module.js:653:30)
      May 22 13:12:28 xoc xo-server[5861]: at Object.Module._extensions..js (module.js:664:10)
      May 22 13:12:28 xoc xo-server[5861]: at Module.load (module.js:566:32) code: 'MODULE_NOT_FOUND' } }
      May 22 13:12:28 xoc systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
      May 22 13:12:28 xoc systemd[1]: xo-server.service: Scheduled restart job, restart counter is at 5.
      May 22 13:12:28 xoc systemd[1]: Stopped XO Server.
      May 22 13:12:28 xoc systemd[1]: xo-server.service: Start request repeated too quickly.
      May 22 13:12:28 xoc systemd[1]: xo-server.service: Failed with result 'start-limit-hit'.
      May 22 13:12:28 xoc systemd[1]: Failed to start XO Server.

      posted in Xen Orchestra
      B
      beber75
    • xo-service not starting anymore after upgrade

      Hi,

      after being cut from internet for weeks, I've recovered today my line and decided to update my xo community edition. Since then, the xo-service is not starting anymore. I received this message:

      deki@xoc:~$ systemctl status xo-server.service
      ā— xo-server.service - XO Server
      Loaded: loaded (/lib/systemd/system/xo-server.service; enabled; vendor preset: enabled)
      Active: failed (Result: start-limit-hit) since Fri 2020-05-22 12:55:35 UTC; 1s ago
      Process: 4838 ExecStart=/usr/local/bin/node ./bin/xo-server (code=exited, status=0/SUCCESS)
      Main PID: 4838 (code=exited, status=0/SUCCESS)

      mai 22 12:55:35 xoc systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
      mai 22 12:55:35 xoc systemd[1]: xo-server.service: Scheduled restart job, restart counter is at 5.
      mai 22 12:55:35 xoc systemd[1]: Stopped XO Server.
      mai 22 12:55:35 xoc systemd[1]: xo-server.service: Start request repeated too quickly.
      mai 22 12:55:35 xoc systemd[1]: xo-server.service: Failed with result 'start-limit-hit'.
      mai 22 12:55:35 xoc systemd[1]: Failed to start XO Server.

      I've tryed to launch the command:

      sudo systemctl reset-failed xo-server.service

      but it does not help too.

      posted in Xen Orchestra
      B
      beber75