Could you do "thread apply all bt", once you see this Segmentation
fault message?
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fe4a23e9710 (LWP 9557)]
0x7fe4d1fc601c in attrlist_find_or_create_locking_optional () from
/usr/lib64/dirsrv/libslapd.so.0
(gdb) t
sure.. i'll do that and rerun them..
On Wed, Sep 29, 2010 at 4:25 PM, Noriko Hosoi wrote:
> On 09/29/2010 12:49 PM, Rich Megginson wrote:
>
>> Gary Morris wrote:
>>
>>> ah.. sorry.. ok.. just retried with 1.2.6.1-1.. /
>>>
>>> [r...@dalp-ct02 logs]# rpm -qa | grep 389
>>> 389-dsgw-1.1.5-1.fc13.
On 09/29/2010 12:49 PM, Rich Megginson wrote:
Gary Morris wrote:
ah.. sorry.. ok.. just retried with 1.2.6.1-1.. /
[r...@dalp-ct02 logs]# rpm -qa | grep 389
389-dsgw-1.1.5-1.fc13.x86_64
389-admin-console-1.1.5-1.fc13.noarch
389-admin-1.1.11-1.fc13.x86_64
389-ds-base-1.2.6.1-1.fc13.x86_64
389-d
Gary Morris wrote:
>
> ok.. it pulled 389-ds-base-1.2.6-2.fc13.x86_64.. is that ok or do i
> need to be on 1.2.6-1? On 1.2.6-2 I'm having the same problem. As
> soon as I start an application that is ldap intensive, the directory
> server crashes real quick. No errors of any sort reported.
No
