Posts made by geek-baba

geek-baba

@dustinb3403 Not sure I understand the question...I am running xo-server 5.10.2 and xo-web 5.10.5 on Ubuntu 16.04.2 LTS (GNU/Linux 4.4.0-87-generic x86_64)

geek-baba

Anyone tried to update to 5.11? It broke my installation, reverted to last snapshot, let me know how it goes for others...

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.

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'

geek-baba

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

geek-baba

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

/opt/xo-server/.xo-server.yaml

I see this file, I believe I have been creating a new file which is causing the issue. I didn't realize since the new file also works flawlessly.

geek-baba

@scottalanmiller as a NAS

geek-baba

@Danp I have used 2 different commands and both resulted in wiping the file:

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

1st one I used to for last update and 2nd one to test when you asked to do it today.

geek-baba

@DustinB3403 I am using the freenas with the community edition, what are the issues you see with this setup...

geek-baba

@DustinB3403 I dont know the path of this file...

geek-baba

@Danp just tested and it again wiped out the config file.

geek-baba

@Danp /home/xoa/certs/xo-local.crt

geek-baba

@DustinB3403 thats right, I used your installer and updater for community edition. The only thing outside I did was to setup self signed certs for access.

geek-baba

@DustinB3403 I am not sure, after the update the https stopped working, so I went back to the tutorial I followed to set it up https://xen-orchestra.com/forum/topic/440/problems-setting-up-https-on-xo and I used the same path and recreated it and it started to work again.

geek-baba

@Danp I lost the config file itself /opt/xo-server/config.yaml, it was blank and I had to recreate. Now before I updated after defining the GIT local user, I tried next-version and stable commands, so that may have caused the issue.

geek-baba

@Danp I used your guide to enable https and only changed one file mentioned in the guide

https://xen-orchestra.com/forum/topic/440/problems-setting-up-https-on-xo/2

geek-baba

@Danp thanks it solved the issue, it broke my self signed ssl cert though

And I am not sure what caused sudden increase in interest on this topic, my email was blowing up this morning

geek-baba

@Danp
I have tried 2 of them:

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

Output of 1:
root@xo:~# sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -f
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 2624 100 2624 0 0 9088 0 --:--:-- --:--:-- --:--:-- 9079
Stopping xo-server...
Checking for Yarn package...
Checking for Yarn update...
Reading package lists... Done
Building dependency tree
Reading state information... Done
yarn is already the newest version (0.27.5-1).
The following packages were automatically installed and are no longer required:
linux-headers-4.4.0-62 linux-headers-4.4.0-62-generic linux-headers-4.4.0-72 linux-headers-4.4.0-72-generic linux-headers-4.4.0-75 linux-headers-4.4.0-75-generic linux-headers-4.4.0-78
linux-headers-4.4.0-78-generic linux-headers-4.4.0-79 linux-headers-4.4.0-79-generic linux-image-4.4.0-62-generic linux-image-4.4.0-72-generic linux-image-4.4.0-75-generic linux-image-4.4.0-78-generic
linux-image-4.4.0-79-generic linux-image-extra-4.4.0-62-generic linux-image-extra-4.4.0-72-generic linux-image-extra-4.4.0-75-generic linux-image-extra-4.4.0-78-generic
linux-image-extra-4.4.0-79-generic rlwrap
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Checking xo-server...
Current branch stable
Current version v5.8.0
91 updates available
Updating from source...

*** Please tell me who you are.

Run

git config --global user.email "[email protected]"
git config --global user.name "Your Name"

to set your account's default identity.
Omit --global to set the identity only in this repository.

[email protected] prebuild /opt/xo-server
index-modules src/api src/xapi/mixins src/xo-mixins

index generated src/api/index.js
index generated src/xapi/mixins/index.js
index generated src/xo-mixins/index.js

[email protected] build /opt/xo-server
gulp build --production

[05:39:08] Using gulpfile /opt/xo-server/gulpfile.js
[05:39:08] Starting 'build'...
[05:39:08] Starting 'clean'...
[05:39:08] Finished 'clean' after 6.08 ms
[05:39:08] Starting 'buildCoffee'...
[05:39:08] Starting 'buildEs6'...
[05:39:13] Finished 'buildCoffee' after 5.01 s
[05:39:32] Finished 'buildEs6' after 24 s
[05:39:32] Finished 'build' after 24 s
Done in 46.71s.
Updated version v5.8.0
Checking xo-web...
Current branch stable
Current version v5.8.3
44 updates available
Updating from source...

*** Please tell me who you are.

Run

git config --global user.email "[email protected]"
git config --global user.name "Your Name"

to set your account's default identity.
Omit --global to set the identity only in this repository.

fatal: unable to auto-detect email address (got 'root@xo.(none)')
Cannot save the current index state
Updating 9199784..2ee7333
error: Your local changes to the following files would be overwritten by merge:
yarn.lock
Please, commit your changes or stash them before you can merge.
Aborting
Clearing directories...
Installing...
yarn install v0.27.5
[1/4] Resolving packages...
[2/4] Fetching packages...
warning [email protected]: The platform "linux" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
[4/4] Rebuilding all packages...
success Saved lockfile.
$ npm run build

[email protected] build /opt/xo-web
npm run build-indexes && NODE_ENV=production gulp build

[email protected] build-indexes /opt/xo-web
index-modules --auto src

index generated src/common/intl/locales/index.js
index generated src/common/themes/index.js
[05:40:06] Using gulpfile /opt/xo-web/gulpfile.js
[05:40:06] Starting 'build'...
[05:40:06] Starting 'buildPages'...
[05:40:06] Starting 'buildScripts'...
[05:40:06] Starting 'buildStyles'...
[05:40:06] Starting 'copyAssets'...
[05:40:10] Finished 'buildPages' after 4.21 s
[05:40:15] Finished 'buildStyles' after 8.84 s
[05:40:16] Finished 'copyAssets' after 9.74 s
[05:42:42] Finished 'buildScripts' after 2.6 min
[05:42:42] Finished 'build' after 2.6 min
Done in 181.81s.
Updated version v5.8.3
Restarting xo-server...

geek-baba

Hi @DustinB3403

I am trying to update the xo community install however after running the script successfully the xo web and server version remains old. I can see the master stable source is updated with latest version.
https://github.com/vatesfr/xo-web - 5.10.4
https://github.com/vatesfr/xo-server - 5.10.0

After running the updater script my xo is still at xo-server 5.8.0 and xo-web 5.9.0.