- Print
- PDF
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 Skylight 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:
/opt/accedian/skylight/glassfish5/glassfish/nodes/bizn1/bizn1instance/logs/auditing_business.log
For more information, see Auditing User Actions and API Requests.
Backup Database Logs
The file is located in the following directory:
/opt/accedian/skylight/glassfish5/glassfish/nodes/bizn1/bizn1instance/logs/all.log
Other
- Logs related to the Session management and the interaction between the Supervision Endpoint
The file is located in the following directory:
/opt/accedian/skylight/glassfish5/glassfish/nodes/bizn1/bizn1instance/logs/sdmm.log
- Logs related to the interaction with the Devices
The file is located in the following directory:
/opt/accedian/skylight/glassfish5/glassfish/nodes/mednX/mednXinstance/logs/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:
/opt/accedian/skylight/logs/hamon.log
AppMon Logs
Writes a log of activity and error messages related to the AppMon.
You can find the log file that contains entries about the app_mon located in the following directory on the appliance:
/opt/accedian/appliance_monitor/logs/app_mon.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 Skylight orchestrator appliance:
/opt/accedian/log
Skylight orchestrator Services Logs
App_server Activity Logs
Writes a log of activity and error messages related to the app_server.
You can find the log file that contains entries about the app_server activities located in the following directory on the appliance:
/opt/accedian/skylight/logs/vision.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 Skylight orchestrator appliance:
/opt/accedian/skylight/logs/deploymenttool.log
MySQL Service Activity Logs
Writes a log of activity and error messages related to the MySQL service.
You can find the log file that contains entries about the mysql service activities located in the following directory on the appliance:
/opt/accedian/skylight/logs/mysql.log
Ubuntu OS Logs
You can find the log file that contains entries about Ubuntu OS located in the following directory:
- Authentication logs: /var/log/auth.log
- Kernel logs: /var/log/kern.log
- Syslog: /var/log/syslog
- Lists all installs, upgrades, removals and purges on the system: /var/log/dpkg.log
Managing Logs
When solving issues for clients, Accedian Technical Support may require the server log files produced by Skylight orchestrator. They will occasionally require logs that are finer-grained than the logs usually produced by Skylight 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
Log in to the Skylight orchestrator on port 22.
Connect to Glassfish as an administrator by entering:
cd /opt/accedian/skylight/glassfish5/bin
./asadmin --port=5048
The asadmin prompt is displayed.List the logging level of each module by entering:
list-log-levels bizcluster
list-log-levels medclusterChange 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.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
Log in to the Skylight orchestrator on port 22.
Connect to Glassfish as an administrator by entering:
cd /opt/accedian/skylight/glassfish/bin
./asadmin --port=5048
The asadmin prompt is displayed.Save the current log files and start new logs by entering:
rotate-log --target bizcluster
rotate-log --target medclusterTerminate 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 Skylight orchestrator modules. When the intervention on the appliance is finished, the logging levels should be changed back to their normal levels.
shoalLogger <CONFIG>
com.accedian.ems.bus.discovery.DiscoveryActionLogger <INFO>
com.accedian.ems.bus <INFO>
com.accedian.ems.ecf.server.request.MgmtRequestLogger <INFO>
com.accedian.ems <INFO>
com.accedian.ems.mediation <INFO>
com.accedian.ems.mediation.server.discovery.DiscoveryActionLogger <INFO>
com.accedian.ems.mediation.server.pm.logger.MediationPMActionLogger <INFO>
com.sun.enterprise.server.logging.GFFileHandler <ALL>
java.util.logging.ConsoleHandler <FINEST>
javax.enterprise.resource.corba <INFO>
javax.enterprise.resource.javamail <INFO>
javax.enterprise.resource.jdo <INFO>
javax.enterprise.resource.jms <INFO>
javax.enterprise.resource.jta <INFO>
javax.enterprise.resource.resourceadapter <INFO>
javax.enterprise.resource.sqltrace <FINE>
javax.enterprise.resource.webcontainer.jsf.application <INFO>
javax.enterprise.resource.webcontainer.jsf.config <INFO>
javax.enterprise.resource.webcontainer.jsf.context <INFO>
javax.enterprise.resource.webcontainer.jsf.facelets <INFO>
javax.enterprise.resource.webcontainer.jsf.lifecycle <INFO>
javax.enterprise.resource.webcontainer.jsf.managedbean <INFO>
javax.enterprise.resource.webcontainer.jsf.renderkit <INFO>
javax.enterprise.resource.webcontainer.jsf.resource <INFO>
javax.enterprise.resource.webcontainer.jsf.taglib <INFO>
javax.enterprise.resource.webcontainer.jsf.timing <INFO>
javax.enterprise.system.container.cmp <INFO>
javax.enterprise.system.container.ejb <INFO>
javax.enterprise.system.container.ejb.mdb <INFO>
javax.enterprise.system.container.web <INFO>
javax.enterprise.system.core.classloading <INFO>
javax.enterprise.system.core.config <INFO>
javax.enterprise.system.core <INFO>
javax.enterprise.system.core.naming <INFO>
javax.enterprise.system.core.security <INFO>
javax.enterprise.system.core.selfmanagement <INFO>
javax.enterprise.system.core.transaction <INFO>
javax.enterprise.system <INFO>
javax.enterprise.system.ssl.security <INFO>
javax.enterprise.system.tools.admin <INFO>
javax.enterprise.system.tools.backup <INFO>
javax.enterprise.system.tools.deployment <INFO>
javax.enterprise.system.util <INFO>
javax.enterprise.system.webservices.registry <INFO>
javax.enterprise.system.webservices.rpc <INFO>
javax.enterprise.system.webservices.saaj <INFO>
javax <INFO>
javax.org.glassfish.persistence <INFO>
org.apache.catalina <INFO>
org.apache.coyote <INFO>
org.apache.jasper <INFO>
org.apache <WARNING>
org.dozer <WARNING>
org.eclipse.persistence.session <INFO>
org.glassfish.admingui <INFO>
org.hibernate <WARNING>
org.jvnet.hk2.osgiadapter <INFO>
org.quartz <WARNING>
org.snmp4j <WARNING>
org.springframework <WARNING>
© 2024 Cisco and/or its affiliates. All rights reserved.
For more information about trademarks, please visit: Cisco trademarks
For more information about legal terms, please visit: Cisco legal terms
For legal information about Accedian Skylight products, please visit: Accedian legal terms and tradmarks