Project

General

Profile

Actions
Copy link

Bug #18530

closed

We don't know which hook timeout when it happens

Added by François ARMAND about 4 years ago. Updated almost 4 years ago.

Status:
Released
Priority:
N/A
Assignee:
Nicolas CHARLES
Category:
Web - Config management
Target version:
6.1.7
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:

Description

So, we know that a hook timed out:

[2020-11-09 10:55:16+0100] ERROR policy.generation.manager - Error when updating policy, reason was: Error when executing hooks in directory '/opt/rudder/etc/hooks.d/policy-generation-finished'. <- Inconsistency: Hook ''/opt/rudder/etc/hooks.d/policy-generation-finished' with environment parameters: [[RUDDER_NODE_IDS:] [RUDDER_GENERATION_DATETIME:2020-11-09T09:55:09.633+01:00] [RUDDER_END_GENERATION_DATETIME:2020-11-09T09:55:16.078+01:00] [RUDDER_NODE_IDS_PATH:/var/rudder/policy-generation-info/last-updated-nodeids] [RUDDER_NUMBER_NODES_UPDATED:0] [RUDDER_ROOT_POLICY_SERVER_UPDATED:1]]' timed out after PT1H

We even have details about parameters leading to the timeout. But not WHICH hook timed out. So this is not actionnable and dumb.

Files

clipboard-202012021829-umzwf.png (31.9 KB) clipboard-202012021829-umzwf.png François ARMAND, 2020-12-02 18:29
Actions
Copy link

Also available in: Atom PDF