AT_3649778.log is increasing gradually and impacting server

rickycrave · Post by **rickycrave** » 07 Aug 2009 10:23

Hello Friends,

We have recently upgraded Control-M agent to 6.3.01.400 level on one of the Host server(AIX server) and also Control module for SAP version to 6.3.01.100 level. Now once the jobs are allowed to submit on this server all are executing fine but at some period the jobs are getting failed saying that "Failed to save job information to file. check available disk space. For more information, see Agent diagnostics dump file in the proclog directory".

I have checked and found that the log AT_3649778.log is increasing gradually and making the proclog directory full and impacting other jobs/

Could any one suggest me regarding this.

Regards,
Ricky.

philmalmaison · Post by **philmalmaison** » 09 Aug 2009 2:52

first
look that your diag level is not too high for a normal situation.
second
do a job to periodically do some clean.
third
verify that a particulary job is not doing something wrong and anormally log tp proclog
fourth
verify taht a particular event managed by the agent is not doing something wrong and log in proclog
fives
ask to give some more space to your agent directorie if necessary

have fun

regards
philmalmaison

rickycrave · Post by **rickycrave** » 18 Aug 2009 11:36

Hi philmalmaison,

Thanks for your reply.

1. I have checked the diag level is set to 0.
2. Also increased the file system as per below error.

The jobs were getting failed due to the error "The disk free space is 38 MB while a minimum of 50 MB is required".

Now the agent is up and running fine.

But one more information I want...What are AT,AS,AM logs that are getting generated gradually in agent proclog directory. Is there any parameter to limit these logs?

Regards,
Ricky

philmalmaison · Post by **philmalmaison** » 18 Aug 2009 2:00

some things can be parametred by ctmagcfg
sapteus2% ctmagcfg

Agent Configuration Utility

1) Agent-to-Server Port Number . . . : [7007]
2) Server-to-Agent Port Number . . . : [7996]
For items 3 and 4 do not use IP address
3) Primary CONTROL-M/Server Host . . : [sapteus2]
4) Authorized CONTROL-M/Server Hosts : [sapteus2]
5) Diagnostic Level. . . . . . . . . : [0]
6) Comm Trace. . . . . .(0-OFF|1-ON) : [0]
7) Advanced parameters

s) Save and Restart CONTROL-M/Agent Services
q) Quit

Please enter your choice:7

Agent Configuration Utility - advanced menu

1) Days To Retain Log Files. . . . . : [7]
2) Daily Log File Enabled. . . (Y|N): [Y]
3) Tracker Event Port. . . . . . . . : [7997]
4) Logical Agent Name. . . . . . . . : [sapteus2]
5) Persistent Connection . . . . . . : [N]
6) Allow Comm Init. . . . . . . . . : [Y]
7) Foreign Language Support. . . . . : []

Locale (LATIN-1 mode only) . . .. : []
9) Protocol Version. . . . . . . . . : [07]
10) AutoEdit Inline. . . . . . . (Y|N): [N]
11) Listen to Network Interface . . . : [*ANY]
12) CTMS Address Mode . . . . . (IP|) : []
13) Timeout for Agent utilities . . . : [120]
14) TCP/IP Timeout. . . . . . . . . . : [120]
15) Tracker Polling Interval. . . . . : [120]

r) Return to main menu

otherwise you can use ctm_agcln utility to limit sysouts only

regards
philmalmaison

rickycrave · Post by **rickycrave** » 19 Aug 2009 10:54

Hi philmalmaison,

I have checked the ctmagcfg utility and all the parameters are set correctly at agent computer.

Also how to invoke this ctm_agcln utility to limit sysouts. I didn't found this utility in exe directory.

Could you please tell me.

Thanks,
Ricky

philmalmaison · Post by **philmalmaison** » 26 Aug 2009 1:47

#
# Traitement Sysout des agents
#
Lag=`ctm_agstat -LIST "*" | awk '{print $2}'`
for ag in ${Lag}
do
echo ${sep} >> ${fic_main}
echo "Agent : ${ag} retention : ${retain_sysout_ag} jours" >> ${fic_main}
ctmagcln -agent ${ag} -days ${retain_sysout_ag} >> ${fic_main}
echo "RC = `echo $?`" >> ${fic_main}
echo ${sep} >> ${fic_main}
done

usage:
ctmagcln -agent <agent_name> [ -days <sysout> ]

regards
philmalmaison

Ross_T_Boss · Post by **Ross_T_Boss** » 22 Feb 2010 5:00

Hi,

I thought I would update this thread as I had a very similar problem, and could not find the answer. But I think i have figured it out.

There were some 'dissapeared' extracted jobs after a SAP app instance went down, these failed when we rebooted and the agent was restarted. However, Control-M still has entries in the <agent>\CM\STATUS\ directory and <agent>\CM\PROCID for these jobs and attempts to track their status over and over in SAP. This generates the ctmat log at an alarming rate.

I have removed these files and restarted the agent, and now the problem has gone away. Hopefully this is solved, but does anyone know if this could have toehr side-effects or leave table entries that I need to clean up on the Server?