A "socket" was not created for HTTP request before 300000ms

[arsenieciprian]

@Gheppy
what changes have u did ?

[Gheppy]

@arsenieciprian
For me, server 2 moves slower because it is busier and I opted to stop some virtual machines in such a way that I have almost the same transfer speed. I rebuilt XOCE from scratch with the latest version in two versions, one on debian 11.6 and the other on rocky linux 9, both behave the same.

Edit:
this is working with only one backup connexion (NFS share)

[arsenieciprian]

@Gheppy
is not about speed, i have in one datacenter some ancient servers and backups and restore are working well and speed is much slower than this one that give;s this error

[Gheppy]

@arsenieciprian
not the speed itself but the transfer speed, it must be about the same on all sources or destinations or the time difference should not exceed 5 minutes

Edit:
if you have a connection on the source to the first of 10000 and the second of 1000 and on the destination of 10000, you will more than likely have the error

[arsenieciprian]

@Gheppy
it does not have to be a problem speed transfer TCP must do his job and limit transfer between , what about if we transfer over internet , is not allways gigabit or 10 gb, i allready tested if this must be a reason

[Gheppy]

@arsenieciprian.
For me all backups are working now, except that one. And that I split it into 2 simple backups

[capeschools]

I am not sure this adds much to the discussion, but I am also experiencing this issue since the latest update a day or two ago.

xoa 5.80.0
xo-server 5.110.0

I have two hosts in a pool and a single backup location but some backups have completed (all under 5 minutes) and then others have failed at the 5 minute mark from both hosts - I was originally thinking maybe just one host but have success and failure form both to the same location.

[olivierlambert]

@capeschools as a XOA user, you should open a support ticket, this way we could access it remotely and investigate the issue directly there.

[capeschools]

@olivierlambert understood thanks!

[julien-f]

This should be fixed, please test and keep-me posted

https://github.com/vatesfr/xen-orchestra/commit/c71104db4ffabf70acb7e7f91f421fafebc9eaca

0 julien-f committed to vatesfr/xen-orchestra

fix(xo-web): don't add servers with empty httpProxy

Fixes #6656

Introduced by 2412f8b1e

This commit also contains a change in `xo-server` to properly handle servers in database that have this problematic entries.

[arsenieciprian]

@julien-f @olivierlambert

Yes it is working , finaly this issue is fixed.
Thank you

[julien-f]

Thank you all for your help on this!

[olivierlambert]

\o/

[Gheppy]

It is working for me to, thank you

[olivierlambert]

For those affected in XOA: a patch release will be done on latest next week. If you are in a hurry, open a support ticket, we can provide a patch locally

[EddieCh08666741]

@julien-f is there similar codes in restore function. The backup delta seems fixed but the restore showing the same error.

[julien-f]

@EddieCh08666741 The fix should impact both backup and restore, if you still have an issue, please try to reproduce in an official XO appliance and open a support tunnel, I'll investigate.

[arsenieciprian]

@julien-f @EddieCh08666741
For me it is working. I have tested with xoa and xo from sources and backups, restore backups, continuous replication and delta backups.

[EddieCh08666741]

Thanks wanted to write that my issues are all fixed after grabbing a fresh copy and rebuild.

[olivierlambert]

Great news! Thanks @julien-f for the difficult investigation (it was hard to catch) and obviously everyone who helped to report and provide feedback. That's how we build software: together!