A "socket" was not created for HTTP request before 300000ms
-
@arsenieciprian is your restore working fine ?
-
@olivierlambert
When I get home (I have the same problem on my home lab and at work I don't have internet in the servers area), I can open a tunnel if you want. -
@Gheppy This will be probably helpful, I suppose you can have an XOA up to date with the issue, right?
-
I'm at commit b1e81d8 which Replication and delta works fine now. I'm trying to find the commit where restore starts working.
-
I've updated my node version.
$ node -v
v18.14.2I'm in commit 9fcd497c42805cd8b7fb936864a6dae9580677d2 and problem staus the same.
-
@EddieCh08666741 I restore a VM that is created with bc0afb589e96694fb30410cc5843ada6a866d995 and is ok
-
@olivierlambert
I have a XOCE but I will also try an XOA -
I wonder, could you test with Node latest, to see if it could be related to something in Node itself? (19.7 is the current one). Don't forget to rebuild everything.
-
@olivierlambert I'll do that
-
@Gheppy
i m doing now backup with bc0afb589e96694fb30410cc5843ada6a866d995 , i will try restore also i will try export. to see i f is working caz is afected export also -
@arsenieciprian
restore does not work
-
@arsenieciprian I reported this issue awhile back when restore is not working but backing up delta is working. Only recently there are more people reporting this issue during CR and Delta backups.
-
Same here with bc0afb589e96694fb30410cc5843ada6a866d995.
Backups are made but restore gives the same error. -
@BrunoMorais
on the other hand if i restore to other server it is working and machine starts ok -
@arsenieciprian Same behaviour here.
-
@arsenieciprian I can restore the VM to another server and then move it
-
@BrunoMorais
yee cool that is the purpose of backup -
Any feedback with a latest version of Node? Can you try @BrunoMorais @arsenieciprian and @EddieCh08666741 ?
-
@olivierlambert
v19 is not working also . i have tested last friday and theare is no difference -
Okay thanks
