Maintenance of log files.
sandrajones 270000NWW2 Visits (7788)
Maintenance of log files
When we ask for a pdcollect, one of the main areas collected is the logs directory.
Firstly a quick word about pdcollect:
If you have to just send logs instead ; make sure you send all the files in an invocation of the process.
We need the 01 logs as well as the latest one written to.
The <time> section as below is the same for each log in the invocation.
Now lets look at the logs directory itself.
1) The RAS1 logs,
These are the logs that rotate as default round 5 files before the 2-5 files are overwritten, the 01 file always being left.
They have the names such as
What we are looking for is a complete set of files per invocation.
The product does have controls over the maximum number of RAS1 files overall as well as the number per invocation and the location and is set in the config file.
Refer to this link to the Trouble shooting guide for all the detail:
This should give a good balance between keeping logs and filling up disk space. Let you system administrators know that ITM does monitor the files and that is the way to keep most under control.
However I have seen more than once that there has only been one or two files on the system and no *01.log. This has usually due to there being an automatic job that removes files over a certain age.
I even saw that I had a *05 and *02 where had it rotated round but no history of what had happened in between.
Saying that, also check with above link that the KBB_RAS1_LOG variable is set correctly in the config files.
We expect to see all logs for at least the latest invocation of the process.
in fact last months logs may be just taking up space, especially if traces were set but the issue is now solved.
2) Tracing on logs,
Depending on the tracing and activity these logs may be large and rotate frequently, or be smaller with fewer files in the sequence present.
One area to note is to remember to set tracing off again when it is not longer required.
If tracing is requested and there is no information about when to set traces back to ERROR - ask the engineer before the pmr is closed.
Note that if all ITM processes in the RAS1 command flow are at ITM v6.2.3 Fix Pack 2 (or higher), it is possible to set traces off and on via tacmd settrace
and there are other dynamic ways of doing most traces, and setting them off again.
See this video blog: http
A stop and start is not always needed to change trace settings.
On most systems there will be a number of kuiras1* logs in the directory, these are from tacmd commands.
Again the location, number of files in an invocation, the number of overall files are all controlled via the process.
However it is worth noting, that these are defined by the user id that runs them, so every user using tacmd commands has a separate limit.
Usually they are not large files but if there are a large number of tacmd commands run then they do build u, so it may be worth checkign on the number of files you have.
4) other logs
So it is worth letting your system administrators know that ITM does monitor the files and that is the way to keep most under control,
I have seen systems where there was a overall system cron job that deleted files based on age which as already stated causes delays when trying to debug issues.
Subscribe and follow us for all the latest information directly on your social feeds: