Scheduling a repair operation with Novell iMonitor cores eDirectory

Novell eDirectory 8.8 SP1 and Novell eDirectory 8.8 SP2 servers on Linux core when a repair operation is scheduled using Novell iMonitor.

Note that the core happens when the repair operation is scheduled to run and not when pressing "Submit" or "OK" on the iMonitor page.

The current work around is to delete any scheduled repair options through iMonitor.

The core stack looks like the following:

# GDBCMDSTART bt

#0 0xb7ea3007 in DSUtilInit () from //opt/novell/eDirectory/lib/libsal.so.1
#1 0x00000000 in ?? ()




An additional core stack looks like the following:

(gdb) where
#0 0xb7dac1a7 in SAL_ModUnload () from //opt/novell/eDirectory/lib/libsal.so.1
#1 0xb7dacfb8 in SAL_ModLoad () from //opt/novell/eDirectory/lib/libsal.so.1
#2 0x08072f46 in LMLoadModule ()
#3 0xb168e0b5 in LoadDSRepair (pReq=0x95a4500, cmdline=@0xb0a3ee88)
at
/home/n4u_cm/ccm_wa/idc_n4u/ndsmon-idc_n4u-rosalind-SP2_beta/ndsmon/ndshtml/htmrepair.cpp:1050
#4 0xb168e940 in HtmlRepairPage (o_mgr=0xb0a3ff00, h_mgr=0xb0a3f1d8)
at
/home/n4u_cm/ccm_wa/idc_n4u/ndsmon-idc_n4u-rosalind-SP2_beta/ndsmon/ndshtml/htmrepair.cpp:1182
#5 0xb168f172 in HtmlRepairRightRequest (pReq=0x95a4500)
at
/home/n4u_cm/ccm_wa/idc_n4u/ndsmon-idc_n4u-rosalind-SP2_beta/ndsmon/ndshtml/htmrepair.cpp:1356
#6 0xb1709b53 in DSHttpDispatch (pReq=0x95a4500) at
/home/n4u_cm/ccm_wa/idc_n4u/ndsmon-idc_n4u-rosalind-SP2_beta/ndsmon/dshttp.cpp:1590
#7 0xb16c67f9 in DispatchReport (pScheduledReport=0x90bfc40)
at
/home/n4u_cm/ccm_wa/idc_n4u/ndsmon-idc_n4u-rosalind-SP2_beta/ndsmon/ndshtml/htmreport.cpp:4884
#8 0xb160edf0 in _ReportSched (pParm=0x0) at
/home/n4u_cm/ccm_wa/idc_n4u/ndsmon-idc_n4u-rosalind-SP2_beta/ndsmon/report.cpp:328
#9 0xb7daea24 in SAL_ThreadExit () from
//opt/novell/eDirectory/lib/libsal.so.1
#10 0xb7c6413b in start_thread () from /lib/libpthread.so.0
#11 0xb0a404a0 in ?? ()
#12 0xb0a404a0 in ?? ()
#13 0xb0a404a0 in ?? ()
#14 0xb0a404a0 in ?? ()
#15 0x00000000 in ?? ()