On 28/11/2011 11:37 πμ, Quanah Gibson-Mount wrote:
You've provided zero information on why they are freezing (i.e., a backtrace with debugging symbols enabled on the servers where slapd has "frozen").
Thanks Quanah,
Unfortunately, such error has not ever appeared until now, so I doubt I'll be able to reproduce, so as to create a backtrace. If, however, I manage to reproduce, I'll surely post the results. It's a production system, so testing is not so straightforward.
Error logging of the form: "Nov 23 23:12:04 dns2 kernel: slapd[2736] general protection rip:4b5342 rsp:43c54530 error:0" is practically useless?
Can I somehow run a (consumer) server in syncrepl debugging mode, in order to capture *in adequate detail* problems that MIGHT arise, despite a possible high debug logging volume (which would be manageable on a low-load box)?
Of course, I would suggest (attempting) to reproduce the issue with the latest version, as there were numerous fixes related to syncrepl & syncprov in 2.4.27/28. I personally would advise against mixing versions, also. Make all servers run the same OpenLDAP version.
Thanks, Nick