Xen Orchestra - Community Edition - Installing with Yarn

geek-baba

@scottalanmiller I am using freeness using NFS to backup the VM's, its working flawlessly.

scottalanmiller

@shwetkprabhat said in Xen Orchestra - Community Edition - Installing with Yarn:

@scottalanmiller I am using freeness using NFS to backup the VM's, its working flawlessly.

Oh yes, as secondary storage it is fine. I'd still not advise FreeNAS, you should use FreeBSD, CentOS, Suse or Ubuntu instead, but it's not a big issue.

geek-baba

@DustinB3403 so i deleted the file I created and updated the /opt/xo-server/.xo-server.yaml with the following content (which was using for the new file) and I was getting an error "Cant get to /", I reverted back to last night snapshot.


# BE *VERY* CAREFUL WHEN EDITING!
# YAML FILES ARE SUPER SUPER SENSITIVE TO MISTAKES IN WHITESPACE OR ALIGNMENT!
# visit http://www.yamllint.com/ to validate this file as needed

#=====================================================================

# Example XO-Server configuration.
#
# This file is automatically looking for at the following places:
# - `$HOME/.config/xo-server/config.yaml`
# - `/etc/xo-server/config.yaml`
#
# The first entries have priority.
#
# Note: paths are relative to the configuration file.

#=====================================================================

# It may be necessary to run XO-Server as a privileged user (e.g.
# `root`) for instance to allow the HTTP server to listen on a
# [privileged ports](http://www.w3.org/Daemon/User/Installation/PrivilegedPorts.html).
#
# To avoid security issues, XO-Server can drop its privileges by
# changing the user and the group is running with.
#
# Note: XO-Server will change them just after reading the
# configuration.

# User to run XO-Server as.
#
# Note: The user can be specified using either its name or its numeric
# identifier.
#
# Default: undefined
#user: 'nobody'

# Group to run XO-Server as.
#
# Note: The group can be specified using either its name or its
# numeric identifier.
#
# Default: undefined
#group: 'nogroup'

#=====================================================================

# Configuration of the embedded HTTP server.
http:

  # Hosts & ports on which to listen.
  #
  # By default, the server listens on 0.0.0.0:80.
  listen:
    # Basic HTTP.
    -
      # Address on which the server is listening on.
      #
      # Sets it to '127.0.0.1' to listen only on the local host.
      #
      # Default: '0.0.0.0' (all addresses)
      #hostname: '127.0.0.1'

      # Port on which the server is listening on.
      #
      # Default: undefined
      port: 80

      # Instead of `host` and `port` a path to a UNIX socket may be
      # specified (overrides `host` and `port`).
      #
      # Default: undefined
      #socket: './http.sock'

    # Basic HTTPS.
    #
    # You can find the list of possible options there https://nodejs.org/docs/latest/api/tls.html#tls.createServer
    -
    #   # The only difference is the presence of the certificate and the
    #   # key.
    #   #
    #   #hostname: '127.0.0.1'
      port: 443

    #   # File containing the certificate (PEM format).
    #
    #   # If a chain of certificates authorities is needed, you may bundle
    #   # them directly in the certificate.
    #   #
    #   # Note: the order of certificates does matter, your certificate
    #   # should come first followed by the certificate of the above
    #   # certificate authority up to the root.
    #   #
    #   # Default: undefined
      cert: '/home/xoa/certs/xo-local.crt'

    #   # File containing the private key (PEM format).
    #   #
    #   # If the key is encrypted, the passphrase will be asked at
    #   # server startup.
    #   #
    #   # Default: undefined
      key: '/home/xoa/certs/xo-local.key'

  # If set to true, all HTTP traffic will be redirected to the first
  # HTTPs configuration.
  #redirectToHttps: true

  # List of files/directories which will be served.
  mounts:
    '/': '/root/xo-web/dist/'

  # List of proxied URLs (HTTP & WebSockets).
  proxies:
    # '/any/url': 'http://localhost:54722'

# HTTP proxy configuration used by xo-server to fetch resources on the
# Internet.
#
# See: https://github.com/TooTallNate/node-proxy-agent#maps-proxy-protocols-to-httpagent-implementations
#httpProxy: 'http://jsmith:[email protected]:3128'

#=====================================================================

