XO server: 2 vCPU, 4GiB RAM
OS: Debian 11 / 5.10.0-28-amd64 #1 SMP Debian 5.10.209-2 (2024-01-31) x86_64 GNU/Linux
Node.js version: v18.20.2
Yarn version: 1.22.19
XO version: https://github.com/vatesfr/xen-orchestra/commit/771b04acc4480cf138a0c476968d7c613bb8147d
XCP-NG server version: 8.2.1
Environment: 3 hosts, HA, shared storage
The problem is that pool, hosts, VMs (all inventory except one manually added server) seem to disappear from the web UI every 3-6 min, only to reappear automagically after exactly 1 min.
No network changes that could explain timeouts. All was working fine until last week. In fact I think it started after the server patch/update to 8.2.1 (don't recall from which version), the only significant change I did, but no errors in the server logs.
xo-server logs this when it loses the pool (but nothing when the pool reappears):
May 8 17:06:32 xo-ce xo-server[328]: _watchEvents TimeoutError: operation timed out May 8 17:06:32 xo-ce xo-server[328]: at Promise.timeout (/opt/xo/xo-builds/xen-orchestra-202405070909/node_modules/promise-toolbox/timeout.js:11:16) May 8 17:06:32 xo-ce xo-server[328]: at Xapi.apply (file:///opt/xo/xo-builds/xen-orchestra-202405070909/packages/xen-api/index.mjs:773:37) May 8 17:06:32 xo-ce xo-server[328]: at Xapi._call (/opt/xo/xo-builds/xen-orchestra-202405070909/node_modules/limit-concurrency-decorator/src/index.js:85:24) May 8 17:06:32 xo-ce xo-server[328]: at Xapi._watchEvents (file:///opt/xo/xo-builds/xen-orchestra-202405070909/packages/xen-api/index.mjs:1198:31) { May 8 17:06:32 xo-ce xo-server[328]: call: { May 8 17:06:32 xo-ce xo-server[328]: method: 'event.from', May 8 17:06:32 xo-ce xo-server[328]: params: [ [Array], '00000000000063727552,00000000000063699698', 60.1 ] May 8 17:06:32 xo-ce xo-server[328]: } May 8 17:06:32 xo-ce xo-server[328]: } May 8 17:09:32 xo-ce xo-server[328]: _watchEvents TimeoutError: operation timed out May 8 17:09:32 xo-ce xo-server[328]: at Promise.timeout (/opt/xo/xo-builds/xen-orchestra-202405070909/node_modules/promise-toolbox/timeout.js:11:16) May 8 17:09:32 xo-ce xo-server[328]: at Xapi.apply (file:///opt/xo/xo-builds/xen-orchestra-202405070909/packages/xen-api/index.mjs:773:37) May 8 17:09:32 xo-ce xo-server[328]: at Xapi._call (/opt/xo/xo-builds/xen-orchestra-202405070909/node_modules/limit-concurrency-decorator/src/index.js:85:24) May 8 17:09:32 xo-ce xo-server[328]: at Xapi._watchEvents (file:///opt/xo/xo-builds/xen-orchestra-202405070909/packages/xen-api/index.mjs:1198:31) { May 8 17:09:32 xo-ce xo-server[328]: call: { May 8 17:09:32 xo-ce xo-server[328]: method: 'event.from', May 8 17:09:32 xo-ce xo-server[328]: params: [ [Array], '00000000000063727963,00000000000063699698', 60.1 ] May 8 17:09:32 xo-ce xo-server[328]: } May 8 17:09:32 xo-ce xo-server[328]: }Some xcp-ng forum posts from 2023 talked about downgrading to node.js v18 as a solution to a similar timeout issue, but I am already on v18. Would be grateful for any hints, and can share more info.
0 pdonias committed to vatesfr/xen-orchestra fix(CHANGELOG): packages versions (#7639) Introduced by 5d5dc9891f3ee8533c2b1e7239b710f8820c4d2e