Environment
NetIQ Access Manager 3.2
NetIQ Access Manager 3.2 IR1 applied where Identity server logging writes to the /var file system
NetIQ Access Manager 3.2 Access Gateway Appliance
NetIQ Access Manager 3.2 Access Gateway Service
NetIQ Access Manager 3.2 IR1 applied where Identity server logging writes to the /var file system
NetIQ Access Manager 3.2 Access Gateway Appliance
NetIQ Access Manager 3.2 Access Gateway Service
Situation
Access Manager setup and working fine. Users can access protected resources behind the Access Gateway (AG) after having authenticated to the Identity Server. After a week or so of operation, the Access Gateway no longer responded to queries from the browsers. Turns out that the AG had crashed but failed to restart automatically as there was no disk space available on the root file system.
The IDP logging had been enabled to verbose mode as part of the roleout, but had not been disabled since going live. With this level of logging enabled, the ESP on the AG was logging large volumes of data to the "/opt/novell/nesp/lib/webapp/WEB-INF/logs/" path causing the root file system to run out of space.
The IDP logging had been enabled to verbose mode as part of the roleout, but had not been disabled since going live. With this level of logging enabled, the ESP on the AG was logging large volumes of data to the "/opt/novell/nesp/lib/webapp/WEB-INF/logs/" path causing the root file system to run out of space.
Resolution
Add the following startup script to the Access Gateway so that the symbolic link to where the log files are written are changed to the /var/ file system path.
echo "---AG Log File Location Update Started---"
mv /opt/novell/nesp/lib/webapp/WEB-INF/logs/* /var/log/nesp
rm -Rf /opt/novell/nesp/lib/webapp/WEB-INF/logs
echo "---AG Log File Location Update Started---"
mv /opt/novell/nesp/lib/webapp/WEB-INF/logs/* /var/log/nesp
rm -Rf /opt/novell/nesp/lib/webapp/WEB-INF/logs
ln -s
/var/log/nesp
/opt/novell/nesp/lib/webapp/WEB-INF/logs
echo
"---AG Log File Location Update Completed---"
This is a workaround to an issue that will be fixed in 3. SP1.
This is a workaround to an issue that will be fixed in 3. SP1.