This is the 3rd time in as many weeks that my LDAP daemon aborts. I can easily re-start it using omon, but it usually picks sometime on the weekend to stop. :( I pulled the log and it says:
SERIOUS ERROR LDAP Daemon (LDAP Listner) 03.04.07 11:27:38
[OM 10270] Process about to terminate due to error
Signal (Segmentation Violation) trapped by process 24642
Procedure trace follows:
SERIOUS ERROR LDAP Daemon (LDAP Listner) 03.04.07 11:27:38
[OM 10272] BACKTRACE
/opt/scalix/lib/libom_er.so(er_add_backtrace+0xc6)[0x4001c366]
/opt/scalix/lib/libom_er.so[0x4001c665]
/opt/scalix/lib/libom_er.so(er_DumpProcAnsExit+0x1f)[0x4001c7ef]
[0xffffe420]
/lib/tls/libpthread.so.0[0x400bdc7]
/lib/tls/libc.so.6(_clone+0x5e)[0x4018321e]
Usually I can figure out where to look by reading the error log, but this one is way over my head.
Could this point to my maintenance script not working correctly to re-start downed daemons?
I am running 11.0.1 on a SLES9 server. Have downloaded 11.0.2 to install tomorrow AM. I hadn't had any problems with the LDAP daemon until after the 11.0.1 upgrade.
What is a signal segmentation? COuld this point to a "hiccup" in my communication line (DSL)? We have been having some line deterioation with the DSL line, but thought it had been fixed.
BTW is there a look-up table with common error numbers where I can look up errors?
I'm at a loss.
Thanks