Document ID: 116205
Updated: Jul 01, 2013
Contributed by Goran Selthofer, Cisco TAC Engineer.
This document explains why log files are generated on the wrong server in a distributed deployment.
Why are log files generated on a local server instead of on a File server in a distributed deployment?
Engineering Special 3 (ES3) for Cisco Unified E-Mail Interaction Manager(EIM)/Cisco Unified Web Interaction Manager (WIM) Release 4.4.1 changed the default logging logic. This release does not create logs on the File server. Instead, it creates logs on the local servers in a distributed environment.
This behavior is due to the repair implemented for Cisco Bug ID CSCty30820. The Cisco Bug ID has a different title, "Application does not recover after network disconnect," than the title in the ES3 release notes, "Logging on local servers during network disruption."
Although this is the default logging logic with Release 9.0 and later, there is no explicit explanation that this changed in Release 4.4.1 ES3 in any of the customer documentation from Cisco. Because of the logging logic change, there should be appropriate changes in the log collection instructions in the Release 4.4 Troubleshooting Guide. This logging logic should also be clearly documented in the ES3 Release Notes, but it is not currently.
Therefore, realize that this is the expected behavior (logs produced separately on each server in a distributed deployment) when you search for log files from Release 4.4.1 ES3+ and Release 9.0+. Logs are produced on each server at this location <%INSTALL HOME%>\eService\Logs folder.
The Cisco Support Community is a forum for you to ask and answer questions, share suggestions, and collaborate with your peers.
Refer to Cisco Technical Tips Conventions for information on conventions used in this document.