Page 1 of 1

directory engine died on read

Posted: Fri Feb 09, 2007 5:25 am
by rudi
Hi, I have permanent this errors in SAC. The SAC also connect to three other servers (RES). The RES Service is available. When I open SAC theres this error message: "The Adminserver is not reachable".

2007-02-09 10:10:20,259 FATAL [RESService.doRequest:125] javax.naming.NamingException: [LDAP: error code 1 - [OM.LDAP 1000]:
directory engine died on read]
2007-02-09 10:10:20,260 FATAL [RESService.doRequest:126] javax.naming.NamingException: [LDAP: error code 1 - [OM.LDAP 1000]:
directory engine died on read]

2007-02-09 10:04:27,288 WARN [LDAPHelperUtils.extractAttributeValues:220] javax.naming.SizeLimitExceededException: [LDAP: error code 4 - Sizelimit Exceeded]; remaining name 'o=scalix'
2007-02-09 10:04:28,383 ERROR [GetMemberAccessGroupList.createSOAPResponseMessage:246]
2007-02-09 10:04:28,384 ERROR [GetMemberAccessGroupList.createSOAPResponseMessage:246]
2007-02-09 10:04:28,384 ERROR [GetMemberAccessGroupList.createSOAPResponseMessage:246]
2007-02-09 10:04:28,385 ERROR [GetMemberAccessGroupList.createSOAPResponseMessage:246]

Thanks for help!!!!!!

Posted: Fri Feb 09, 2007 5:35 am
by rudi
There is this message too:

2007-02-09 10:04:27,288 WARN [LDAPHelperUtils.extractAttributeValues:220] javax.naming.SizeLimitExceededException: [LDAP: error code 4 - Sizelimit Exceeded]; remaining name 'o=scalix'

Scalix Server 11.0.1, SLES9

Posted: Fri Feb 09, 2007 8:39 am
by rudi
This error is in /var/log/apache2/mod_jk.og:

[Fri Feb 09 12:52:46 2007] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/srv/www/logs/jk-runtime-status errno=2
[Fri Feb 09 12:52:46 2007] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/srv/www/logs/jk-runtime-status errno=2

Posted: Wed Feb 14, 2007 11:24 am
by dannyt
Hi,

Try omshowlog (or look at the fatal log file) on each Scalix server at around the time when this error occurs, there could be something logged by the LDAP server there which may provide more details of the root cause.

Regards,
Danny

Posted: Thu Feb 15, 2007 7:12 am
by rudi
Hi,

I have this errors on one server (note: the scalix server authenticated against a openLDAP Server):

SERIOUS ERROR LDAP Daemon (LDAP Engine ) Thu Feb 15 12:05:10 2007
[OM 10270] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 19655
Procedure trace follows:
<- nm_ParseORN
<- nm_AppendFieldMem
<- nm_PutFieldMem
-> nm_PutFieldMem
-> nm_AppendFieldMem
<- nm_AppendFieldMem
<- nm_PutFieldMem
-> nm_ParseORN
<- nm_ParseORN
<- ul_utUnpackUserEnt
-> ul_CloseUL
<- ul_CloseUL
-> cl_FormatMailNode
-> nm_ParseORN
<- nm_ParseORN
<- cl_FormatMailNode
Pid of logging process: 19655


SERIOUS ERROR LDAP Daemon (LDAP Engine ) Thu Feb 15 12:05:10 2007
[OM 10272] BACKTRACE:
/opt/scalix/lib/libom_er.so(er_add_backtrace+0xc6)[0x400d1366]
/opt/scalix/lib/libom_er.so[0x400d1665]
/opt/scalix/lib/libom_er.so(er_DumpProcAndExit+0x1f)[0x400d17ef]
[0xffffe420]
Pid of logging process: 19655

SERIOUS ERROR LDAP Daemon (LDAP Engine ) Thu Feb 15 12:05:11 2007
[OM 10270] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 19669
Procedure trace follows:
<- nm_ParseORN
<- nm_AppendFieldMem
<- nm_PutFieldMem
-> nm_PutFieldMem
-> nm_AppendFieldMem
<- nm_AppendFieldMem
<- nm_PutFieldMem
-> nm_ParseORN
<- nm_ParseORN
<- ul_utUnpackUserEnt
-> ul_CloseUL
<- ul_CloseUL
-> cl_FormatMailNode
-> nm_ParseORN
<- nm_ParseORN
<- cl_FormatMailNode
Pid of logging process: 19669


SERIOUS ERROR LDAP Daemon (LDAP Engine ) Thu Feb 15 12:05:11 2007
[OM 10272] BACKTRACE:
/opt/scalix/lib/libom_er.so(er_add_backtrace+0xc6)[0x400d1366]
/opt/scalix/lib/libom_er.so[0x400d1665]
/opt/scalix/lib/libom_er.so(er_DumpProcAndExit+0x1f)[0x400d17ef]
[0xffffe420]
Pid of logging process: 19669

Thanks for your help!!!!!!

Posted: Thu Feb 15, 2007 10:34 am
by dannyt
Hi,

The LDAP engine should not segv so that is a bug. However, there is not sufficient info in the trace to determine where the problem is. The only guess I have is that you mention using OpenLDAP to do authentication, so it is possible that the LDAP engine is calling the pam module to authenticate, and somewhere in pam the problem occurs. So pam config might be the next thing to look at but I don't know that area well.

Regards,
Danny