Closed Daniel-Furcht closed 6 years ago
ronivay
commented
6 years ago Hi,
Older installations seem to indeed break because of the existing symlink. Should be fixed in commit: https://github.com/ronivay/XenOrchestraInstallerUpdater/commit/77142b63bb5fa508712117c51a600944e6a772ce
EDIT: too quick, also commit https://github.com/ronivay/XenOrchestraInstallerUpdater/commit/eb44d6c2db8c47de01f60ece6ee704e1bbbbc18d
Can you confirm, thanks.
ronivay
commented
6 years ago No issues during my own tests so this should be okay.
sspanjers
commented
5 years ago I seem to be having the same problem. Debian 9.6, script seems to be running along properly, it gets to starting the xo-server, waiting for the port to be open. Then it fails with the error message below.
Message: waiting for port to be open Something went wrong, exiting. Check ./xo-install.log for more details and use rollback feature if needed Removing /etc/xo/xo-builds/xen-orchestra-201816121406 because of failed installation.
Checking the installation log: Cloning into '/etc/xo/xo-src/xen-orchestra'... DEPRECATION WARNING on line 29, column 8 of /etc/xo/xo-builds/xen-orchestra-201$ Including .css files with @import is non-standard behaviour which will be remov$ Use a custom importer to maintain this behaviour. Check your implementations do$
DEPRECATION WARNING on line 63, column 8 of /etc/xo/xo-builds/xen-orchestra-201$ Including .css files with @import is non-standard behaviour which will be remov$ Use a custom importer to maintain this behaviour. Check your implementations do$
ronivay
commented
5 years ago Hi,
Issue in the first message is fixed. You seem to have an issue with the service not starting. Errors from the service don’t end up to scripts error log, they are found from the systemd log. Are you running the default configuration or custom ? Please paste your configuration file if you altered it. Also check what you have in service logs after this error occurs with: journalctl -u xo-server -n 50
sspanjers
commented
5 years ago I am just running default configuration, no alterations.
Here is the service log output:
-- Logs begin at Sun 2018-12-16 14:02:11 EST, end at Mon 2018-12-17 18:42:11 EST. --
Dec 16 14:35:30 XenOrchestra xo-server[17987]: at asyncGeneratorStep (/etc/xo/xo-builds/xen-orchestra-201816121430/packages/xo-server/dist/index.js:94:103)
Dec 16 14:35:30 XenOrchestra xo-server[17987]: at _next (/etc/xo/xo-builds/xen-orchestra-201816121430/packages/xo-server/dist/index.js:96:194)
Dec 16 14:35:30 XenOrchestra xo-server[17987]: at /etc/xo/xo-builds/xen-orchestra-201816121430/packages/xo-server/dist/index.js:96:364
Dec 16 14:35:30 XenOrchestra xo-server[17987]: at Promise._execute (/etc/xo/xo-builds/xen-orchestra-201816121430/node_modules/bluebird/js/release/debuggability.js:313:9)
Dec 16 14:35:30 XenOrchestra xo-server[17987]: at Promise._resolveFromExecutor (/etc/xo/xo-builds/xen-orchestra-201816121430/node_modules/bluebird/js/release/promise.js:483:18)
Dec 16 14:35:30 XenOrchestra xo-server[17987]: at new Promise (/etc/xo/xo-builds/xen-orchestra-201816121430/node_modules/bluebird/js/release/promise.js:79:10)
Dec 16 14:35:30 XenOrchestra xo-server[17987]: at /etc/xo/xo-builds/xen-orchestra-201816121430/packages/xo-server/dist/index.js:96:97
Dec 16 14:35:30 XenOrchestra xo-server[17987]: at _createWebServer (/etc/xo/xo-builds/xen-orchestra-201816121430/packages/xo-server/dist/index.js:411:27)
Dec 16 14:35:30 XenOrchestra xo-server[17987]: at createWebServer (/etc/xo/xo-builds/xen-orchestra-201816121430/packages/xo-server/dist/index.js:399:27)
Dec 16 14:35:30 XenOrchestra xo-server[17987]: at /etc/xo/xo-builds/xen-orchestra-201816121430/packages/xo-server/src/index.js:574:26
Dec 16 14:35:30 XenOrchestra xo-server[17987]: at Generator.next (
ronivay
commented
5 years ago Hello,
Okay so it seems you have some other process running in port 80, and xo-server can't bind to it and fails to start. Can you please check from netstat output which process is listening port 80 currently. If it's xo-server, then manually shut it down and try update again. If it's something else, then shut it down or run xo-server in another port.
sspanjers
commented
5 years ago That was it. The VM I had was running apache2 in the background. I disabled that service, and re-installed the script. Worked beautifully! Thanks!
Hi, I have tried update XOA to latest version and a erro raised as described bellow:
During Update
Replacing systemd service configuration file Something went wrong, exiting. Check ./xo-install.log for more details and use rollback feature if needed Removing /etc/xo/xo-builds/xen-orchestra-201801080900 because of failed installation.
Log
Cloning into '/etc/xo/xo-builds/xen-orchestra-201801080900'... DEPRECATION WARNING on line 29, column 8 of /etc/xo/xo-builds/xen-orchestra-201801080900/packages/xo-web/src/index.scss: Including .css files with @import is non-standard behaviour which will be removed in future versions of LibSass. Use a custom importer to maintain this behaviour. Check your implementations documentation on how to create a custom importer.
DEPRECATION WARNING on line 63, column 8 of /etc/xo/xo-builds/xen-orchestra-201801080900/packages/xo-web/src/index.scss: Including .css files with @import is non-standard behaviour which will be removed in future versions of LibSass. Use a custom importer to maintain this behaviour. Check your implementations documentation on how to create a custom importer.
/bin/cp: '/etc/xo/xo-builds/xen-orchestra-201801080900/packages/xo-server/xo-server.service' e '/etc/systemd/system/xo-server.service' são o mesmo arquivo