A "socket" was not created for HTTP request before 300000ms
-
I also have the same problem, with backup that take more that 5 min on the same server.
XOCE commit 24ac3ea37d0f4f8e35c2532d93ca13a0308aa4a3.
-
@Gheppy In my case it happens only in 1 of my servers. Does it happen in all your servers or just 1?
-
It should be similar . When the backup is within 5 mins it works. Currently I'm still facing this issue. I've opened a new issue in git. Hope they can fix it soon as I feel this is a key important feature.
-
I have an environment with 4 xcp-ng hosts
2x 7.6 version
2x 8.2.1 version
1x XOA version 5.109.0 backing up vms on smb remotes.Backups are running fine on 7.6 or 8.2.1 hosts.
My problem is occurring in restore.
I can't restore any vm that takes more than 5 min.
I always get the error:
A "socket" was not created for HTTP request before 300000msSo I decided to update xoa to the latest version, the situation got worse, the backup no longer works, giving the same error as the restore.
-
https://github.com/vatesfr/xen-orchestra/issues/6656
Submitted this issue. Hope it can be fixed soon.
closed Restore VM from Delta Backups stops at exactly 5mins #6656
-
@EddieCh08666741 thanks
-
@renatonog82 no problem I have this issue too since few weeks ago.
-
i have the same issue one server is working well, the backups are working great and the other one does not to backup, i have tried export and is the same at 5 minutes exact is stop, the only difference i have fownd betwen that 2 servers is hard drives in the one that works are hp and in the one that does not work is HGST,
my servers are hp dl360 g9 -
@arsenieciprian what is the duration of the successful backup?
-
@EddieCh08666741
on the one that works is more than 10-15 minutes, on the one that does not work is stops at exact 5 minutes -
@EddieCh08666741
On the server that stop's at 5 minutes i have hard drives HGST , i will try this days to replace hard drives, maybe is a hardware issue -
I have 3 Dell R710. All the Disks are the same. 2 Server working good and 1 server having the issue.
I'm going to pull the last commit on master and build again. -
Are those machine running in the same pool? (trying to identify the host configuration that could trigger the bug)
-
@olivierlambert
hi.
My machines are not in pool. are identical but are not in pool -
I'm not sure yet, but is the issue appearing during the backup or during the backup restore?
-
@olivierlambert
backup , restore and export -
for me problem start with commit ab96c549aee17c9ae3c4e78c43962700d11cbf8d
-
Okay, the same for others?
-
@Gheppy said in A "socket" was not created for HTTP request before 300000ms:
ab96c549aee17c9ae3c4e78c43962700d11cbf8d
I'm not surprised, but it's nice to have the confirmation, thanks
-
Bonus question: what's your Node version? (
node -v)
