VDI_IO_ERROR Continuous Replication on clean install.
-
I did quite a number of test and these are all fresh install and the codes for node js fix is there. I'm using the restore function to local SR ( ext4 ) Is there some other codes that needs to be updated ? Anyone have similar issue ?
-
@EddieCh08666741 Hope my above logs can help team to see if there's a bug in the script.
-
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.
-
want to share that I fix this issue by upgrading NPM to latest stable version.
-
Okay thanks for your feedback. Do you remember the previous npm version and what's your current one?
-
seems i spoke too soon lol. Tested another VM and got this same 5mins A "socket" was not created for HTTP request before 300000ms
-
So. theare is a fix, i have this issue also, clean install
-
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.
-
i tryed eveything
1 downgrade orchestra nodejs to v16 - same
2 reinstaled xcp-ng clean - same
-
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.
-
@EddieCh08666741
what branch in git ? -
@arsenieciprian the official supported XOA.
-
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 -
@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) -
Are you sure you are on the latest commit on
masterand did a rebuild? -
We'll be happy to know if you can have the exact commit causing the issue, this will tremendously help
-
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'.
-
@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
-
@olivierlambert i'm doing the git bisect . Will update the commit which cause this issue from restore backup and CR issue.
-
a bit of necroposting.
Issue was fixed for me, not sure when. But now CR working with that storage, same config. -
O olivierlambert marked this topic as a question on
-
O olivierlambert has marked this topic as solved on
