Page 1 of 1

SERIOUS ERROR LDAP Daemon

Posted: Wed Apr 04, 2007 1:41 am
by lcastellanos
ldap gave this error and died:

SERIOUS ERROR LDAP Daemon (LDAP Listener ) 04.03.07
05:24:28
[OM 10270] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 2457 Procedure trace follows:


SERIOUS ERROR LDAP Daemon (LDAP Listener ) 04.03.07
05:24:28
[OM 10272] BACKTRACE:
/opt/scalix/lib/libom_er.so(er_add_backtrace+0xc6)[0x20bee6]
/opt/scalix/lib/libom_er.so[0x20c1e6]
/opt/scalix/lib/libom_er.so(er_DumpProcAndExit+0x1f)[0x20c38f]
/lib/tls/libpthread.so.0[0x40c898]
/lib/tls/libpthread.so.0[0x406371]
/lib/tls/libc.so.6(__clone+0x5e)[0x370ffe]

any idea how to prevent this from happening again?

Posted: Wed Apr 04, 2007 9:14 am
by ScalixSupport
Hi!

Can you tell us what you tried which resulted in this error? If you could provide the
procedure trace it could benefit towards problem resolution.

Thanks,
Subir

Posted: Wed Apr 04, 2007 10:41 am
by lcastellanos
It was in the middle of the night nothing specific was happening It just died on its own.

How do I retrieve the procedure trace?

For now I've created a simple script in case someone is having the same issues:

#!/bin/bash
output=`/etc/init.d/ldapmapper status|grep running > /dev/null;echo $?`;
output1=`/opt/scalix/bin/omstat -a |grep LDAP|awk '{print $3}'`;

if [ "$output" \!= "0" ];
then /etc/init.d/ldapmapper restart > /dev/null;
fi

if [ "$output1" \!= "Started" ];
then /opt/scalix/bin/omon -w ldap > /dev/null;
fi

I put it in /usr/local/sbin/ldapcheck.sh with the following entry in cron:

*/5 * * * * /usr/local/sbin/ldapcheck.sh

Posted: Wed Apr 04, 2007 12:33 pm
by ScalixSupport
Hi!

I wanted the procedure trace that you removed in your first post:
SERIOUS ERROR LDAP Daemon (LDAP Listener ) 04.03.07
05:24:28
[OM 10270] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 2457 Procedure trace follows:


Thanks,
Subir

Posted: Wed Apr 04, 2007 2:19 pm
by lcastellanos
What I pasted is all that was available from omshowlog. There was no Procedure trace.

Here is the entire ouput from omshowlog -s ldap

omshowlog -s ldap

SERIOUS ERROR LDAP Daemon (LDAP Listener ) 04.03.07 05:24:28
[OM 10270] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 2457
Procedure trace follows:


SERIOUS ERROR LDAP Daemon (LDAP Listener ) 04.03.07 05:24:28
[OM 10272] BACKTRACE:
/opt/scalix/lib/libom_er.so(er_add_backtrace+0xc6)[0x20bee6]
/opt/scalix/lib/libom_er.so[0x20c1e6]
/opt/scalix/lib/libom_er.so(er_DumpProcAndExit+0x1f)[0x20c38f]
/lib/tls/libpthread.so.0[0x40c898]
/lib/tls/libpthread.so.0[0x406371]
/lib/tls/libc.so.6(__clone+0x5e)[0x370ffe]


SERIOUS ERROR LDAP Daemon (LDAP Listener ) 04.04.07 08:19:01
[OM 10270] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 26237
Procedure trace follows:


SERIOUS ERROR LDAP Daemon (LDAP Listener ) 04.04.07 08:19:01
[OM 10272] BACKTRACE:
/opt/scalix/lib/libom_er.so(er_add_backtrace+0xc6)[0x2c1ee6]
/opt/scalix/lib/libom_er.so[0x2c21e6]
/opt/scalix/lib/libom_er.so(er_DumpProcAndExit+0x1f)[0x2c238f]
/lib/tls/libpthread.so.0[0x40c898]
/lib/tls/libpthread.so.0[0x406371]
/lib/tls/libc.so.6(__clone+0x5e)[0x22bffe]

Posted: Thu Apr 05, 2007 1:26 am
by ScalixSupport
Hi!

What Scalix version you are using? We have a known bug for the same
http://bugzilla.scalix.com/show_bug.cgi?id=13185

Thanks,
Subir

Posted: Thu Apr 05, 2007 9:54 am
by lcastellanos
This started happening after an upgrade from 10 to 11.0.2.1 looks like that bug should be fixed on that version.

Posted: Fri Apr 06, 2007 3:20 am
by ScalixSupport
Have a look at post:
viewtopic.php?p=31284#31284

Try performing the steps mentioned in the above post, please reply what result you see
are these LDAP errors gone.

Thanks,
Subir