# Connection to the Redis server.
redis:
    # Unix sockets can be used
    #
    # Default: undefined
    #socket: /var/run/redis/redis.sock

    # Syntax: redis://[db[:password]@]hostname[:port][/db-number]
    #
    # Default: redis://localhost:6379/0
    #uri: redis://redis.company.lan/42

    # List of aliased commands.
    #
    # See http://redis.io/topics/security#disabling-of-specific-commands
    #renameCommands:
    #  del: '3dda29ad-3015-44f9-b13b-fa570de92489'
    #  srem: '3fd758c9-5610-4e9d-a058-dbf4cb6d8bf0'


# Directory containing the database of XO.
# Currently used for logs.
#
# Default: '/var/lib/xo-server/data'
#datadir: '/var/lib/xo-server/data'

DustinB3403

@shwetkprabhat I'm sending you a Private message.

geek-baba

@DustinB3403 thanks for helping out and resolving the issue! I cant thank you enough for the time you spent (remote-ing into the machine yesterday and helping all day today via private messages).

For the larger community it looks like if you create a new config.yaml file, XO will register that as config source and any changes after that is not taken into the account, you should use the default config file created by the script (i.e. /opt/xo-server/.xo-server.yaml) to start with or update the installation using the update script and then manually update the default config file.

DustinB3403

@shwetkprabhat glad we were able to sort it out for you.

Texkonc

Yarn? I knew Xen was full of duct tape and bubble gum.

DustinB3403

@Texkonc . . .

Texkonc

@DustinB3403 said in Xen Orchestra - Community Edition - Installing with Yarn:

@Texkonc . . .

Friiiiiday!

DustinB3403

@Texkonc said in Xen Orchestra - Community Edition - Installing with Yarn:

@DustinB3403 said in Xen Orchestra - Community Edition - Installing with Yarn:

@Texkonc . . .

Friiiiiday!

The issue is this is XO. . . not Xen. . .

Texkonc

@DustinB3403 said in Xen Orchestra - Community Edition - Installing with Yarn:

@Texkonc said in Xen Orchestra - Community Edition - Installing with Yarn:

@DustinB3403 said in Xen Orchestra - Community Edition - Installing with Yarn:

@Texkonc . . .

Friiiiiday!

The issue is this is XO. . . not Xen. . .

Tomato, Tomato

DustinB3403

@Texkonc said in Xen Orchestra - Community Edition - Installing with Yarn:

@DustinB3403 said in Xen Orchestra - Community Edition - Installing with Yarn:

@Texkonc said in Xen Orchestra - Community Edition - Installing with Yarn:

@DustinB3403 said in Xen Orchestra - Community Edition - Installing with Yarn:

@Texkonc . . .

Friiiiiday!

The issue is this is XO. . . not Xen. . .

Tomato, Tomato

Not even close.

Tomato / Car tire. . .

hobbit666

So created a new VM installed Ubuntu 16.04 and tried 17.04.
Ran sudo apt-get update and upgrade to update the system.

Then ran

sudo bash
sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_installer/master/xo_install.sh | bash

but I get nothing on http://serverip or https://serverip.

What steps am I missing

p.s. Also ran the

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

commands to update it

DustinB3403

@hobbit666 said in Xen Orchestra - Community Edition - Installing with Yarn:

So created a new VM installed Ubuntu 16.04 and tried 17.04.
Ran sudo apt-get update and upgrade to update the system.

Then ran

sudo bash
sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_installer/master/xo_install.sh | bash

but I get nothing on http://serverip or https://serverip.

What steps am I missing

p.s. Also ran the

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

commands to update it

Check the status of the service with systemctl status xo-server.service

hobbit666

@dustinb3403

xo-server.service - XO Server
   Loaded: loaded (/etc/systemd/system/xo-server.service; enabled; vendor preset: enabled)
   Active: inactive (dead) (Result: exit-code) since Tue 2017-07-18 14:20:10 BST; 1 day 20h ago
  Process: 1230 ExecStart=/usr/local/bin/node ./bin/xo-server (code=exited, status=1/FAILURE)
 Main PID: 1230 (code=exited, status=1/FAILURE)

>Jul 18 14:20:10 WYN-XENORCH xo-server[1230]:     at Function.Module.runMain (module.js:605:10)
Jul 18 14:20:10 WYN-XENORCH xo-server[1230]:     at startup (bootstrap_node.js:158:16)
Jul 18 14:20:10 WYN-XENORCH xo-server[1230]:     at bootstrap_node.js:575:3
Jul 18 14:20:10 WYN-XENORCH systemd[1]: xo-server.service: Main process exited, code=exited, status=1/FAILURE
Jul 18 14:20:10 WYN-XENORCH systemd[1]: xo-server.service: Unit entered failed state.
Jul 18 14:20:10 WYN-XENORCH systemd[1]: xo-server.service: Failed with result 'exit-code'.
Jul 18 14:20:10 WYN-XENORCH systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
Jul 18 14:20:10 WYN-XENORCH systemd[1]: Stopped XO Server.
Jul 18 14:20:10 WYN-XENORCH systemd[1]: xo-server.service: Start request repeated too quickly.
Jul 18 14:20:10 WYN-XENORCH systemd[1]: Failed to start XO Server.

