Troubleshooting the Address Allocation Server

Networking Guide
Chapter 8, Configuring an Address Allocation Server (AAS)

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:

free up space
move the database directory elsewhere -- this requires shutting down the server
lower the maximum size so that the database will be compressed

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).

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.