Gents,
After we have done the implementation of the standard Citrix security patch XS82E031, our log files in XenCenter suddenly shows errors with
1) check_xapi
2) check_slave_status
We went to Citrix first, why this was happing, just after implementing a Citrix security patch.
Their answer was:
The hotfix XS82E031 removes HTTP access to the management network static web page.
This web page can now only be accessed through HTTPS.
The alerts in XenCenter "HA lizard - check_xapi: Pool Host on Server: 161.89.92.182 not responding to HTTP - manual intervention may be required" probably means that HA Lizard is doing something that we no longer support, i.e. probing the HTTP landing page (probably to check the host is up).
Is this a known issue or is there a bypass known to this?
Looking forward to your comments
Hans
After we have done the implementation of the standard Citrix security patch XS82E031, our log files in XenCenter suddenly shows errors with
1) check_xapi
2) check_slave_status
We went to Citrix first, why this was happing, just after implementing a Citrix security patch.
Their answer was:
The hotfix XS82E031 removes HTTP access to the management network static web page.
This web page can now only be accessed through HTTPS.
The alerts in XenCenter "HA lizard - check_xapi: Pool Host on Server: 161.89.92.182 not responding to HTTP - manual intervention may be required" probably means that HA Lizard is doing something that we no longer support, i.e. probing the HTTP landing page (probably to check the host is up).
Is this a known issue or is there a bypass known to this?
Looking forward to your comments
Hans