DustinB3403

@hobbit666 can you format that as code for easier reading ...

Danp

@hobbit666 Try restarting the service with sudo systemctl restart xo-server.service and then post the output from journalctl -u xo-server -f -n 50

hobbit666

root@WYN-XENORCH:~# sudo systemctl restart xo-server.service
root@WYN-XENORCH:~# journalctl -u xo-server -f -n 50
-- Logs begin at Tue 2017-07-18 14:20:01 BST. --
Jul 20 13:42:40 WYN-XENORCH systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
Jul 20 13:42:40 WYN-XENORCH systemd[1]: Stopped XO Server.
Jul 20 13:42:40 WYN-XENORCH systemd[1]: Started XO Server.
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]: module.js:487
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]:     throw err;
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]:     ^
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]: Error: Cannot find module 'bluebird'
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]:     at Function.Module._resolveFilename (module.js:485:15)
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]:     at Function.Module._load (module.js:437:25)
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]:     at Module.require (module.js:513:17)
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]:     at require (internal/module.js:11:18)
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]:     at Object.<anonymous> (/opt/xo-server/bin/xo-server:12:18)
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]:     at Module._compile (module.js:569:30)
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]:     at Object.Module._extensions..js (module.js:580:10)
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]:     at Module.load (module.js:503:32)
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]:     at tryModuleLoad (module.js:466:12)
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]:     at Function.Module._load (module.js:458:3)
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]:     at Function.Module.runMain (module.js:605:10)
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]:     at startup (bootstrap_node.js:158:16)
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]:     at bootstrap_node.js:575:3
Jul 20 13:42:40 WYN-XENORCH systemd[1]: xo-server.service: Main process exited, code=exited, status=1/FAILURE
Jul 20 13:42:40 WYN-XENORCH systemd[1]: xo-server.service: Unit entered failed state.
Jul 20 13:42:40 WYN-XENORCH systemd[1]: xo-server.service: Failed with result 'exit-code'.
Jul 20 13:42:40 WYN-XENORCH systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
Jul 20 13:42:40 WYN-XENORCH systemd[1]: Stopped XO Server.
Jul 20 13:42:40 WYN-XENORCH systemd[1]: Started XO Server.
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]: module.js:487
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]:     throw err;
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]:     ^
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]: Error: Cannot find module 'bluebird'
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]:     at Function.Module._resolveFilename (module.js:485:15)
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]:     at Function.Module._load (module.js:437:25)
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]:     at Module.require (module.js:513:17)
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]:     at require (internal/module.js:11:18)
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]:     at Object.<anonymous> (/opt/xo-server/bin/xo-server:12:18)
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]:     at Module._compile (module.js:569:30)
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]:     at Object.Module._extensions..js (module.js:580:10)
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]:     at Module.load (module.js:503:32)
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]:     at tryModuleLoad (module.js:466:12)
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]:     at Function.Module._load (module.js:458:3)
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]:     at Function.Module.runMain (module.js:605:10)
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]:     at startup (bootstrap_node.js:158:16)
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]:     at bootstrap_node.js:575:3
Jul 20 13:42:40 WYN-XENORCH systemd[1]: xo-server.service: Main process exited, code=exited, status=1/FAILURE
Jul 20 13:42:40 WYN-XENORCH systemd[1]: xo-server.service: Unit entered failed state.
Jul 20 13:42:40 WYN-XENORCH systemd[1]: xo-server.service: Failed with result 'exit-code'.
Jul 20 13:42:40 WYN-XENORCH systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
Jul 20 13:42:40 WYN-XENORCH systemd[1]: Stopped XO Server.
Jul 20 13:42:40 WYN-XENORCH systemd[1]: xo-server.service: Start request repeated too quickly.
Jul 20 13:42:40 WYN-XENORCH systemd[1]: Failed to start XO Server.

Danp

@hobbit666 That's not good. Any errors logged when you installed XO?

hobbit666

@danp No everything seemed to go straight through no issues.