VDI_IO_ERROR Continuous Replication on clean install.

[EddieCh08666741]

@EddieCh08666741 Hope my above logs can help team to see if there's a bug in the script.

[EddieCh08666741]

I want to share my findings. I did a clean install XOCE on several distros ubuntu,debian and the 5mins restore still happens. I've tried both commits one with the requesttimeout=0 and the other requesttimeout=86xxxx running on node 18. I've installed XOA stable version which is running lower version of node runs perfectly fine always 100% on every restore.

[EddieCh08666741]

want to share that I fix this issue by upgrading NPM to latest stable version.

[olivierlambert]

Okay thanks for your feedback. Do you remember the previous npm version and what's your current one?

[EddieCh08666741]

seems i spoke too soon lol. Tested another VM and got this same 5mins A "socket" was not created for HTTP request before 300000ms

[arsenieciprian]

So. theare is a fix, i have this issue also, clean install

[nat]

I got the same error "Error: A "socket" was not created for HTTP request before 300000ms". My two XCP-ng hosts are 8.2.1 with a clean install & applied all patches. I still don't know how to fix it.

[arsenieciprian]

i tryed eveything
1 downgrade orchestra nodejs to v16 - same
2 reinstaled xcp-ng clean - same

[EddieCh08666741]

I've been testing with many variations all clean install from XO from sources all stopped at 5mins. installed 3-4 fresh copy. The only one which work consistently is the node 16 xoa stable version.

[arsenieciprian]

@EddieCh08666741
what branch in git ?

[EddieCh08666741]

@arsenieciprian the official supported XOA.

[BrunoMorais]

Hello,
I'm having the same issue in Delta Backups.
Opened here a topic here https://xcp-ng.org/forum/topic/7007/a-socket-was-not-created-for-http-request-before-300000ms

[yomono]

@BrunoMorais I had the same error yesterday, I rolled back to a previous commit and it started working again. I don't know the exact commit right now, sorry
(Note that this is not the same error as "vdi_io_error" and the cause it's probably also not the same)

[olivierlambert]

Are you sure you are on the latest commit on master and did a rebuild?

[olivierlambert]

We'll be happy to know if you can have the exact commit causing the issue, this will tremendously help

[EddieCh08666741]

@olivierlambert

I did another test on fresh new copy of debian 11. Install XOCE. And run some backup to test.

M packages/xo-server/config.toml
Your branch is up to date with 'origin/master'.

[olivierlambert]

@EddieCh08666741 we still have issues to reproduce the issue sadly. So we count on affected users to point to the commit where it started to fail

[EddieCh08666741]

@olivierlambert i'm doing the git bisect . Will update the commit which cause this issue from restore backup and CR issue.

[Tristis Oris]

a bit of necroposting.
Issue was fixed for me, not sure when. But now CR working with that storage, same config.

[olivierlambert]

Good to know it works now Thanks for the feedback!