Hi, Latest update from customer. ---------------------------------------------------------------------------------------------------------------------------------------------------- >> This is something we expect RH to let us know. Is it related to deref ? What is the risk and impact of this change ? <<As this is a Bug, we will not be able to predict the behavior or what is causing it, which is why we involved our Developers. there is low to no risk of disabling deref. Ok, could you please point me to the RH documentation so we evaluate this suggestion ? - When the hang occurs, how long does it last. Could you collect 'top -H' at that time and get more frequent pstack >>There are several thread dumps attached to this case which are taken automatically and programmatically. <<We have reviewed the pstacks provided. The developers assisting on this case would like a pstack or series of 3 or 4 that happen at the time specified. Ok, I am adapting the temporary monitoring scripts and will soon provide new dumps. >>In regards to top -h, please let us know how to perform this programmatically. <<We do not provide scripts so, at best we could give you the command to run. Ok, it can be done with ( top -H -n 1 > top_output_$$.txt ). I will upload together with the above dumps. <<Could you confirm if the following attribute is set to 'nsslapd-db-deadlock-policy=6' ? Yes, it is still set to 6 since update on (Tue, Jun 16, 2020, 4:00:03 PM GMT+2). ----------------------------------------------------------------------------------------------------------------------------------------------------
Thank you taking your time and submitting this request for Red Hat Enterprise Linux 7. Red Hat Enterprise Linux 7 is in Maintenance Support 2 Phase. This bug was reevaluated and will be postponed to RHEL 8. Thank you for understanding. Red Hat Enterprise Linux Identity Management Team