Looks like there was a problem when starting xo-server/reading journalctl...
-
Something didn't work when I tried to install xen orchestra,following this tutorial :
https://www.youtube.com/watch?v=bq1iKO-0jWs&feature=emb_logo
root@ziomario-z390aoruspro:/etc/xen/XenOrchestraInstallerUpdater# ./xo-install.sh
Welcome to automated Xen Orchestra install
Following options will be used for installation:
OS: Ubuntu 20
Basedir: /opt/xo
User: root
Port: 443
HTTPS: true
Git Branch for source: master
Following plugins will be installed: all
Number of previous installations to preserve: 3
Node.js and yarn auto update: trueErrorlog is stored to /etc/xen/XenOrchestraInstallerUpdater/logs/xo-install.log-202017081445 for debug purposes
Xen Orchestra configuration will be stored to /root/.config/xo-server/config.toml, if you don't want it to be replaced with every update, set CONFIGUPDATE to false in xo-install.cfg
- Autoinstall
- Update / Install without packages
- Deploy docker container
- Rollback to another existing installation
- Exit
: 1
[ok] OS Ubuntu so making sure universe repository is enabled
[ok] Running apt-get update
[..] Installing build dependencies, redis server, python, git, libvhdi-utils, lv[ok] Installing build dependencies, redis server, python, git, libvhdi-utils, lvm2, nfs-common, cifs-utils, curl
[..] Installing apt-transport-https and ca-certificates packages to support http[ok] Installing apt-transport-https and ca-certificates packages to support https repos
[ok] Installing node.js
[ok] Installing yarn
[ok] Enabling and starting redis service
[ok] Enabling and starting rpcbind service
[ok] Creating missing basedir to /opt/xo
[ok] Creating missing xo-builds directory to /opt/xo/xo-builds
[info] Fetching Xen Orchestra source code
[info] Creating install directory: /opt/xo/xo-builds/xen-orchestra-202017081445
[info] xo-server and xo-web build quite a while. Grab a cup of coffee and lay back
[ok] Running installation
[ok] Installing plugins
[info] Fixing binary path in systemd service configuration file
[info] Adding WorkingDirectory parameter to systemd service configuration file
[info] Fixing relative path to xo-web installation in xo-server configuration file
[info] Changing port in xo-server configuration file
[info] Enabling HTTPS in xo-server configuration file
[info] Activating modified configuration file[info] Symlinking fresh xo-server install/update to /opt/xo/xo-server
[info] Symlinking fresh xo-web install/update to /opt/xo/xo-web[info] Replacing systemd service configuration file
[info] Reloading systemd configuration[info] Starting xo-server...
waiting for port to be open
waiting for port to be open
waiting for port to be open
waiting for port to be open
waiting for port to be open
waiting for port to be open[fail] Looks like there was a problem when starting xo-server/reading journalctl. Please see logs for more details
attached log :
[0_1597671077223_xo-install.log-202017081445](Uploading 100%) xo-install.log-202017081445.txt
-
The log didn't capture the full error. You should try manually checking with the following command --
journalctl -u xo-server -n 100
You can increase the numeric portion as needed.
-
@Danp said in Looks like there was a problem when starting xo-server/reading journalctl...:
journalctl -u xo-server -n 100
ago 17 14:50:42 ziomario-z390aoruspro xo-server[22308]: 2020-08-17T12:50:42.606Z xo:main INFO Configuration loaded.
ago 17 14:50:42 ziomario-z390aoruspro xo-server[22308]: 2020-08-17T12:50:42.629Z xo:main WARN Web server could not listen on https://localhost:443 {
ago 17 14:50:42 ziomario-z390aoruspro xo-server[22308]: error: Error: listen EADDRINUSE: address already in use :::443
ago 17 14:50:42 ziomario-z390aoruspro xo-server[22308]: at Server.setupListenHandle [as _listen2] (net.js:1313:16)
ago 17 14:50:42 ziomario-z390aoruspro xo-server[22308]: at listenInCluster (net.js:1361:12)
ago 17 14:50:42 ziomario-z390aoruspro xo-server[22308]: at Server.listen (net.js:1447:7)
ago 17 14:50:42 ziomario-z390aoruspro xo-server[22308]: at Server.listen (/opt/xo/xo-builds/xen-orchestra-202017081445/node_modules/http-server-plus/index.js:135:12)
ago 17 14:50:42 ziomario-z390aoruspro xo-server[22308]: at makeWebServerListen (/opt/xo/xo-builds/xen-orchestra-202017081445/packages/xo-server/src/index.js:454:41) {
ago 17 14:50:42 ziomario-z390aoruspro xo-server[22308]: code: 'EADDRINUSE',
ago 17 14:50:42 ziomario-z390aoruspro xo-server[22308]: errno: 'EADDRINUSE',
ago 17 14:50:42 ziomario-z390aoruspro xo-server[22308]: syscall: 'listen',
ago 17 14:50:42 ziomario-z390aoruspro xo-server[22308]: address: '::',
ago 17 14:50:42 ziomario-z390aoruspro xo-server[22308]: port: 443,
ago 17 14:50:42 ziomario-z390aoruspro xo-server[22308]: niceAddress: 'https://localhost:443'
ago 17 14:50:42 ziomario-z390aoruspro xo-server[22308]: }
ago 17 14:50:42 ziomario-z390aoruspro xo-server[22308]: } -
root@ziomario-z390aoruspro:/etc/xen/XenOrchestraInstallerUpdater/logs# sudo netstat -tulpn | grep :443
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 3173/vmware-hostd
tcp6 0 0 :::443 :::* LISTEN 3173/vmware-hostd -
@ziomario said in Looks like there was a problem when starting xo-server/reading journalctl...:
vmware-hostd
Why is that service installed / running?
-
Hello. I have removed vmware and now the port 443 is free. but now,what should I do ? I'm not sure that xen orchestra is working great. to which IP I should connect to see the xen orchestra web administration ? Since the installation ended with an error before,now I don't know what to do. I tried to reinstall it choosing 1 on the menu,but this is what happened :
1. Autoinstall 2. Update / Install without packages 3. Deploy docker container 4. Rollback to another existing installation 5. Exit : 1 [ok] OS Ubuntu so making sure universe repository is enabled [ok] Running apt-get update [..] Installing build dependencies, redis server, python, git, libvhdi-utils, lv[ok] Installing build dependencies, redis server, python, git, libvhdi-utils, lvm2, nfs-common, cifs-utils, curl [..] Installing apt-transport-https and ca-certificates packages to support http[ok] Installing apt-transport-https and ca-certificates packages to support https repos [info] Checking current node.js version [info] node.js version already on 12 [ok] Enabling and starting redis service [ok] Enabling and starting rpcbind service [info] Fetching Xen Orchestra source code [info] Creating install directory: /opt/xo/xo-builds/xen-orchestra-202017081708 [info] No changes to xen-orchestra since previous install. Skipping xo-server and xo-web build. [info] Cleaning up install directory: /opt/xo/xo-builds/xen-orchestra-2020170817
the IP number of xcp-ng is 192.168.122.150,but if It seems that this IP is not the IP that I should use,as u can see below :
the IP of the PC where I have installed xen orchestra is 192.68.1.6,but :
Firefox canβt establish a connection to the server at 192.168.1.6:443.
Firefox canβt establish a connection to the server at https://192.168.1.6.
-
@ziomario Please use the Markdown syntax for code/console output, otherwise it's very hard to read your content.
``` your console output ```
-
@olivierlambert : refresh the page
-
are u there ? what should I do ?
-
You could try issuing the command
systemctl restart xo-server
and then check the logs again. -
I've gone into /opt and I have removed the xo folder. otherwise it didn't work.
-
I'm not familiar with that particular script, so I can't help you debug further. Best option at this point is to blow away the VM and start over with a completely fresh install of Ubuntu.