getaddrinfo EAI_AGAIN error during backup

Forza

Hello,

I just got the following error message. Have not seen something like that before. Is this a XOA or XCP-ng error? Looks like a temporary DNS resolution error?

srv02 is pool master. XOA is runnign on srv01. srv03+srv04 are NFS backup remotes.

XOA version:

- node: 14.16.0
- npm: 6.14.11
- xen-orchestra-upload-ova: 0.1.4
- xo-server: 5.77.0
- xo-server-auth-github-enterprise: 0.2.2
- xo-server-auth-google-enterprise: 0.2.2
- xo-server-auth-ldap-enterprise: 0.10.2
- xo-server-auth-saml-enterprise: 0.8.0
- xo-server-backup-reports-enterprise: 0.16.8
- xo-server-telemetry: 0.4.0
- xo-server-transport-email-enterprise: 0.5.0
- xo-server-transport-icinga2-enterprise: 0.1.1
- xo-server-transport-nagios-enterprise: 0.1.1
- xo-server-transport-slack-enterprise: 0.0.0
- xo-server-transport-xmpp-enterprise: 0.1.1
- xo-server-usage-report-enterprise: 0.9.0
- xo-server-xoa: 0.11.3
- xo-web-enterprise: 5.79.0
- xoa-cli: 0.25.1
- xoa-updater: 0.35.0

I did the XOA self check which seems to indicate some issue?

Danp

Do the following to address the latter issue --

Export your XOA config
Deploy a new XOA VM
Import your XOA config in new VM
Power down or remove the old XOA VM
Profit

Forza

@danp said in getaddrinfo EAI_AGAIN error during backup:

Do the following to address the latter issue --

Export your XOA config

Deploy a new XOA VM

Import your XOA config in new VM

Power down or remove the old XOA VM

Profit

Almost at least

Some things I've noticed.

After importing the old XOA config.json in the new XOA. I got no information about needing a reboot to get it to work. At first I actually thought the import failed and I re-did it.
XOA IP settings were not preserved.
XOA registration settings weren't preserved.

All in all it worked but with a bit of fiddling. Perhaps Vates team could streamline this process to make it clearer

And on topic, I only got that error once, and subsequent backups works as should. I am using the new XOA though. Any idea what can cause an error like that?

olivierlambert

Pinging @pdonias and/or @julien-f about the feedback.

XOA IP settings: that's normal and on purpose (if you still have your old XOA up, this will cause issues)
Registration: I'm not sure why it's not preserved

julien-f

Regarding the registration, it's not an XO setting per se, it's related to the updater instead.

It would probably be easy to implement though but we need to discuss the pros and the cons, especially security-wise.

Forza

IMHO it would be enough that the information about registration/proxy/updater and IP settings as well as the need to reboot XOA were printed on the page. It would be good to know that the json is not a complete backup before exporting.

Forza

I got the same error again today.

It's a delta job with two remotes.

Even though it says the backup failed, it looks like it is available on both remotes:

srv01 = pool member
srv02 = pool master
srv03, srv04 = backup remotes
XOA runs on srv02

The error seems to imply that it can't resolve the hostname of srv02, but that seems rather odd. I am using static IP only.