Agent gone into debug mode?
Posted: 29 Apr 2013 1:28
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!
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!