updater could not fetch data from xen-orchestra.com server (unexpected error 22). Please check your connection

MarkusRS

Hi,

I am new to XOA so I searched this forum but couldn't find anything in this regard.

I am trying the trial version of XOA which I registered yesterday.

In Registration area it states "registered to ...".

When trying to upgrade via the GUI I get this error message:

4/25/2023, 10:24:56 AM: Start updating...
4/25/2023, 10:24:57 AM: updater could not fetch data from xen-orchestra.com server (unexpected error 22). Please check your connection

regularly around every 10minutes.

When I ssh into the console:

[04:38 25] xoa@xoa:~$ xoa check
....
✔ Node version
✔ Memory
✔ xo-server config syntax
✔ Disk space for /
✔ Disk space for /var
✔ Native SMB support
✔ Fetching VM UUID
✔ xoa-support user
✔ XOA version
✔ Appliance registration
✔ NTP synchronization
✔ local SSH server
✔ npm version
✔ Internet connectivity
✖ XOA status: not up-to-date, please run xoa-updater

ping also works...

[04:39 25] xoa@xoa:~$ ping xen-orchestra.com
PING xen-orchestra.com(2a01:240:ab08::4 (2a01:240:ab08::4)) 56 data bytes
64 bytes from 2a01:240:ab08::4 (2a01:240:ab08::4): icmp_seq=1 ttl=57 time=43.2 ms
64 bytes from 2a01:240:ab08::4 (2a01:240:ab08::4): icmp_seq=2 ttl=57 time=41.4 ms

[04:46 25] xoa@xoa:~$ xoa-updater --upgrade

✖ {
  message: 'updater could not fetch data from xen-orchestra.com server (unexpected error 22). Please check your connection'
}

There is no firewall between xoa and the internet, just a router.

When I hover the mouse over the xoa upgrade icon it just turns into a red no entry sign.

I checked this page:
https://xen-orchestra.com/docs/updater.html
but couldn't find any more information.

I checked this page:
https://xen-orchestra.com/docs/general-troubleshooting.html

So I tried

tail -f /var/log/syslog

which gave me

*tail: cannot open '/var/log/syslog' for reading: Permission denied
tail: no files remaining*

Clicking on the "learn more" Link at
https://xen-orchestra.com/docs/general-troubleshooting.html redirected me to
https://xen-orchestra.com/docs/logs.html
which resulted in
"This xen-orchestra.com page can’t be foundNo webpage was found for the web address: https://xen-orchestra.com/docs/logs.html"

I guess I must be missing something very obvious....

Any ideas?

MarkusRS

Okay, sorry please ignore my post, after registering with a different user, the upgrade now worked fine. I think the error message before had to do with using a user which was not allowed for a trial. Perhaps one could state this in the error message, for example "Trial expired" or similar

I'll leave the post online if anybody else has a similar problem

MarkusRS

By the way, when I try to leave feedback via the

"Help us to improve this page! (opens new window)"

on this page

https://xen-orchestra.com/docs/general-troubleshooting.html

because I wanted to state that the tail command does not work and the hyperlink right beside it neither...

I was forwarded to a github page, where I first needed an account, which I then did because I wanted to help with the documentation, and then I got this error message on github:

You need to fork this repository to propose changes.

olivierlambert

You tried to register with a deleted account I think, causing the issue. Could it be possible? (we do not delete account automatically except if you ask us to do so)

MarkusRS

This post is deleted!

MarkusRS

@olivierlambert said in updater could not fetch data from xen-orchestra.com server (unexpected error 22). Please check your connection:

You tried to register with a deleted account I think, causing the issue. Could it be possible? (we do not delete account automatically except if you ask us to do so)

Ah, thank you, yes this is correct. I didn't remember deleting the account. And I was afraid that the 7 day trial period was too short for testing, so I used the old (deleted) accont. However strange that it accepted the old deleted account in the registration field, but I guess this is because the accound didn't really got deleted just de-activated, however then the registration should have failed I guess Thanks for clearing this up!

olivierlambert

Okay so you are right: we did not test this scenario, so that's why the error is cryptic. I'm adding @Enishowk in the loop so he can put that in our backlog