@olivierlambert thanks for the hint. I cleaned up VMs on my SR and now everything works perfectly.
Thanks for the help.
@olivierlambert thanks for the hint. I cleaned up VMs on my SR and now everything works perfectly.
Thanks for the help.
Just to further add. It seems that all my VMs are down/inaccessible some how.
Furthermore I can't ping the VM's and they appear faulty in XCP-NGs console.
This might have happened since last update of XCP-NG. I'm not sure about this but I just wanted to mention it.
I suddenly have trouble launching XOA. I can ssh into the instance but when I try to update XOA from the cli I get this error:
[03:35 01] xoa@xoa:~$ sudo xoa-updater --upgrade
[sudo] password for xoa:
stable channel selected
New versions available:
xen-orchestra 5.75.0 (5.74.3 installed)
xo-server 5.103.1 (5.102.3 installed)
xo-web-free 5.104.0 (5.103.0 installed)
Downloading packages...
✖ {
message: "ENOENT: no such file or directory, mkdir '/tmp/xoa-updater'"
}
The status of the xo-server status is:
[03:36 01] xoa@xoa:~$ sudo systemctl status xo-server.service
● xo-server.service - XO Server
Loaded: loaded (/etc/systemd/system/xo-server.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2022-11-01 03:32:40 EDT; 6min ago
Main PID: 456 (node)
Tasks: 11 (limit: 2330)
Memory: 146.5M
CGroup: /system.slice/xo-server.service
└─456 node /usr/local/bin/xo-server
Nov 01 03:38:59 xoa xo-server[456]: error: Error: connect ECONNREFUSED ::1:6379
Nov 01 03:38:59 xoa xo-server[456]: at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1157:16)
Nov 01 03:38:59 xoa xo-server[456]: at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
Nov 01 03:38:59 xoa xo-server[456]: errno: -111,
Nov 01 03:38:59 xoa xo-server[456]: code: 'ECONNREFUSED',
Nov 01 03:38:59 xoa xo-server[456]: syscall: 'connect',
Nov 01 03:38:59 xoa xo-server[456]: address: '::1',
Nov 01 03:38:59 xoa xo-server[456]: port: 6379
Nov 01 03:38:59 xoa xo-server[456]: }
Nov 01 03:38:59 xoa xo-server[456]: }
Any help is highly appreciated.
@Andrew thanks for your reply. I have more than enough cores and memory slots for one CPU so I guess I’ll put one of the CPUs in the drawer.
I have a Dell r630 with dual CPUs. I’m not utilising half of the cores and my question is whether it will have any performance difference if I remove one of the CPUs?
Just to information if anyone else ends in a similar situation. My problem was created by two issues: 1) Failing to updating redis-server packet 2) Trouble with node modules.
Failing to update redis-server: I found out that I had trouble updating redis with the apt package manager. It stalled because the Forever service blocked apt upgrade
. So I stopped the forever service forever stop orchestra
and then updated redis.
The trouble with the node modules: Followed this post and removed the node modules and rebuild.
Does anyone know if this is related to node or is it related to reverting the XO back to a previous snapshot?
Just a little update: I didn't find a solution to the problem so I ended up restoring from my backup. However, I think I found what originally created the problems:
It was not directly related to XO, but before I upgraded XO, which caused the problems, I ran sudo apt upgrade
and somehow the redis-server service stalled and maybe corrupted the update and thus created problems when I tried to update XO.
So what I did was, after I restored from the backup I shutdown the redis-server.service and then sudo apt upgrade
and then upgraded XO from git. And now it works. But thanks a lot for your help @julien-f and @Danp.
I have just restored XO from a backup because I had some challenges after upgrading XO community edition.
However, now my scheduled backup jobs fails all with the following error: ENOENT: no such file or directory, uv_cwd
The full log error:
{
"data": {
"mode": "full",
"reportWhen": "failure"
},
"id": "1625253198637",
"jobId": "7c1a955d-40c5-4f84-8b1f-573911427001",
"jobName": "Weekly Backup",
"message": "backup",
"scheduleId": "0bd28888-e278-4628-87e1-b0ba58c6f892",
"start": 1625253198637,
"status": "failure",
"tasks": [
{
"data": {
"type": "remote",
"id": "7847ae41-54e0-4534-9790-a9c57ca6744a"
},
"id": "1625253199171",
"message": "get remote adapter",
"start": 1625253199171,
"status": "failure",
"end": 1625253199171,
"result": {
"errno": -2,
"code": "ENOENT",
"syscall": "uv_cwd",
"message": "ENOENT: no such file or directory, uv_cwd",
"name": "Error",
"stack": "Error: ENOENT: no such file or directory, uv_cwd\n at process.wrappedCwd (internal/bootstrap/switches/does_own_process_state.js:130:28)\n at process.cwd (/home/mex/xen-orchestra/node_modules/graceful-fs/polyfills.js:10:19)\n at handleArguments (/home/mex/xen-orchestra/node_modules/execa/index.js:39:36)\n at NfsHandler.execa [as _execa] (/home/mex/xen-orchestra/node_modules/execa/index.js:75:17)\n at NfsHandler._sync (/home/mex/xen-orchestra/@xen-orchestra/fs/dist/_mount.js:83:18)"
}
}
],
"end": 1625253199172
}
As mentioned I restored the XO VM from a backup. I also made a snapshot that I also reverted back to. My Backup remote is working and tested.
Any help is highly appreciated.
@julien-f and @Danp thanks a lot for your help! Now it works if I manually run cli.mjs
mex@xo-community:~/xen-orchestra/packages/xo-server$ sudo ./dist/cli.mjs
2021-06-30T06:21:41.457Z xo:main INFO Configuration loaded.
2021-06-30T06:21:41.478Z xo:main INFO Web server listening on http://[::]:80
2021-06-30T06:21:41.924Z xo:main INFO Setting up / → /home/mex/xen-orchestra/packages/xo-web/dist
However, what should I do to recreate the service to start on boot. When setting up and using forever as described here. I'm still not able to load the web interface.
It seems that the service starts and is active
mex@xo-community:~/xen-orchestra/packages/xo-server$ sudo service orchestra status
● orchestra.service - LSB: forever-service startup script for orchestra
Loaded: loaded (/etc/init.d/orchestra; generated)
Active: active (exited) since Wed 2021-06-30 08:28:05 CEST; 3min 15s ago
Docs: man:systemd-sysv-generator(8)
Process: 1141 ExecStart=/etc/init.d/orchestra start (code=exited, status=0/SUCCESS)
Jun 30 08:28:04 xo-community systemd[1]: Starting LSB: forever-service startup script for orchestra...
Jun 30 08:28:05 xo-community orchestra[1141]: (node:1145) Warning: Accessing non-existent property 'padLevels' of module exports inside c
Jun 30 08:28:05 xo-community orchestra[1141]: (Use `node --trace-warnings ...` to show where the warning was created)
Jun 30 08:28:05 xo-community orchestra[1141]: (node:1145) Warning: Accessing non-existent property 'padLevels' of module exports inside c
Jun 30 08:28:05 xo-community orchestra[1141]: Starting orchestra
Jun 30 08:28:05 xo-community orchestra[1141]: (node:1162) Warning: Accessing non-existent property 'padLevels' of module exports inside c
Jun 30 08:28:05 xo-community orchestra[1141]: (Use `node --trace-warnings ...` to show where the warning was created)
Jun 30 08:28:05 xo-community orchestra[1141]: (node:1162) Warning: Accessing non-existent property 'padLevels' of module exports inside c
Jun 30 08:28:05 xo-community systemd[1]: Started LSB: forever-service startup script for orchestra.
@julien-f said in xo-server/bin doesn't exist after updating with yarn build.:
@runevn Don't know much about
forever
, in the meantime, you can try to runxo-server
manually:> cd packages/xo-server > ./dist/cli.mjs
Thanks for your reply @julien-f . When I manually run xo-server it still doesn't work. Here is the output
mex@xo-community:~/xen-orchestra/packages/xo-server$ sudo ./dist/cli.mjs
(node:65352) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.
(Use `node --trace-warnings ...` to show where the warning was created)
/home/mex/xen-orchestra/packages/xo-server/dist/xapi/mixins/index.js:2
import _gpu, * as __gpu from "./gpu";
^^^^^^
SyntaxError: Cannot use import statement outside a module
at wrapSafe (internal/modules/cjs/loader.js:1001:16)
at Module._compile (internal/modules/cjs/loader.js:1049:27)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
at Module.load (internal/modules/cjs/loader.js:950:32)
at Function.Module._load (internal/modules/cjs/loader.js:790:14)
at ModuleWrap.<anonymous> (internal/modules/esm/translators.js:199:29)
at ModuleJob.run (internal/modules/esm/module_job.js:169:25)
at async Loader.import (internal/modules/esm/loader.js:177:24)
at async Object.loadESM (internal/process/esm_loader.js:68:5)
mex@xo-community:~/xen-orchestra/packages/xo-server$
Is there any other information that I can provide?
@danp said in xo-server/bin doesn't exist after updating with yarn build.:
@runevn IDK. Maybe @julien-f can suggest a solution for this.
But thank you for your effort! I really appreciate it.
Does this means that XO can't find its own module or is it node's module?
mex@xo-community:~$ node --trace-warnings ...
internal/modules/cjs/loader.js:905
throw err;
^
Error: Cannot find module '/home/mex/...'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
at Function.Module._load (internal/modules/cjs/loader.js:746:27)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:76:12)
at internal/main/run_main_module.js:17:47 {
code: 'MODULE_NOT_FOUND',
requireStack: []
}
@danp said in xo-server/bin doesn't exist after updating with yarn build.:
What's your Node version? Post the output of
node -v
. You should be on v14.17.1.
Yes
mex@xo-community:~/xen-orchestra/packages/xo-server$ node -v
v14.17.1
Again, thanks for your replies.
@danp I have just deleted the forever-service and reinstalled it but it didn't help. I can't still access the Web UI.
I still get this status message
mex@xo-community:~/xen-orchestra/packages/xo-server$ sudo service orchestra status
● orchestra.service - LSB: forever-service startup script for orchestra
Loaded: loaded (/etc/init.d/orchestra; generated)
Active: active (exited) since Tue 2021-06-29 11:52:21 CEST; 3s ago
Docs: man:systemd-sysv-generator(8)
Process: 30529 ExecStart=/etc/init.d/orchestra start (code=exited, status=0/SUCCESS)
Jun 29 11:52:21 xo-community systemd[1]: Starting LSB: forever-service startup script for orchestra...
Jun 29 11:52:21 xo-community orchestra[30529]: (node:30533) Warning: Accessing non-existent property 'padLevels' of module exports inside
Jun 29 11:52:21 xo-community orchestra[30529]: (Use `node --trace-warnings ...` to show where the warning was created)
Jun 29 11:52:21 xo-community orchestra[30529]: (node:30533) Warning: Accessing non-existent property 'padLevels' of module exports inside
Jun 29 11:52:21 xo-community orchestra[30529]: Starting orchestra
Jun 29 11:52:21 xo-community orchestra[30529]: (node:30550) Warning: Accessing non-existent property 'padLevels' of module exports inside
Jun 29 11:52:21 xo-community orchestra[30529]: (Use `node --trace-warnings ...` to show where the warning was created)
Jun 29 11:52:21 xo-community orchestra[30529]: (node:30550) Warning: Accessing non-existent property 'padLevels' of module exports inside
Jun 29 11:52:21 xo-community systemd[1]: Started LSB: forever-service startup script for orchestra.
@danp said in xo-server/bin doesn't exist after updating with yarn build.:
I'm not familiar with forever, so I can't help any further on this.
May I ask, if you do not use forever how would you then redo the service?
Thanks for your help.
@danp Thanks for your reply. Now I have run (based on these instructions )
However, I can't still reach the web UI of XO
yarn global add forever
yarn global add forever-service
# Be sure to edit the path below to where your install is located!
cd /home/username/xen-orchestra/packages/xo-server/
# Change the username below to the user owning XO
forever-service install orchestra -r username -s dist/cli.mjs
Or should I redo my service in another way?
Now the output of systemctl status orchestra is:
mex@xo-community:~/xen-orchestra/packages/xo-server$ sudo service orchestra status
● orchestra.service - LSB: forever-service startup script for orchestra
Loaded: loaded (/etc/init.d/orchestra; generated)
Active: active (exited) since Tue 2021-06-29 09:01:08 CEST; 4s ago
Docs: man:systemd-sysv-generator(8)
Process: 1857 ExecStart=/etc/init.d/orchestra start (code=exited, status=0/SUCCESS)
Jun 29 09:01:08 xo-community systemd[1]: Starting LSB: forever-service startup script for orchestra...
Jun 29 09:01:08 xo-community orchestra[1857]: (node:1861) Warning: Accessing non-existent property 'padLevels' of module exports inside c
Jun 29 09:01:08 xo-community orchestra[1857]: (Use `node --trace-warnings ...` to show where the warning was created)
Jun 29 09:01:08 xo-community orchestra[1857]: (node:1861) Warning: Accessing non-existent property 'padLevels' of module exports inside c
Jun 29 09:01:08 xo-community orchestra[1857]: Service orchestra already running
Jun 29 09:01:08 xo-community systemd[1]: Started LSB: forever-service startup script for orchestra.
After updating Xen Orchestra (community edition) I can't start XO. I get the error message that xo-server/bin does not exist.
I just followed these steps:
$ git checkout .
$ git pull --ff-only
$ yarn
$ yarn build
mex@xo-community:~/xen-orchestra$ sudo systemctl status orchestra.service
● orchestra.service - LSB: forever-service startup script for orchestra
Loaded: loaded (/etc/init.d/orchestra; generated)
Active: failed (Result: exit-code) since Mon 2021-06-28 18:15:23 CEST; 6s ago
Docs: man:systemd-sysv-generator(8)
Process: 2865 ExecStart=/etc/init.d/orchestra start (code=exited, status=255/EXCEPTION)
Jun 28 18:15:22 xo-community orchestra[2865]: Starting orchestra
Jun 28 18:15:22 xo-community orchestra[2865]: -bash: line 0: cd: /home/mex/xen-orchestra/packages/xo-server/bin: No such file or directory
Jun 28 18:15:23 xo-community orchestra[2865]: (node:2896) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
Jun 28 18:15:23 xo-community orchestra[2865]: (Use `node --trace-warnings ...` to show where the warning was created)
Jun 28 18:15:23 xo-community orchestra[2865]: (node:2896) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
Jun 28 18:15:23 xo-community orchestra[2865]: error: Cannot start forever
Jun 28 18:15:23 xo-community orchestra[2865]: error: script /root/xo-server does not exist.
Jun 28 18:15:23 xo-community systemd[1]: orchestra.service: Control process exited, code=exited, status=255/EXCEPTION
Jun 28 18:15:23 xo-community systemd[1]: orchestra.service: Failed with result 'exit-code'.
Jun 28 18:15:23 xo-community systemd[1]: Failed to start LSB: forever-service startup script for orchestra.
This is the content of the xo-server folder:
mex@xo-community:~/xen-orchestra/packages/xo-server$ ls -l
total 52
-rw-r--r-- 1 root root 4961 Jun 28 17:29 config.toml
drwxr-xr-x 8 root root 4096 Jun 28 18:13 dist
drwxr-xr-x 2 root root 4096 Mar 3 21:45 docs
drwxr-xr-x 13 root root 4096 Jun 28 17:47 node_modules
-rw-r--r-- 1 root root 5096 Jun 28 17:29 package.json
-rw-r--r-- 1 root root 1331 Mar 3 21:45 README.md
-rw-r--r-- 1 root root 4766 Mar 3 21:45 sample.config.toml
-rw-r--r-- 1 root root 2302 Mar 3 21:45 signin.pug
drwxr-xr-x 8 root root 4096 Jun 28 17:29 src
-rw-r--r-- 1 root root 246 Mar 3 21:45 xo-server.service
How to fix this error? Please let me know if you need additional information.
thank