Novell ACCESS MANAGER 3.1 SP1 - GATEWAY GUIDE Manual page 131

Alert
Failure in Audit, Stopping
Services
Failure in Audit, Will lose events,
but continuing services
Failure in Audit, Server is offline
5 To send alerts to the Administration Console, select the Send to Device Manager check box.
6 To send alerts to a log file, click New in the Send to Log File section, specify a name for the log
profile, then click OK.
6a Configure the following Log File details:
Log File Name: Specify a name for the log file and a path where the file should be
stored.
Max File Size: Specify a maximum size in KB for the log file. The size can be from
50 to 100000 KB. Specify 0 to indicate that there is no maximum file size.
6b Click OK.
7 To enable e-mail notification click New in the Send Email Notifications section, specify a name
for the e-mail profile, then click OK.
7a Configure the following e-mail details:
E-mail Recipients: To add a recipient to the list, click New, specify the e-mail
address of the recipient, then click OK. You can add multiple e-mail addresses. To
delete a recipient, select the user's email address, click Delete, then click OK.
Description
Generated when the audit server has failed, and the Access
Gateway has been configured to stop services.
To configure the Access Gateway to continue when auditing
services are not available, click Auditing > Novell Auditing,
deselect the Stop Services on Audit Server Failure option, then
click Apply.
Generated when the audit agent has failed. The Access
Gateway continues to run, but no audit events are generated.
As a workaround while solving this problem, you can enable
proxy service logging (see
Service Logging," on page
files provide some details on the HTTP traffic.
If you do not want the Access Gateway to run without
generating events, you need to manually shut down the Access
Gateway.
Generated when the audit agent is unable to contact the audit
server. When this condition occurs, the audit agent uses local
caching for the audit events.
Do not allow this condition to continue indefinitely. The Access
Gateway soon reaches the limits of its local cache. If this
happens, events can be lost and the Access Gateway might
need to stop services.
For troubleshooting information, see
Audit" (http://www.novell.com/documentation/novellaudit20/
novellaudit20/data/al0lh30.html)
Administration Guide (http://www.novell.com/documentation/
novellaudit20/novellaudit20/data/bookinfo.html).
Section 4.2, "Configuring Proxy
110). The common and extended log
"Troubleshooting Novell
in the Novell Audit
Access Gateway Maintenance 131