--- title: "Log File Management" slug: "log-file-management-for-orchestrator-docker" tags: ["Docker", "log files", "Audit Logs", "Legacy Orchestrator", "admin"] updated: 2026-06-01T17:46:06Z published: 2026-06-01T17:46:06Z canonical: "docs.crossworkassurance.cisco.com/log-file-management-for-orchestrator-docker" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.crossworkassurance.cisco.com/llms.txt > Use this file to discover all available pages before exploring further. # Log File Management ## Log File Locations ### Functional Logs #### Auditing Logs These are logs related to the actions performed by users in the web interface and as well as logs of requests made on the web services REST API. The following are examples of user actions that are registered in the log: - Successful login - Addition of a network element - Request for a manual resync of a network element. As an administrator, you may find it useful to view this log for various reasons. For example: - To investigate who accessed or tried to access the appliance - To troubleshoot issues a user is experiencing while using the appliance - To determine whether a user action was accomplished successfully - To determine which user made a change to any stored information, such as a Crosswork Assurance device configuration. **Note**: Only user actions and API requests are logged. Actions initiated by the system, by an automatic trigger, or by a resync are not logged. The log file is stored in the following directory: **${volume-location so-logs}/bizn1/bizn1instance/auditing_business.log** #### Backup Database Logs The file is located in the following directory: **${volume-location so-logs}/bizn1/bizn1instance/all.log** #### Other - Logs related to the Session management and the interaction between the Supervision Endpoint The file is located in the following directory: **${volume-location so-logs}/bizn1/bizn1instance/sdmm.log** - Logs related to the interaction with the Devices The file is located in the following directory: **${volume-location so-logs}/mednX/mednXinstance/all.log** Where **X** is a mediation number from 1-12 ### Redundancy Logs The redundancy feature writes a log of activity and error messages. The log file that contains entries about redundancy is located in the following directory on the appliance for the active site: **${volume-location so-logs}/hamon/hamon.log** ### CLI manager Logs Writes a log of activity and error messages related to the climanager. You can find the log file that contains entries about the climanager located in the following directory on the appliance: **/home/skylight/so/bin/logs/clibase.log** ### Upgrade Logs The upgrade feature writes a log of activity and error messages. You can find the log file that contains entries about the upgrade located in the following directory on the Legacy Orchestrator appliance: **/home/skylight/docker-dist.log** ### Deployment Profile Configuration Logs The deployment feature writes a log of activity and error messages. You can find the log file that contains entries about deployment located in the following directory on the Legacy Orchestrator appliance: **${volume-location so-logs}/skylight/deploymenttool.log** ## Managing Logs When solving issues for clients, Accedian Technical Support may require the server log files produced by Legacy Orchestrator. They will occasionally require logs that are finer-grained than the logs usually produced by Legacy Orchestrator. These are the log levels that are available (in order of increasing detail): - SEVERE - produces the fewest log entries - WARNING - INFO - CONFIG - FINE - FINER - FINEST - ALL - produces the most log entries. ### Changing the Log Level **To change the log files** 1. Open an SSH terminal session to the Legacy Orchestrator CLI on port 2200. 2. At the prompt, enter: **shell container core** You are brought to the appliance’s OS-level shell. 3. Connect to Glassfish as an administrator by entering: **cd /opt/accedian/skylight/glassfish5/bin ./asadmin --port=5048** The **asadmin** prompt is displayed. 4. List the logging level of each module by entering: **list-log-levels bizcluster list-log-levels medcluster** 5. Change the log level by entering commands similar to the following example (which sets the log level to FINE): **set-log-levels --target bizcluster com.accedian.ems.ecf.server.request.MgmtRequestLogger=FINE set-log-levels --target medcluster com.accedian.ems.ecf.server.request.MgmtRequestLogger=FINE** where: **com.accedian.ems.ecf.server.request.MgmtRequestLogger** is the logger module. 6. Terminate the admin session by entering: **quit** ### Rotating the Log Files It is possible to close the log files (server.log, all.log, thirdParty.log), mark them with the current time and start fresh logs. Rotating the log files in this way may be useful if you want to reduce the amount of data to inspect when performing system tests. In addition, starting new log files may be necessary when using finer log levels because they produce large files. **To rotate the log files** 1. Open an SSH terminal session to the Legacy Orchestrator CLI on port 2200. 2. At the prompt, enter: **shell container core** You are brought to the appliance’s OS-level shell. 3. Connect to Glassfish as an administrator by entering: **cd /opt/accedian/skylight/glassfish/bin ./asadmin --port=5048** The **asadmin** prompt is displayed. 4. Save the current log files and start new logs by entering: **rotate-log --target bizcluster rotate-log --target medcluster** 5. Terminate the asadmin session by entering: **quit** Old log files have been closed; file names now include a timestamp and new logs are created. ### Normal Log Levels This section lists the normal log levels for Legacy Orchestrator modules. When the intervention on the appliance is finished, the logging levels should be changed back to their normal levels. ``` shoalLogger com.accedian.ems.bus.discovery.DiscoveryActionLogger com.accedian.ems.bus com.accedian.ems.ecf.server.request.MgmtRequestLogger com.accedian.ems com.accedian.ems.mediation com.accedian.ems.mediation.server.discovery.DiscoveryActionLogger com.accedian.ems.mediation.server.pm.logger.MediationPMActionLogger com.sun.enterprise.server.logging.GFFileHandler java.util.logging.ConsoleHandler javax.enterprise.resource.corba javax.enterprise.resource.javamail javax.enterprise.resource.jdo javax.enterprise.resource.jms javax.enterprise.resource.jta javax.enterprise.resource.resourceadapter javax.enterprise.resource.sqltrace javax.enterprise.resource.webcontainer.jsf.application javax.enterprise.resource.webcontainer.jsf.config javax.enterprise.resource.webcontainer.jsf.context javax.enterprise.resource.webcontainer.jsf.facelets javax.enterprise.resource.webcontainer.jsf.lifecycle javax.enterprise.resource.webcontainer.jsf.managedbean javax.enterprise.resource.webcontainer.jsf.renderkit javax.enterprise.resource.webcontainer.jsf.resource javax.enterprise.resource.webcontainer.jsf.taglib javax.enterprise.resource.webcontainer.jsf.timing javax.enterprise.system.container.cmp javax.enterprise.system.container.ejb javax.enterprise.system.container.ejb.mdb javax.enterprise.system.container.web javax.enterprise.system.core.classloading javax.enterprise.system.core.config javax.enterprise.system.core javax.enterprise.system.core.naming javax.enterprise.system.core.security javax.enterprise.system.core.selfmanagement javax.enterprise.system.core.transaction javax.enterprise.system javax.enterprise.system.ssl.security javax.enterprise.system.tools.admin javax.enterprise.system.tools.backup javax.enterprise.system.tools.deployment javax.enterprise.system.util javax.enterprise.system.webservices.registry javax.enterprise.system.webservices.rpc javax.enterprise.system.webservices.saaj javax javax.org.glassfish.persistence org.apache.catalina org.apache.coyote org.apache.jasper org.apache org.dozer org.eclipse.persistence.session org.glassfish.admingui org.hibernate org.jvnet.hk2.osgiadapter org.quartz org.snmp4j org.springframework ``` **© 2026 Cisco and/or its affiliates. All rights reserved.** For more information about trademarks, please visit: [Cisco trademarks](https://www.cisco.com/c/en/us/about/legal/trademarks.html)[](https://www.cisco.com/c/en/us/about/legal/trademarks.html) For more information about legal terms, please visit: [Cisco legal terms](https://www.cisco.com/c/en/us/about/legal/terms-conditions.html)