Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Subscriber ac_j.out.log file 61GB

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.

2 REPLIES
New Member

Re: Subscriber ac_j.out.log file 61GB

I think it's a memory issue.

Cisco Employee

Re: Subscriber ac_j.out.log file 61GB

Looks like you may have run into CSCef21927:

AC_J.out.log file size over 56GB on CM subscriber

Symptom:

DC directory service is Paused and no disk space is left on server

Condition:

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

name ''

Work Around:

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.

Kevin

121
Views
0
Helpful
2
Replies