Troubleshooting the Address Allocation Server
If the AAS is not giving out addresses, a diagnostic message will be written
to the syslog file.
The most likely problem is running out of space in the
filesystem where the transaction log is stored.
Solutions to this are:
A potential configuration problem may occur if the
maximum size is made smaller than the minimum amount
of space required to store the information for the addresses.
If this is the case, a
compression will be attempted every time a request is processed
(since the database will always be too large).
free up space
move the database directory elsewhere -- this requires shutting down the
lower the maximum size so that the database will be compressed
It is possible for the checkpoint area to fill up if it
is on the same filesystem as the database transaction log.
If a checkpoint file cannot be written due to space problems,
the server will issue a warning message but continue to run.
You can adjust the frequency of checkpointing and
the number of checkpoint files to help overcome this problem.
For more about AAS
Resetting the state of the AAS database
© 2007 The SCO Group, Inc. All rights reserved.
SCO OpenServer Release 6.0.0 -- 05 June 2007