Bug 314811
Summary: | Samba core dumps on startup | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Bojan Smojver <bojan> |
Component: | nss_ldap | Assignee: | Nalin Dahyabhai <nalin> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 5.0 | CC: | david_ragonese, dpal, jplans, vtsuryawanshi |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-06-30 00:00:28 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Bojan Smojver
2007-10-01 23:00:30 UTC
From the stack trace this seem an nss_ldap bug. Which versions of glibc and nss_ldap are installed? Are you seeing this repeatably, or did it just happen the one time? glibc-2.5-12 nss_ldap-253-3 It only happened once - last reboot for the new kernel. But, this box hasn't been up all that long, so this may not be indicative. BTW, this box points to itself for LDAP. It is running a replica of OpenLDAP database from another box. This exact error still occurs using the following recent builds, but instead while running ps -ef | grep running_process_name. It intermittently occurs every 10 minutes and NSCD is killed. - host1 – LINUX KERNEL v 2.6.18.53, NSS_LDAP Version 253-5 - host2 – LINUX KERNEL v 2.6.18.92, NSS_LDAP 253-17 ============================ Signal 6 (ABRT) caught by ps (procps version 3.2.7). Please send bug reports to <feedback.net> or <albert.net> ps: ../../../libraries/libldap/error.c:273: ldap_parse_result: Assertion `r != ((void *)0)' failed. Was the box configured with 'ssl start_tls'? This is the same error as #499302, though the backtrace is missing some symbols so I can't be sure it's the same. Unfortunately, I don't have access to this system any more, so I really cannot answer this question. I think we will close this since it is unclear if there is still an issue or not. If you come across this issue again please reopen the bug. (In reply to comment #7) > If you come across this issue again please reopen the bug. Check. |