Environment
NetIQ Access Manager 3.2 Support Pack 1 Interim Release 1 applied
NetIQ Access Manager 3.2 Access Gateway Appliance or Service running
Email based alerting enabled on Access Gateway for all defined events
NetIQ Access Manager 3.2 Access Gateway Appliance or Service running
Email based alerting enabled on Access Gateway for all defined events
Situation
Access Manager setup and working fine - all users could access protected resources behind the Access Gateway after authenticating to the Identity Server. Auditing was enabled for all events on the Identity Server, but the Access Gateway used emails (via SNMP) for alerts for the various events that are triggered. The alerts were enabled via the AG
Devices > Access Gateways > Edit > Alerts > [Name of Profile]. In this setup, customer enabled alerts for following events:
System Up , System Down , Configuration Changed
When such an action occured, email were received without problems by the administrator. However, after applying the 3.2 SP1 IR1 patch, the same operations would not trigger any email updates to the administrator.
Looking at the ags_error.log under /var/opt/novell/nam/logs/mag/amlogging, we would see the following entry at the time the event occured:
<amLogEntry> 2013-02-08T10:39:47Z ERROR AGM: AM#204653001: AMDEVICEID#ag-68447E157B36F281: AgmAlertIndication: processIndication(), thread=1901, Exception Caught: java.lang.NoSuchMethodError: com.novell.nacm.logging.alert.AMAlertLog.email(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)V </amLogEntry> <amLogEntry> 2013-02-08T10:39:47Z ERROR AGM: AM#204653001: AMDEVICEID#ag-68447E157B36F281: AgmAlertIndication: java.lang.NoSuchMethodError: com.novell.nacm.logging.alert.AMAlertLog.email(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)V at com.novell.nacm.agm.AgmAlertIndication.processIndication(AgmAlertIndication.java:179) at com.novell.dcc.channel.RespondChannel$_B.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) </amLogEntry>
System Up , System Down , Configuration Changed
When such an action occured, email were received without problems by the administrator. However, after applying the 3.2 SP1 IR1 patch, the same operations would not trigger any email updates to the administrator.
Looking at the ags_error.log under /var/opt/novell/nam/logs/mag/amlogging, we would see the following entry at the time the event occured:
<amLogEntry> 2013-02-08T10:39:47Z ERROR AGM: AM#204653001: AMDEVICEID#ag-68447E157B36F281: AgmAlertIndication: processIndication(), thread=1901, Exception Caught: java.lang.NoSuchMethodError: com.novell.nacm.logging.alert.AMAlertLog.email(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)V </amLogEntry> <amLogEntry> 2013-02-08T10:39:47Z ERROR AGM: AM#204653001: AMDEVICEID#ag-68447E157B36F281: AgmAlertIndication: java.lang.NoSuchMethodError: com.novell.nacm.logging.alert.AMAlertLog.email(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)V at com.novell.nacm.agm.AgmAlertIndication.processIndication(AgmAlertIndication.java:179) at com.novell.dcc.channel.RespondChannel$_B.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) </amLogEntry>
Resolution
Apply 3.2 SP1 IR1a. The IR1 patch failed to include a jar file that had the required method in it to send emails.