For some reason my subscriber callmanager server had a full disk. I found this file "C:\Program Files\Cisco\CallManagerAttendant\logs\ac_j.out.log" was the culprit and had reached 61Gb in size!
The file was currently in use and I couldn't find out what process had it open so I restarted the server and now it is back down to 0bytes. I just wanted to know what would cause that file to grow so large and how to prevent it.
DC directory service is Paused and no disk space is left on server
4.1(0.204) ccm subscriber with TCD service started. In this case, it seems like
the directory process was shutdown for an extended period of time. The file is
filled with the following exception:
"Exception in findAllUsersPaged: javax.naming.CommunicationException: Connection
reset [Root exception is java.net.SocketException: Connection reset]; remaining
restarting the TCD should truncate this file.
In this particular case the DC Directory service was stopped or paused which caused this log file to fill up with this exception error. We would have to look at the file to find out what exception error caused it to fill up. It could be the same or it could be a different exception.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...