@olivierlambert Thanks! I did that and now it is just works.
Thanks for the help!
@olivierlambert Thanks! I did that and now it is just works.
Thanks for the help!
Wow - you guys where right. I had a Raspberry pi running with that address on my network. Sorry for the inconvenience and thanks for your 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.