Enable The Access Gateway Monitor Service For The Core Dump Logic To Work Correctly; The Access Gateway Hangs When The Audit Server Comes Back Online - Novell ACCESS MANAGER 3.1 SP2 - ACCESS GATEWAY GUIDE 2010 Manual

Section 7.6.5, "Troubleshooting a Access Gateway Crash," on page 229
Section 7.6.6, "Access Gateway Not Responding," on page 233
Section 7.6.7, "Access Gateway Dumps Core After 10 Minutes When Non-Redirected Login Is
Enabled," on page 233
7.6.1 Enable the Access Gateway Monitor Service for the Core
Dump Logic to Work Correctly
When the Access Gateway monitor service is running in the Access Gateway appliance, it monitors
the available disk space in the
below 3GB, the Access Gateway prevents dumping core files.
In the Novell Access Manager 3.1 SP2 release, monitor service is disabled by default. To enable
this, execute the following command as:
/etc/init.d/lagmonitor start
For more information about this service, see
Monitor Service," on page
7.6.2 The Access Gateway Hangs When the Audit Server
Comes Back Online
When the Platform Agent loses its connection to the audit server, it enters caching mode. The default
size of the audit cache file is unlimited. This means that if the connection is broken for a long time
and traffic is high, the cache file can become quite large. When the connection to the audit server is
re-established, the Platform Agent becomes very busy while it tries to upload the cached events to
the audit server and still process new events. When coming out of caching mode, the Platform Agent
appears unresponsive because it is so busy and because it holds application threads that are logging
new events for a long period of time. If it holds too many threads, the system can appear to hang.
You can minimize the effects of this scenario by configuring two parameters in the
Parameters for the logevent File
Table 7-4
Parameter
LogMaxCacheSize
LogCacheLimitAction
When you set a finite cache file size, it limits the number of events that must be uploaded to the
audit server when caching mode is terminated and keeps the Platform Agent responsive to new audit
events that are registered.
228 Novell Access Manager 3.1 SP2 Access Gateway Guide
partition (/) before dumping core. When the disk space goes
root
Section 7.1.2, "Using the Linux Access Gateway
203.
Description
Sets a limit to the amount of cache the Platform Agent can consume to log
events when the audit server is unreachable. The default is Unlimited.
Specifies what the Platform Agent should do with incoming events when the
maximum cache size limit is reached. You can select one of the following
actions:
Delete the current cache file and start logging events in a new cache file.
Stop logging, which preserves all entries in the cache and stops the
collecting of new events.
file.
logevent