Installation guide

Accounting Problems
15-2
Problems with Accounting Log
Introduction
If you experience problems creating an Accounting log file, verify the following:
• The access server has enough memory to accommodate the LOG SIZE requirements of
the accounting component.
• The LOG SIZE specification is a valid value.
• The THRESHOLD specification is appropriate.
Verify the Log Size
To verify that the access server is storing Accounting events, enter the following
command:
Local> SHOW ACCOUNTING
Accounting Characteristics:
Threshold: None
Log Size: 128K
Console Logging: Disabled
If the Log Size is zero, Accounting events are not being stored. This can occur for two
reasons:
• Insufficient memory. If the defined Log Size is nonzero, the access server could not
allocate the requested memory during initialization. During initialization, the
accounting component is the last component to boot. If the remaining memory is
insufficient to accommodate the DEFINEd Log Size, there will be no accounting log
and the dynamic log size will be set to zero. Choose a smaller specification for Log Size
and reboot the access server with the following commands (substituting your desired
log size for 128):
Local> DEFINE ACCOUNTING LOGSIZE 128
Local> INITIALIZE
• DEFINED LOGSIZE 0: If the accounting log size is DEFINEd to zero (LIST
ACCOUNTING), the access server did not attempt to allocate an accounting log during
initialization. Enter the following commands (substituting your desired log size for
128):
Local> DEFINE ACCOUNTING LOGSIZE 128
Local> INITIALIZE