@yann said in New Rust Xen guest tools:

In Debian 10 and Ubuntu 20.04, what I see is on apt-get update on first run is:

 Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown.  Could not handshake: Error in the certificate verification. [IP: 172.65.251.78 443]

That would look like Gitlab current SSL certificates would be depending on a root CA that only appeared in newer distros?

And on subsequent runs, then I start getting 401 replies as others reported.

I'm getting this error with a clean install of Debian 12.4... was this something that was addressed and is appearing again, or is the solution at this stage to still install manually?

Hi again, apologies for my tardiness. I've switched to Ubuntu server rather than Debian and all appears to be well again. I can only assume that it is an environment/dependency issue in Debian.

OK, so XOA is working fine on my side except for the pfSense/FreeBSD VM, but to be honest I'm not sure I have ever tried a file level restore on it before and can't see any reason why I would ever need to in future.

I guess I'm looking for an environment issue then, perhaps a dependency? I've got 2 independent sites (one at home, one at our local church) that are configured the same and having the same problems. Will try setting up on Ubuntu and see if that resolves.

@badrAZ @julien-f

A little more info... I'm also having this problem, but it seems only non-Linux file systems have a problem on my side. Let me know if I can run/supply anything on this side that might be useful?

Debian, CentOS and Ubuntu files recoveries are all fine, but Windows Server, Windows 10 and pfSense drives are throwing the same error others have posted previously. Error seems to start a step earlier than what has been previously suggested though?

Server is XO Community on Debian, NFS remote (Synology NAS) all LVMs I think.

Selecting backup date is fine. Selecting drive from the backup gives this error:

Mar 25 06:05:32 BKP01 xo-server[431]: { Error: spawn fusermount ENOENT
Mar 25 06:05:32 BKP01 xo-server[431]:     at Process.ChildProcess._handle.onexit (internal/child_process.js:190:19)
Mar 25 06:05:32 BKP01 xo-server[431]:     at onErrorNT (internal/child_process.js:362:16)
Mar 25 06:05:32 BKP01 xo-server[431]:     at _combinedTickCallback (internal/process/next_tick.js:139:11)
Mar 25 06:05:32 BKP01 xo-server[431]:     at process._tickCallback (internal/process/next_tick.js:181:9)
Mar 25 06:05:32 BKP01 xo-server[431]:   errno: 'ENOENT',
Mar 25 06:05:32 BKP01 xo-server[431]:   code: 'ENOENT',
Mar 25 06:05:32 BKP01 xo-server[431]:   syscall: 'spawn fusermount',
Mar 25 06:05:32 BKP01 xo-server[431]:   path: 'fusermount',
Mar 25 06:05:32 BKP01 xo-server[431]:   spawnargs: [ '-uz', '/tmp/tmp-431GWsDT1lOqXyY' ],
Mar 25 06:05:32 BKP01 xo-server[431]:   originalMessage: 'spawn fusermount ENOENT',
Mar 25 06:05:32 BKP01 xo-server[431]:   command: 'fusermount -uz /tmp/tmp-431GWsDT1lOqXyY',
Mar 25 06:05:32 BKP01 xo-server[431]:   exitCode: undefined,
Mar 25 06:05:32 BKP01 xo-server[431]:   signal: undefined,
Mar 25 06:05:32 BKP01 xo-server[431]:   signalDescription: undefined,
Mar 25 06:05:32 BKP01 xo-server[431]:   stdout: '',
Mar 25 06:05:32 BKP01 xo-server[431]:   stderr: '',
Mar 25 06:05:32 BKP01 xo-server[431]:   failed: true,
Mar 25 06:05:32 BKP01 xo-server[431]:   timedOut: false,
Mar 25 06:05:32 BKP01 xo-server[431]:   isCanceled: false,
Mar 25 06:05:32 BKP01 xo-server[431]:   killed: false }

Partitions still load, but then this error occurs when selecting a partition:

Mar 25 06:07:51 BKP01 xo-server[431]: { Error: spawn fusermount ENOENT
Mar 25 06:07:51 BKP01 xo-server[431]:     at Process.ChildProcess._handle.onexit (internal/child_process.js:190:19)
Mar 25 06:07:51 BKP01 xo-server[431]:     at onErrorNT (internal/child_process.js:362:16)
Mar 25 06:07:51 BKP01 xo-server[431]:     at _combinedTickCallback (internal/process/next_tick.js:139:11)
Mar 25 06:07:51 BKP01 xo-server[431]:     at process._tickCallback (internal/process/next_tick.js:181:9)
Mar 25 06:07:51 BKP01 xo-server[431]:   errno: 'ENOENT',
Mar 25 06:07:51 BKP01 xo-server[431]:   code: 'ENOENT',
Mar 25 06:07:51 BKP01 xo-server[431]:   syscall: 'spawn fusermount',
Mar 25 06:07:51 BKP01 xo-server[431]:   path: 'fusermount',
Mar 25 06:07:51 BKP01 xo-server[431]:   spawnargs: [ '-uz', '/tmp/tmp-431yl3BiFVbSmWB' ],
Mar 25 06:07:51 BKP01 xo-server[431]:   originalMessage: 'spawn fusermount ENOENT',
Mar 25 06:07:51 BKP01 xo-server[431]:   command: 'fusermount -uz /tmp/tmp-431yl3BiFVbSmWB',
Mar 25 06:07:51 BKP01 xo-server[431]:   exitCode: undefined,
Mar 25 06:07:51 BKP01 xo-server[431]:   signal: undefined,
Mar 25 06:07:51 BKP01 xo-server[431]:   signalDescription: undefined,
Mar 25 06:07:51 BKP01 xo-server[431]:   stdout: '',
Mar 25 06:07:51 BKP01 xo-server[431]:   stderr: '',
Mar 25 06:07:51 BKP01 xo-server[431]:   failed: true,
Mar 25 06:07:51 BKP01 xo-server[431]:   timedOut: false,
Mar 25 06:07:51 BKP01 xo-server[431]:   isCanceled: false,
Mar 25 06:07:51 BKP01 xo-server[431]:   killed: false }
Mar 25 06:07:51 BKP01 xo-server[431]: 2020-03-24T20:07:51.178Z xo:api WARN admin@admin.net | backupNg.listFiles(...) [135ms] =!> Error: Command failed with exit code 32: mount --options=loop,ro,offset=608174080 --source=/tmp/tmp-431yl3BiFVbSmWB/vhdi15 --target=/tmp/tmp-431ieOQYw52Cr6a