Bug #16256
closed
Deadlock on compliance computing
Description
I generated policies, accepted nodes and the same time, and went to home page several time
after a while, compliance didn't show up...
running jstack show that a lot of thread are BLOCKED (see attachement)
Files
Updated by Nicolas CHARLES almost 5 years ago
I had a query 'idle in transaction' in postgresql: select nodeid, nodeconfigid, begindate, configuration from nodeconfigurations where enddate is null;
this was because of the load script
Updated by Nicolas CHARLES almost 5 years ago
There is also an issue on the policy generation: calling policy/regenerate every 30 minutes causes it to lock after first generation after midnight: every subsequent call results in
<title>502 Proxy Error</title> </head><body> <h1>Proxy Error</h1> <p>The proxy server received an invalid response from an upstream server.<br /> The proxy server could not handle the request <em><a href="/rudder/api/latest/system/regenerate/policies">POST /rudder/api/latest/system/regenerate/policies</a></em>.<p> Reason: <strong>Error reading from remote server</strong></p></p> </body></html>
compliance doesn't show up either
thread dump is attached
Updated by Nicolas CHARLES almost 5 years ago
- Related to Bug #16200: Missing timing info in compliance computation logs added
Updated by Nicolas CHARLES almost 5 years ago
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Updated by Nicolas CHARLES almost 5 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/2632
Updated by Nicolas CHARLES almost 5 years ago
this does have a negative impact on perfs, but make it works.
Updated by Nicolas CHARLES almost 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|84b17130ce0df8430acf1e0bf84bd7a4ecb90eb2.
Updated by Nicolas CHARLES almost 5 years ago
- Fix check changed from To do to Checked
tested, after 2 days of non stop regeneration and group update, there is no deadlock
Updated by Alexis Mousset almost 5 years ago
- Subject changed from Deadlock on compliance on Rudder 5.0 to Deadlock on compliance computing
- Name check changed from To do to Reviewed
Updated by Vincent MEMBRÉ almost 5 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.15 which was released today.