File deployment logging

File deployment uses the RS EGO service running on the master host, and an rsdeploy agent that runs on each compute host.

The RS EGO service generates an rs.hostname.log file under /eservices/rs/log on the host on which the RS service runs. You can use the Platform Management Console to retrieve this Symphony log file.

The rsdeploy agent generates a cli.log file in the /eservice/rs/work directory on the compute host. You can use the Platform Management Console generic log retrieval feature to retrieve this log file.

The following is an example of a log file identifying a problem:

RSAuditlogger - 2007-10-02 17:56:45.325 Eastern Daylight Time CONFIG <Admin> PACKAGE <test> HOST <-> install failed - Domain <Application>: The specified resource ComputeHost has no hosts or was not found in the cluster. Ensure that the resource group exists in EGO and contains hosts.

Enable logging for the rsdeploy agent

Copy a log4j properties file called cli.log4j.properties to /eservice/rs/work on the target host.

This file shows errors relating to decompressing the file package and running the install script.

The following example is the resulting log when the winuninst.bat file was missing from the package:

CLI.dpl.download.RunTask - Domain <Application>: The command,  cmd /c cmd /c winuninst.bat , failed with the error, The system cannot find the file specifiedCLI.dpl.download.InstallModule - Domain <Application>: Failed to start the uninstall command,  cmd /c cmd /c winuninst.bat .