@wahla Hello !

In XO you can search "power_state:halted", select all VMs, and start

If you want to do it automatically, I think you can script it with xe, but the best way is to understand why VM are shutting down or doesn't restart 🙂

Try with xe then.

@Andrew all that was okay. The proxy string was incorrect, now working. Thanks

If you want to login manually without any SSH key, you have to add a password for the account (passwd). Then you can log in with your Debian user with this password.

Updated to Master build, a66ae, xo-server 5.92.0, xo-web 5.96.0.
Consoles seem to work fine again.
thanks all!

@Danp I'll do some more digging on this once I have some time and see if I can find anything in the logs. I didn't have a chance to look yesterday when I was working on this.

It might be worth noting that I was trying to setup an S3 remote, not sure if it would happen with another one and maybe it has something to do with timing out (was trying to hook into Backblaze which doesn't seem to be working right either, works fine on all my other machines running TrueNAS and stuff but can't get it connected with XCP-ng, other S3 places like Wasabi and Amazon work fine though).

I'll update this thread with more info once I do some more testing, might have time this weekend but not sure yet, and this is in a production environment, so I do want to be careful about causing potential issues.

Click on "More details" to get it 🙂

Zstd is for XVA file format compression.

There's no compression on delta, because we need to merge them on destination, when retention is reached (inside the backup repository). So it doesn't really worth it (since you'll have to decompress them to do the merge).

Hello, mtill ! In this situation, you may try to recover the stored data on the RAM because, in your case, the data was overwritten in the RAM. The number of recovered files by this method depends on the RAM size, the size of files that was overwritten by this way and by the time running this process. I can suggest you use a specialized recovery service like raid recovery service to ensure that you will restore more data you can. I wish you a bit of good luck.

I agree, I don't think it's a technical limitation, just a use case not "covered" 🙂

The DNS cache has been merged, keep us posted if you have any issues. 🙂

@Darkbeldin Got ya, thanks!

If you do a backup with XO, then it's like you have all the snapshot saved in the backup repository.

Oh okay, it's a problem on restore.

Then there's something wrong on the backup chain. Any hint @julien-f ?

Feel free to ask for a feature request, as long it's well described in terms of the "what I need" functionally 🙂

@cyrus104 Hi,
No, there is no way to enable HA at XO level and it is on purpose. Enabling HA as to be taken very seriously, it can cause pool wide crippling issues so we considerer doing it through CLI and be aware of what you really do being mandatory.

That would be easier if you open a ticket so we can use our remote access tunnel to take a look 🙂

Have you saved the view you wanted to have? I'm not entirely sure to get it, what is the URL you have in your browser?

You would have to write a daemon, listing for webhooks, parse it, and then send it to Mattermost with the expected payload.

Wow, that's far from any hint on the error log 🤔

Nice catch then.