Just out of curiosity, how would you present something like "On monday, wednesday, friday, sunday, every other month at 4:30AM" or "Every day, every six hours, 15minutes past in january, march, june, september, december" in date format on that tiny space except showing the exact next scheduled time which doesn't tell anything really. Imo the cron time in that view is the best for quick overview. For those who want more details or don't understand cron time can do schedules without knowing anything about it from the edit view and also see the future scheduled execution times in date format.

Sure i get the idea for tasks that run every day at specific time, that'd be easy but as the examples above show, there can be quite complex cron schedules that would be difficult to show.

@olivierlambert said in Alerts in XO/XOA?:

it's in your dashboard view.

Do you mean the Alarms section? It is not showing anything for me. There is no log showing past events.

I don't think you can reset power state with XCP-ng Center 🤔

@olivierlambert

Thank you. I will do this - If I am successful - I will post it here 🙂

That's correct 🙂

Thanks for the feedback @Kajetan321 However, I have 0 idea on what it means and how it would work. Assistance will be welcome.

@shinuza got it, thanks. sad of course(

"ansible needs a stable unique id to identify hosts"
not realy, with manual host lists awx download new every time and remove old\chenged info.
same for netbox integration.

for most of task just enough tags like linux, db, etc.

@ppikna97 Np, I was also using template_file originally but as its now deprecated there have been no builds released for M1 based Mac (leading/forcing me down the templatefile function route).

It happens 🤷 No worries 🙂

@olivierlambert Thank you, I've changed the settings on b2 to "Keep all versions of the file (default)".

@olivierlambert Thank you 🙂

@theaeon No, that's a normal case and it's handled properly. The issue would be if one of the IPs has 2 IPs in the same field separated by a white space like: "x.x.x.x y.y.y.y", or if the field is just empty or anything else that doesn't look like a proper IP address.

If you want to check the addresses more thoroughly, you can install xo-cli with npm i -g xo-cli, log into your XO with xo-cli --register <XO-Server URL> <username> <password> and then run xo-cli --list-objects --addresses type=VM \$pool=<pool ID>.

@danp
Forgot to reply in time 😛

I updated to the latest version of XO (from sources).
Now everything imports fine.

You can close this thread if you want.

Weird… Can you remove the snapshot of the failing VM and try again to see if you still have the error?

To me it's like the delta capability on XCP-ng side is failing on a specific disk 🤔

@gskger said in create XO account from ssh:

I completely missed that in the troubleshooting documentation but it is already there - nice 👍

@olivierlambert said in create XO account from ssh:

As @gskger siad, this was already documented and visible by searching the term "recover" in the search bar 🙂

Uh 😊 - I tried a lot of other search terms, just not recover. Anyway - I'm back on track, thank you very much for all your help.

Nice one, thanks guys. 🙂

"It's complicated". The simple way is to copy your VHD to create a new one that will be unfragmented.

You set up your timezone, not your time sync. Please open a ticket we can assist to check if your virtual appliance is correctly synced 🙂

@andrewreid XO team has released a new version 5.66.2 for XOA and new sources for the XO community that should fix most of the recent backup issue, so please update to latest and report back if needed.