Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
Changing the Log Level
There are four log levels available for each log file, with the default values and location of the relevant configuration
file listed in the table above.
file listed in the table above.
The available values are:
■
OFF
: Disables logging for the component.
■
WARN
: Only logs warnings and errors.
■
INFO
: Contains the same as WARN with additional, non-critical, log entries.
■
DEBUG
: This log level is very verbose, and should only be activated if instructed to do so by a Cisco support
representative. Debug logging is normally only used in advanced troubleshooting scenarios, and disabled as
soon as the troubleshooting session ends.
soon as the troubleshooting session ends.
To change the log level:
1.
.
2.
Create a backup copy of the configuration file before making any modifications to it.
3.
Open a text editor as an administrator.
4.
Open the configuration file in the text editor.
5.
Locate the
<log4net>
element, the
<root>
element within, and then the
<level>
element.
6.
Update the element with the desired value, for example from
<level value="WARN"/>
to
<level
value="DEBUG"/>
.
7.
8.
Save and close the file.
—
For all logs related to services, you must restart the relevant Windows service for the change to take effect.
—
For all IIS-based logs, the new log level takes effect immediately.
We strongly recommend reverting the log level back to its initial value after debugging, as increasing the log level
significantly increases the size of the log.
significantly increases the size of the log.
The steps to revert are the same as above.
Reading the Logs
The Cisco TMS version and the user account the component uses are logged every time the component starts.
Example log entries:
2013-06-19 20:14:29,108 [6] WARN Tandberg.TMS.Framework.AccessControl.AclService - Access denied to:
SystemRead
SystemRead
2013-06-20 14:53:04,503 [75] ERROR ASP.global_asax - System.Web.Services.Protocols.SoapException:
Unspecified Error
Unspecified Error
at Tandberg.TMS.External.SoapExceptionThrower.Throw(ExceptionContext exceptionContext)
at Tandberg.TMS.External.SoapExceptionThrower.Throw(Exception e, String actor)
at Tandberg.TMS.Global.Application_AuthenticateRequest(Object sender, EventArgs e)
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
The first log entry is from a log-web file. It is logged as a WARN (warning), and shows that a user tried to access a
page they do not have access to. The attempt was denied by the Access Control List mechanism of Cisco TMS, and a
corresponding log entry was created. In general, a WARN log entry is not critical and indicates no loss of data or
functionality.
page they do not have access to. The attempt was denied by the Access Control List mechanism of Cisco TMS, and a
corresponding log entry was created. In general, a WARN log entry is not critical and indicates no loss of data or
functionality.
The second log entry is from a log-web-external file. It is logged as an ERROR, and a full stack trace is displayed. In
general, an ERROR followed by a stack trace indicates that data or functionality has been lost. In this specific case,
the root cause of the ERROR is that a Cisco TMSBA client tried to create a new booking, but had syntactical errors in
general, an ERROR followed by a stack trace indicates that data or functionality has been lost. In this specific case,
the root cause of the ERROR is that a Cisco TMSBA client tried to create a new booking, but had syntactical errors in
288
Cisco TelePresence Management Suite Administrator Guide
Troubleshooting