My three test systems seems to work properly when the management agent start type is set to delayed. So i think this can be a workaround for the moment.

@stormi indeed not free of irony

@olivierlambert

Hi, thanks for your reply.

To your questions:

1. XO Commit 3aa36f9
2. XCP-ng 8.2.1 LTS with latest updates (updated last saturday)

Regards

Hi All

I am just curious if i am the only one who is facing this.

I have an actual XenOrchestra which is build from the sources. Recently i've noticed, that i'm not able to download the systemlogs tgz file from Hosts -> Host -> Advanced Tab -> yellow button "Download system logs".

I have two Hosts in a pool, they both behave the same with any browser:

1. Download starts without estimation but at high speed
2. Some Megabytes are downloaded (~180MiB when trying on masterhost while 90MiB on slavehost)
3. Download speed suddenly stop an stuck at 0 for some minutes
4. Browser considered the download as failed
5. The file "logs.tgz" is corrupted an cannot be read.

With google search i did not found anything useful. Am i missing something or is there currently a problem with this feature?

Kind regards and have a nice day!

Hi,

I agree to this conclusion at this time.

Greetings

My three test systems seems to work properly when the management agent start type is set to delayed. So i think this can be a workaround for the moment.

@Greg_E
Hi Greg_E

Thanks for your detailed report and informations I will try it with delayed start. It could be a solution indeed. When i have news on this, i will share it here.

@archw
Hi, i thought the same today so i gave a try. But unfortunately at my test server fully patched with fresh ADDC on it there are the same issues present. But i have to say that i did not a detailed test at this time.

@archw

You should also notice that you cannot run any task scheduler tasks any longer. The task starts, but the action is not taken and after the timeout it end. Also any .msi package cannot be installed due to the Windows Installer Service is not able to start.

@Greg_E

Hi Greg_E

Yea, that are exactly the same findings as mine

I think to disable the Service could be a workaround for the moment. 9.4.0 did not make a difference compared to 9.3.0.

We will start our new project with 2025 with workaround in place and monitor the situation when a new version become available where the issue may have been fixed.

I'm glad for any further comment on this topic when new informations become available from any the community members or the devs

Have a nice evening!

@Greg_E

Hello Greg_E

I would be interested to know if you have had the opportunity to take a look at the problem I described? Were you able to reproduce the behavior?

The server has been released in the meantime (some may even have been accidentally updated to 2025 ) so the problem should soon become more noticeable among early adopters.