[Date Prev][Date Next]
(ITS#3908) Assertion in ber_get_next
Full_Name: Preston A. Elder
Version: 2.3.4 (+ CVS-2005-07-21)
Submission from: (NULL) (184.108.40.206)
I've triggered yet another assertion.
I suppose I could be said to be using the HEAD as of 2005-07-21, though I'm
pretty sure this would still happen in an unpatched 2.3.4, since according to
the CVS archive, the file in question has not been modified in 6 months. The
file in question is libraries/liblber/io.c.
This error is coming courtacy of apache2 with mod_ldap_userdir, and I don't know
exactly how liblber is used, so I don't know how to reproduce it externally.
All I DO know is it happens infrequently, usually hours after the slapd and
apache servers have been started. And when it does happen, it stops ldap
working in apache, and I believe has farther reaching effects also (I've noticed
issues with mail, etc).
As mentioned in my previous bugs (#3853 and #3861), I'm using openldap with a
PostgreSQL backend. I can't see where to create my own login on this issue
tracking system, so I can't actually leave feedback on those issues, but as of
the head of 2005-07-21, both of those issues are resolved (which is why I went
to that head snapshot).
The error(s) coming from apache2 is:
apache2: io.c:501: ber_get_next: Assertion `ber->ber_buf == ((void *)0)' failed.
[Sun Jul 31 00:46:13 2005] [notice] child pid 29611 exit signal Aborted (6)
apache2: io.c:681: ber_get_next: Assertion `0' failed. [Sun Jul 31 01:27:04
2005] [notice] child pid 28334 exit signal Aborted (6)
apache2: io.c:681: ber_get_next: Assertion `0' failed. [Sun Jul 31 01:27:05
2005] [notice] child pid 30474 exit signal Aborted (6)
apache2: io.c:681: ber_get_next: Assertion `0' failed.
[Sun Jul 31 01:27:06 2005] [notice] child pid 30050 exit signal Aborted (6)
Its always triggering assertions on those two lines, 501 and 681 (681 more than
I can provide extra information on request, however snice its unpredictable when
this will happen, and the server I'm running this on is live, I can't just turn
up a general trace on the LDAP server, else my log would get very huge, very
quickly. Though I can turn up the log level a little, if you know which log
level would help most to diagnose this issue.
Also, please let me know how to register on here so I can leave followups.