Hi Erwin,
I think the pstack is first step to diagnose what is going on. I
suspected a timeout because of the long etime (250s) that is close to a
5min timeout (ioblock, ssl timeout,...) but ATM there is no strong
evidence of this. timeout are not systematically reported in error logs
as it is normal networking event.
best regards
thierry
On 7/12/21 8:24 AM, Erwin Weitlaner wrote:
Thank you Thierry for your support.
So I will try to get the thread dump .. If the problem comes with a connection timeout from a (not listening) client, shoudn´t I see an error log entry somewhere? I searched for that for hours but no hints .. Maybe not the right idea but the problem came after our last linux patch, so if others have similar problems maybe a code change issue?
SG Erwin
_______________________________________________
389-devel mailing list -- 389-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________
389-devel mailing list -- 389-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
