This document describes an issue that has recently come to the attention of the Cisco Technical Assistance Center (TAC) where the Jetty logs in Unity Connection will fill the root partition. There has been some confusion about how Cisco bug ID CSCts98388 addresses the issue. The goal of this document is to explain what steps are required in order to address the issue. Additionally, it describes next steps.
Cisco recommends that you have knowledge of Cisco Unity Connection Versions 8.5.1, 8.6.2, and 9.x.
The information in this document is based on Cisco Unity Connection Versions 8.5.1, 8.6.2, and 9.x.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
You might recieve a notification in the logs or by Real-Time Monitoring Tool (RTMT) that Unity Connection disk space is low on the root partition. The problem in some cases is that the Jetty logs consume a large portion of space.
Cisco bug ID CSCts98388 has been filed in order to address this issue. However, there has been some confusion about how a patched version of software addresses the problem. The Solution section discusses how to resolve the problem.
Complete these steps in order to disable Logging.
Obtain a version of software for Unity Connection that has this defect patched. Once this version is loaded, you will have the commands available that were not there previously.
Note: It is important to understand that loading the patched version by itself does not prevent the issue.
Here are the commands for the Request Log:
set cuc jetty requestlog enable set cuc jetty requestlog disable
Here are the commands for the StdErr Log:
set cuc jetty stderrlog enable set cuc jetty stderrlog disable
Here are the commands for the Stdout Log:
set cuc jetty stdoutlog enable set cuc jetty stdoutlog disable
Enter these commands on both Publisher and Subscriber in order to prevent the log from continuing to fill the drives:
set cuc jetty requestlog disable
set cuc jetty stderrlog disable
set cuc jetty stdoutlog disable
Restart the Jetty service in order for the commands to take effect. Without a restart of the service, the logs continue to write and fill space.
Note: When an upgrade is completed, the Jetty logs are reenabled. So, after an upgrade is completed, you must enter the three commands listed in Step 2 in order to disable logging and restart the Jetty Service.
Clear Disk Space
Complete these steps in order to clear disk space.
Unfortunately, only the Stdout Log has a command to remove the logs via admin. The other two logs have to be removed via root. This section describes the commands so that you are aware of them. This document can be referenced when you open a TAC case.
Here is the path for the log: /usr/local/jetty/logs/*.request.log.
Here is the command to remove logs via the root:
rm -fv /usr/local/jetty/logs/2014*.log
Here is the path for the log: /var/log/active/jetty/*.stderrout.log.
Here is the command to remove logs via root:
This command deletes files that are older than five days:
rm -fv /var/log/active/jetty/2014*.log
Here is the path for the log: /var/log/active/jetty/*.stdout.log.
Here is the command to delete via the root:
rm -fv /var/log/active/jetty/2014*.log
Here is the command to delete via the admin:
file delete activelog /jetty/2014*.log noconfirm
The Business Unit will investigate an enhancement to the software where this logging is disabled by default.
Cisco bug ID CSCup13856 has been raised to address these points:
Set the default value of Jetty log tracing in order to disable.
The settings of the CLI enable/disable should persist over upgrade.
At this time, there is no specific date for its implementation.