Problems Upgrading XenOrchestra
-
@dustinb3403 Sorry for not doing this earlier, here it is:
root@xong:~# 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 3884 100 3884 0 0 7185 0 --:--:-- --:--:-- --:--:-- 7179
Stopping xo-server...
Checking for Yarn package...
Checking for Yarn update...
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E074D16EB6FF4DE3
W: Failed to fetch https://dl.yarnpkg.com/debian/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E074D16EB6FF4DE3
W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists... Done
Building dependency tree
Reading state information... Done
yarn is already the newest version (0.27.5-1).
The following package was automatically installed and is no longer required:
libuv1
Use 'sudo apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 202 not upgraded.
Checking for Repo change...
fatal: destination path 'xen-orchestra' already exists and is not an empty directory.
sed: can't read /lib/systemd/system/xo-server.service: No such file or directory
Checking xen-orchestra...
Current branch master
Current version 5.20.0 / 5.20.1
0 updates available
Updating from source...
Saved working directory and index state WIP on master: dd60d82 fix(xo-web/Backup-ng/logs): ability to retry a single failed/interrupted VM backup (#3052)
HEAD is now at dd60d82 fix(xo-web/Backup-ng/logs): ability to retry a single failed/interrupted VM backup (#3052)
Dropped refs/stash@{0} (18b359699d970b29635b05696058ebe0772ee4f4)
Already up-to-date.
Clearing directories...
Installing...
yarn install v0.27.5
error The workspace feature is currently experimental and needs to be manually enabled - please add "workspaces-experimental true" to your .yarnrc file.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
yarn build v0.27.5
error The workspace feature is currently experimental and needs to be manually enabled - please add "workspaces-experimental true" to your .yarnrc file.
Updated version 5.20.0 / 5.20.1
Checking plugins...
Restarting xo-server... -
@papaf My yarn repo was not being used for key issues, it's now ok and updated, and it's all working.
Thanks anyway! -
@papaf Ok, the compilation did more things this time, way more. But in the end, the result is unfortunately the same. XO isn't starting and, as you can see from the output linked, I have no xo-server nor xo-web in /opt, just the .old copies.
I've loaded the output on pastebin because it's gigantic. BTW, I have no idea why it prints all this stuff...
Compilation output on pastebinThanks again!
-
@papaf I would honestly just start with a fresh install at this point. It's so trivial to get a new instance up and running.
-
@papaf I don't see any errors in the upgrade log.
If you run
systemctl status xo-server.servicewhat output do you get? -
@bnrstnr said in Xen Orchestra - Community Edition - Installing with Yarn:
@papaf I would honestly just start with a fresh install at this point. It's so trivial to get a new instance up and running.
Also this isn't a bad idea. The only downside is @papaf might not have a recent configuration backup that could be used to restore his settings.
But even setting up the settings again generally isn't a difficult process.
-
@dustinb3403 This the output:
● xo-server.service - XO Server
Loaded: loaded (/etc/systemd/system/xo-server.service; enabled; vendor preset: enabled)
Active: inactive (dead) (Result: exit-code) since Fri 2018-06-08 15:16:43 CEST; 1h 16min ago
Process: 7992 ExecStart=/usr/local/bin/node ./bin/xo-server (code=exited, status=200/CHDIR)
Main PID: 7992 (code=exited, status=200/CHDIR)Jun 08 15:16:42 xong systemd[1]: xo-server.service: Main process exited, code=exited, status=200/CHDIR
Jun 08 15:16:42 xong systemd[1]: xo-server.service: Unit entered failed state.
Jun 08 15:16:42 xong systemd[1]: xo-server.service: Failed with result 'exit-code'.
Jun 08 15:16:43 xong systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
Jun 08 15:16:43 xong systemd[1]: Stopped XO Server.
Jun 08 15:16:43 xong systemd[1]: xo-server.service: Start request repeated too quickly.
Jun 08 15:16:43 xong systemd[1]: Failed to start XO Server.But this is expected as there's no active directory in /opt, just the .old copies.
Also, how do I backup the old config and how do I start clean?
-
@papaf said in Xen Orchestra - Community Edition - Installing with Yarn:
@dustinb3403 This the output:
● xo-server.service - XO Server
Loaded: loaded (/etc/systemd/system/xo-server.service; enabled; vendor preset: enabled)
Active: inactive (dead) (Result: exit-code) since Fri 2018-06-08 15:16:43 CEST; 1h 16min ago
Process: 7992 ExecStart=/usr/local/bin/node ./bin/xo-server (code=exited, status=200/CHDIR)
Main PID: 7992 (code=exited, status=200/CHDIR)Jun 08 15:16:42 xong systemd[1]: xo-server.service: Main process exited, code=exited, status=200/CHDIR
Jun 08 15:16:42 xong systemd[1]: xo-server.service: Unit entered failed state.
Jun 08 15:16:42 xong systemd[1]: xo-server.service: Failed with result 'exit-code'.
Jun 08 15:16:43 xong systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
Jun 08 15:16:43 xong systemd[1]: Stopped XO Server.
Jun 08 15:16:43 xong systemd[1]: xo-server.service: Start request repeated too quickly.
Jun 08 15:16:43 xong systemd[1]: Failed to start XO Server.But this is expected as there's no active directory in /opt, just the .old copies.
Also, how do I backup the old config and how do I start clean?
In order to export a config backup the system would need to be working, do you have a snapshot you can revert to that was working? If so, revert login to Export, export the config file and then make a new Debian/Ubuntu VM and reinstall. Then just import your config file into the new installation and shutdown the old installation.
-
@dustinb3403 If I rename the two .old directories in /opt, xo starts.
You really think it's necessary to start from scratch? Isn't there a way to clean everything xo related and compile from the start?
-
@papaf said in Xen Orchestra - Community Edition - Installing with Yarn:
@dustinb3403 If I rename the two .old directories in /opt, xo starts.
You really think it's necessary to start from scratch? Isn't there a way to clean everything xo related and compile from the start?
Well there might be, the most simple approach is often to just build a new instance. XO is designed to be disposable, since you can always just import your configuration.
Rebuilding takes maybe 15 minutes (in most cases).
-
@dustinb3403 In case I want to recompile from scratch on the same VM, should I clear /opt? Is that enough?
-
@papaf said in Xen Orchestra - Community Edition - Installing with Yarn:
@dustinb3403 In case I want to recompile from scratch on the same VM, should I clear /opt? Is that enough?
Yeah just remove the folders that have xen-orchestra.
-
@dustinb3403 Ugh, I ran into yet another issue: apparently, recent ubuntu distro have a great deal of issue booting on XenServer 7.0, which I need to keep... can't update...
At the same time, it seems every boot media for 16.10 has disappeared from existence... so, what's the recommended ubuntu distro for this, that is available currently for download? -
@papaf said in Xen Orchestra - Community Edition - Installing with Yarn:
@dustinb3403 Ugh, I ran into yet another issue: apparently, recent ubuntu distro have a great deal of issue booting on XenServer 7.0, which I need to keep... can't update...
At the same time, it seems every boot media for 16.10 has disappeared from existence... so, what's the recommended ubuntu distro for this, that is available currently for download?"Current" is the recommended distro, always current. If you are having issues with Ubuntu you can use Debian as well.
-
@papaf said in Xen Orchestra - Community Edition - Installing with Yarn:
@dustinb3403 Ugh, I ran into yet another issue: apparently, recent ubuntu distro have a great deal of issue booting on XenServer 7.0, which I need to keep... can't update...
At the same time, it seems every boot media for 16.10 has disappeared from existence... so, what's the recommended ubuntu distro for this, that is available currently for download?Are you using the latest version of XenServer? The latest version is 7.5
-
@black3dynamite said in Xen Orchestra - Community Edition - Installing with Yarn:
Are you using the latest version of XenServer? The latest version is 7.5
His hardware might have compatibility issues or some other such issue.
-
@dustinb3403 It's more like no downtime allowed, hence no chance to update. I'm trying with 18.04 server, but I need to be able to specify a couple of kernel parameters at boot or it won't start...
-
@papaf said in Xen Orchestra - Community Edition - Installing with Yarn:
@dustinb3403 It's more like no downtime allowed, hence no chance to update. I'm trying with 18.04 server, but I need to be able to specify a couple of kernel parameters at boot or it won't start...
The mythos of "No downtime" means your business doesn't understand that scheduled downtime is usually way less downtime compared to unplanned downtime.
-
@papaf said in Xen Orchestra - Community Edition - Installing with Yarn:
@dustinb3403 It's more like no downtime allowed, hence no chance to update. I'm trying with 18.04 server, but I need to be able to specify a couple of kernel parameters at boot or it won't start...
Which Ubuntu 18.04 iso did you download?
By default, you end up downloading there new installer.
http://releases.ubuntu.com/18.04/ubuntu-18.04-live-server-amd64.isoThe old installer can be found here:
http://cdimage.ubuntu.com/releases/18.04/release/ubuntu-18.04-server-amd64.iso -
@black3dynamite I used the old one, and it worked. I succesfully installed xo now. Normally, I'd like to know what went wrong, but it's too late and friday
