Environment
Novell Access Management 3 Linux Access Gateway
Situation
In casesd where the Linux Access Gateway (LAG) fails to respond to
any requests, and the ics_dyn daemon does not appear to be running,
it may be that one of the LAG services has crashed. Looking at the
output of the /etc/init.d/novell-vmc status command will confirm
this ... check and see if any of the services are NOT in the
running state. If this is the case, there is most likely the need
to get a coredump.
You can enable the coredump option in LAG by doing the following:
1) In /etc/init.d/novell-vmc-chroot, uncomment the following line (line no 58)
#ulimit -c unlimited
2) Restart novell-vmc
/etc/init.d/novell-vmc restart
When the problem is duplicated e.g. by applying a change in the UI that appears to fail, look at the files under /chroot/lag. If there is a crash, LAG would have dumped the core as core.
You can send the coredump, config files ( /var/novell/cfgdb/vcdn/config.xml and /var/novell/cfgdb/.current/config.xml) and /var/log/ics_dyn.log to the technical support team in such events and they will diagnose the issue.
You can enable the coredump option in LAG by doing the following:
1) In /etc/init.d/novell-vmc-chroot, uncomment the following line (line no 58)
#ulimit -c unlimited
2) Restart novell-vmc
/etc/init.d/novell-vmc restart
When the problem is duplicated e.g. by applying a change in the UI that appears to fail, look at the files under /chroot/lag. If there is a crash, LAG would have dumped the core as core.
You can send the coredump, config files ( /var/novell/cfgdb/vcdn/config.xml and /var/novell/cfgdb/.current/config.xml) and /var/log/ics_dyn.log to the technical support team in such events and they will diagnose the issue.