Solution : https://service.sap.com/sap/support/notes/1516577 (SAP Service marketplace login required)
Summary :
SAP has discussed IGS trace logs potentially growing large due to verbose logging at trace level 2 or higher, impacting the watchdog, multiplexer, and portwatcher files. A solution is offered by installing an IGS patch that enables log truncation features. You can set "igs/trace_logging" parameters for truncation, size in MB, and time interval checking in the instance profile for IGS 7.x, or through "TRACELOGGING" element in the igs.xml file for IGS 6.40. After the adjustment, oversized logs are renamed, and new events are logged thereafter. Ensure all parameters are value-set for functionality.
Key words :
prerequisites igs trace logs naturally increase, maximum file size limit, maximum set file size, symptom igs trace logs, xml configuration file, sp patch level, relevant igs patch, subsequent log events, log entry indicating, igs trace level
Related Notes :
| 946153 | Parameters of the IGS configuration file igs.xml |
| 896400 | Upgrade your integrated IGS 7.x installation |
| 844669 | Profile parameter of IGS as of Version 7.x |
| 793473 | Applying a patch for Windows standalone IGS |
| 718267 | Upgrade your integrated IGS 6.40 installation |