A "socket" was not created for HTTP request before 300000ms
-
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
-
@olivierlambert
i have also checked bios settings , raid settings and everyhing is same , the only difference betwen the working server and non working server is Hard Drive producer, but i cannot blame hard disk caz they are working perfect and to write and to read. Honestley i do not know what to try anymore -
My case is the same. All Dell servers with same hardware. The disks are all Western Digital disks in all servers. They are just different models in the different servers. (Of course each server as same models).
Everything works good in 2 hosts only in host 3 I have these Issues.
-
@olivierlambert
commit 1fbe870884a426b35f762a77fd6f3bba6dfa75b0 with node 19.7 same problem.
On XOA I can't, I am on trial now. -
@olivierlambert I tested few weeks back with 19 not working too.
-
@olivierlambert
any news regarding this bug , -
@julien-f is currently investigating on it.
-
btw continuous replication is not working also
