On 10/09/2017 05:20 PM, tdarby@xxxxxxxxxxxxxxxxx wrote: > I fixed the problem but the solution makes me concerned that this version of 389 server is not going to work for me. In short, I found that deleting a particular entry on both servers brought them back to life. This actually makes sense because they both died at exactly the same time, so I'm guessing this entry was updated on one, got replicated to the other and then they both crashed. At the time of this crash, what is typically happening to this entry is a lot of individual attribute value adds and deletes coming from multiple machines and processes. > > I've never seen anything bad happen on version 1.2 servers and, in fact, I had two 1.2 servers replicating with these 1.3.6 servers and both of them stayed up. This might be fixed in a newer version of 1.3.6, what version are you using now? rpm -qa | grep 389-ds-base > > So, what do I do now? CentOS won't let me go backwards. Should I go forward and use 1.3.7 instead? > _______________________________________________ > 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
