[Date Prev][Date Next]
Re: (ITS#3571) Syncrepl Provider Crash
>On Monday 28 February 2005 17:28, email@example.com wrote:
>>>Full_Name: Ralf Haferkamp
>>>Version: 2.2.23 (rel_eng 2.2)
>>>OS: SuSE Linux
>>>Submission from: (NULL) (220.127.116.11)
>>>When configured with a sessionlog the syncrepl provider crashes
>>>after an entry has been removed from the database and the consumer
>>>issues the next sync request.
>>>It crashes in the send_search_entry() call in
>>>slap_send_session_log() (sessionlog.c). The uploaded patch fixes
>>>this particular problem for me. It was made against the current
>>The 2.2 provider has more problems than just this.
>I realized that it has a significant memory leak and the current code in
>rel_eng 2.2 still crashes immediately on the first consumer request
>(2.2.23 still seems fine in this regard). Are this the kind for
>problems you are referring to? Or is it just completely broken?
>Unfortunately we have a few customers using syncrepl :(. So I might
>need to fix these issues.
There are a variety of modifications that the 2.2 provider doesn't
detect properly, and fails to send to refresh clients, among other
things. There are also a number of back-bdb instabilities due to the
provider code. I'd say it's mostly broken.
I am unable to cause a crash in this scenario. Please send your
slapd.conf (ACLs and syncrepl config are most relevant) as well as a
backtrace of the crash.
>>You should switch to the 2.3 provider as soon as practical.
>2.3 it not an option at the momemnt. But is it feasible to backport the
>the syncprov overlay from 2.3 to 2.2? If yes, I might go that way.
Extremely difficult, I think. And you must #if out all of the 2.2
provider from back-bdb to insure stability.
>>I will apply your patch, but realize that no more development effort
>>is going into the 2.2 provider.
>Thanks for the clarification.
-- Howard Chu
Chief Architect, Symas Corp. Director, Highland Sun
Symas: Premier OpenSource Development and Support