Cannot write to log file. (NETIQKB54163)

  • 7754163
  • 02-Feb-2007
  • 17-Oct-2007

Resolution

fact
AppManager 5.0.x

fact
AppManager 5.x

fact
AppManager 6.0

fact
AppManager 6.0.x

fact
Red Hat Linux

fact
Sun Solaris

fact
SuSE Linux

fact
HP-UX

fact
FreeBSD

fact
IBM AIX

symptom
Cannot write to log file.

symptom
No error messages will be send to the debug log file for now, however it will be retried five minutes later.

cause
The partition storing your log files has run out of space.

fix

Make space available. The agent will attempt to append or recreate the log files every five minutes.

For example, imagine that an AMU agent is configured to save all its log files in /tmp/netiq/logs/.  Once you fill up the partition which holds the AMU agent log files (/tmp/netiq/logs/ in our example), your nqmlog.err will gain these two error messages:

Fri Aug 04 15:27:40 CDT 2006: Exception while trying to write into log file
Fri Aug 04 15:27:40 CDT 2006: No error messages will be send to the debug log file for now, however it will be retried 5 minutes later !!

This assumes there are at least enough bytes free on the disk to write that much.  Even if it cannot write those log messages, it does attempt to recreate the nqmlog files every five minutes.



note
For more information about how to change where the log files are stored, see NETIQKB53727: " How do I change where log files are stored?" https://www.netiq.com/kb/esupport/consumer/esupport.asp?id=NETIQKB53727.

Additional Information

Formerly known as NETIQKB54163