IBM Support

Impact server and gui log files not being written

Troubleshooting


Problem

The files: impactserver.log, impactserver-errors.log, impactgui.log or impactgui-errors.log are not written to.

 

Symptom

The files may be seen to be not written to after an Impact fixpack update.

 

Cause

The existence of an 'old' entry in the impactserver.log4j.properties or impactgui.log4j.properties files, using an out of date syntax, for example:

log4j.appender.NETCOOL.file=/u01/log/netcool/system/impactserver.log

can cause the files: impactserver.log, impactserver-errors.log, impactgui.log or impactgui-errors.log not to be written to.

In this example the .properties files were also configured to write the logs to a non-default location (hence the unusual path above), which is a permitted customisation.  
 

Resolving The Problem

Remove the line(s) with the 'old' style syntax.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSB2GF","label":"Netcool\/Impact"},"ARM Category":[{"code":"a8m0z000000bqcVAAQ","label":"Impact"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.0.0;5.1.0;5.1.1;6.1.0;6.1.1;7.1.0"}]

Document Information

Modified date:
18 May 2026

UID

ibm17273291