XO Team

Also, can you go into the directory of xo-server and show me the output of this command please:

> node -p '[require("./package").version, require("@xen-orchestra/cron/package").version]'

It would help if you could reproduce the issue with the official XOA, because we know the environment and how it was built.

Or give me a step by step process (with all the backup config) to reproduce the issue.

Cannot reproduce.

I've setup some tests, we should know more in a couple of hours.

@vapaa Can you show me the scheduling config of your job please?

This is strange, are you sure you are up to date?

You should be using at least xo-server 5.50.1 and its dependency @xen-orchestra/cron 1.0.4.

Just look at the hour of the datetime, the first one is 02:22, the second 03:22 and the last one 04:22

Sure! Make sure you're connected to XO with xo-cli and then:

$ xo-cli log.delete namespace=restore id=1570142063787

Hi @axiom00, it's not possible to clear the logs from the UI. We purposely removed the feature because the logs are very useful to investigate on a problem and they were too often deleted by mistake. Let us know what you think about this

> xo-cli --list-objects type=message \$object=<VM UUID>