APAR status
Closed as program error.
Error description
The IIS suite generates machine log files in the /tmp directory, this normal. Logs older that five days are suppose to be deleted, this is not happening. Settings are: LOGGING_INTERVAL=4 RUN_TIMEOUT=0 LOG_INCREMENT_INTERVAL=86400 CLEANUP_INTERVAL=432000 HANDLE_DIRECTORY=/tmp LOG_DIRECTORY=/tmp
Local fix
This fix is included in 8.0.1 fixpack 3
Problem summary
**************************************************************** USERS AFFECTED: The resource tracker files were not being rolled over or deletedand were overflowing available disk space on the server. **************************************************************** PROBLEM DESCRIPTION: The resource tracker was ignoring the setting in the restrac_settings file, so the logs grew without limit. **************************************************************** RECOMMENDATION: This change is included in 8.1 Fix Pack 1. ****************************************************************
Problem conclusion
The resource_tracker is controlled by a file located in PXEngine/etc named restrack_settings. The format is shown below: LOGGING_INTERVAL=4 RUN_TIMEOUT=0 LOG_INCREMENT_INTERVAL=86400 CLEANUP_INTERVAL=432000 HANDLE_DIRECTORY=/tmp LOG_DIRECTORY=/tmp Here the logging interval is 4 or every 4 seconds write to the active log. The log increment interval is 86400 seconds or every24 hours start a new log. The cleanup interval is set to 432000 seconds or every 5 days delete logs greater than 5 days old. Lastly, the handle and log directory is set to /tmp or where the pid and logs are written. In the /tmp directory there is another file which contains the activity of the resource_tracker named resource_tracker.8001.log. In this log, you can see how the log manager rolls over the log files after the defined time of 86400seconds or 24 hours and deletes log files older than 432000 seconds or 5 days. You can see the log roll-over in screen shotsyou provided as well. Below is a shot of a resource_tracker log file: ##IIIS-DSEE-TRES-0000310:05:37(000)Resource Tracker Log ##IIIS-DSEE-TRES-0000810:05:37(001)Opening log file: /tmp/machineLog.8001.hawkcewin01.20080508100536. ##IIIS-DSEE-TRES-0000910:05:37(000)Closing log file. ##IIIS-DSEE-TRES-0000810:05:37(001)Opening log file: /tmp/machineLog.8001.hawkcewin01.20080509100537. ##IIIS-DSEE-TRES-0001010:05:37(002)Removing old log: machineLog.8001.hawkcewin01.20080502061733. ##IIIS-DSEE-TRES-0001010:05:37(003)Removing old log: machineLog.8001.hawkcewin01.20080503061735. ##IIIS-DSEE-TRES-0001010:05:37(004)Removing old log: machineLog.8001.hawkcewin01.20080504061737. ##IIIS-DSEE-TRES-0000910:05:38(000)Closing log file. ##IIIS-DSEE-TRES-0000810:05:38(001)Opening log file: /tmp/machineLog.8001.hawkcewin01.20080510100538. ##IIIS-DSEE-TRES-0001010:05:38(002)Removing old log: machineLog.8001.hawkcewin01.20080505061739. ##IIIS-DSEE-TRES-0000910:05:42(000)Closing log file. ##IIIS-DSEE-TRES-0000810:05:42(001)Opening log file: /tmp/machineLog.8001.hawkcewin01.20080511100542. ##IIIS-DSEE-TRES-0001010:05:42(002)Removing old log: machineLog.8001.hawkcewin01.20080506061743. ##IIIS-DSEE-TRES-0000910:05:44(000)Closing log file. ##IIIS-DSEE-TRES-0000810:05:44(001)Opening log file: /tmp/machineLog.8001.hawkcewin01.20080512100544. ##IIIS-DSEE-TRES-0001010:05:44(002)Removing old log: machineLog.8001.hawkcewin01.20080506153849. ##IIIS-DSEE-TRES-0000910:05:45(000)Closing log file. ##IIIS-DSEE-TRES-0000810:05:45(001)Opening log file: /tmp/machineLog.8001.hawkcewin01.20080513100545. ##IIIS-DSEE-TRES-0001010:05:45(002)Removing old log: machineLog.8001.hawkcewin01.20080507142951. ##IIIS-DSEE-TRES-0001010:05:45(003)Removing old log: machineLog.8001.hawkcewin01.20080508100536. ##IIIS-DSEE-TRES-0000910:05:47(000)Closing log file. ##IIIS-DSEE-TRES-0000810:05:47(001)Opening log file: /tmp/machineLog.8001.hawkcewin01.20080514100547. ##IIIS-DSEE-TRES-0001010:05:47(002)Removing old log: machineLog.8001.hawkcewin01.20080509100537. ##IIIS-DSEE-TRES-0000910:05:50(000)Closing log file. ##IIIS-DSEE-TRES-0000810:05:50(001)Opening log file: /tmp/machineLog.8001.hawkcewin01.20080515100550. ##IIIS-DSEE-TRES-0001010:05:50(002)Removing old log: machineLog.8001.hawkcewin01.20080510100538. The resource_tracker is started by the same script that starts the JobMonApp. The script is located in the PXEngine/java directory and it is named jobmoninit. There is an environment variable that can be set to disable the resource_tracker from being started by the section leader and that variable is named APT_DISABLE_TRACKER_STARTUP. Define this environment variable insay the dsenv file if you want it global and set it's value to 1. APT_DISABLE_TRACKER_STARTUP When this is set, it ensures that the section leaders on each node will not make sure that a resource_tracker is running on the physical machine at startup. Typically this would add an additional fork + exec to section leader overhead. So, if APT_DISABLE_TRACKER_STARTUP is set, it won't start the resource_tracker. Bear in mind that if you want to use the resource estimation features of DataStage you will need to reenable the resource_tracker.
Temporary fix
Comments
APAR Information
APAR number
JR30452
Reported component name
WIS DATASTAGE
Reported component ID
5724Q36DS
Reported release
801
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-09-10
Closed date
2008-10-23
Last modified date
2010-12-09
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WIS DATASTAGE
Fixed component ID
5724Q36DS
Applicable component levels
R801 PSY
UP
R810 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"IBM InfoSphere DataStage"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
09 December 2010