It is currently 26 May 2017 11:57


Post new topic  Reply to topic  [ 2 posts ] 
Author Message
PostPosted: 29 Apr 2013 9:28 
Offline
Nouveau
Nouveau
User avatar

Joined: 29 Apr 2013 8:00
Posts: 4
Yesterday morning one of my agents seemed to hang, so I recycled it and everything appeared to recover.

However, since my new day procedure on the 27th at 12:00, it seems like this agent has somehow gone into debug mode. The proclog directory is filling up with AT_*.log files, including a DbCmContainer.log files which has grown to 8GB.

The contents of all of these log files look OK to my eyes, and I'm wondering if the agent may have stuck itself into Debug mode.

Agent 6.4.01.500 with 7.0.00.000 Control-M for Databases

How would I go about turning this off? My Sysadmins are having a cow with all of the disk space being used...

Thanks in advance!


Top
   
 Post subject:
PostPosted: 29 Apr 2013 10:37 
Offline
Nouveau
Nouveau
User avatar

Joined: 29 Apr 2013 8:00
Posts: 4
Just to answer my own question, yes, it did manage to get itself into Highest Debug mode over the weekend. I guess the agent just got bored.

Resetting the debug level back to 0 in the CCM has resolved the issue.


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 2 posts ] 

All times are UTC+10:00


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Limited
The site created by Franck YOT. Images, logo, content and trademarks about Control-M products are property of BMC Software.
All the comments are property of their posters. Images, logo, content and design are © copyright by Scheduler-Usage.com. All Rights Reserved