111
xe host-param-set uuid=<xenserver_host_uuid> logging:syslog_destination=<hostname>
2. Issue the command:
xe host-syslog-reconfigure uuid=<xenserver_host_uuid>
to enforce the change. (You can also execute this command remotely by specifying the host parameter.)
XenCenter logs
XenCenter also has client-side log. This file includes a complete description of all operations and errors that occur
when using XenCenter. It also contains informational logging of events that provide you with an audit trail of
various actions that have occurred. The XenCenter log file is stored in your profile folder. If XenCenter is installed
on Windows XP, the path is
%userprofile%\AppData\Citrix\XenCenter\logs\XenCenter.log
If XenCenter is installed on Windows Vista, the path is
%userprofile%\AppData\Citrix\Roaming\XenCenter\logs\XenCenter.log
To quickly locate the XenCenter log files, for example, when you want to open or email the log file, click on View
Application Log Files in the XenCenter Help menu.
Troubleshooting connections between XenCenter and theXenServer host
If you have trouble connecting to the XenServer host with XenCenter, check the following:
• Is your XenCenter an older version than the XenServer host you are attempting to connect to?
The XenCenter application is backward-compatible and can communicate properly with older XenServer hosts,
but an older XenCenter cannot communicate properly with newer XenServer hosts.
To correct this issue, install a XenCenter version that is the same, or newer, than the XenServer host version.
• Is your license current?
You can see the expiration date for your License Key in the XenServer host General tab under the Licenses
section in XenCenter.
Also, if you upgraded your software from version 3.2.0 to the current version, you should also have received
and applied a new License file.
For details on licensing a host, see the chapter "XenServer Licensing" in the XenServer Installation Guide.
• The XenServer host talks to XenCenter using HTTPS over port 443 (a two-way connection for commands and
responses using the XenAPI), and 5900 for graphical VNC connections with paravirtual Linux VMs. If you have
a firewall enabled between the XenServer host and the machine running the client software, make sure that
it allows traffic from these ports.