Bug #10973
closed
When hooks are exiting with an error we can have stackoverflow error if there are many of them
Added by Nicolas CHARLES almost 7 years ago.
Updated about 5 years ago.
Category:
Web - Config management
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Description
I have an install with 1600 nodes
I had a stackoverflow error at generation - increasing Xss to 128m allowed me to circumvent the issue
The I got thousands of
stderr: '2017-06-21T18:21:55+0200 error: Can't stat file '/var/rudder/ncf//bin/sh: 0: Can't open /var/rudder/ncf/common/10_ncf_internals/list-compatible-inputs' for parsing. (stat: No such file or directory) ' ; Exit code=1 for hook: '/opt/rudder/etc/hooks.d/policy-generation-node-ready/10-cf-promise-check'. stdout: stderr: '2017-06-21T18:21:55+0200 error: Can't stat file '/var/rudder/ncf//bin/sh: 0: Can't open /var/rudder/ncf/common/10_ncf_internals/list-compatible-inputs' for parsing. (stat: No such file or directory) ' ; Exit code=1 for hook: '/opt/rudder/etc/hooks.d/policy-generation-node-ready/10-cf-promise-check'. stdout: stderr: '2017-06-21T18:21:55+0200 error: Can't stat file '/var/rudder/ncf//bin/sh: 0: Can't open /var/rudder/ncf/common/10_ncf_internals/list-compatible-inputs' for parsing. (stat: No such file or directory) ' ; Exit code=1 for hook: '/opt/rudder/etc/hooks.d/policy-generation-node-ready/10-cf-promise-check'.
as you can see, the nodeid is missing there
- Target version changed from 4.1.5 to 4.1.6
- Effort required set to Very Small
- Priority changed from 0 to 58
- Target version changed from 4.1.6 to 4.1.7
- Priority changed from 58 to 57
- Target version changed from 4.1.7 to 4.1.8
- Priority changed from 57 to 56
- Target version changed from 4.1.8 to 4.1.9
- Priority changed from 56 to 55
- Priority changed from 55 to 66
- Assignee set to François ARMAND
- Priority changed from 66 to 65
- Target version changed from 4.1.9 to 4.1.10
- Target version changed from 4.1.10 to 4.1.11
- Priority changed from 65 to 62
- Target version changed from 4.1.11 to 4.1.12
- Priority changed from 62 to 60
- Target version changed from 4.1.12 to 4.1.13
- Priority changed from 60 to 59
- Target version changed from 4.1.13 to 411
- Target version changed from 411 to 4.1.13
- Target version changed from 4.1.13 to 4.1.14
- Priority changed from 59 to 58
- Target version changed from 4.1.14 to 4.1.15
- Target version changed from 4.1.15 to 4.1.16
- Target version changed from 4.1.16 to 4.1.17
- Target version changed from 4.1.17 to 4.1.18
- Target version changed from 4.1.18 to 4.1.19
- Subject changed from When hooks are exiting an error, we don't get the node that is failing, and we can have stackoverfloww error if there are many of them to When hooks are exiting an error we can have stackoverfloww error if there are many of them
- User visibility changed from Infrequent - complex configurations | third party integrations to Operational - other Techniques | Rudder settings | Plugins
- Effort required changed from Very Small to Medium
- Priority changed from 58 to 29
I'm take that "very small" is to look at the real weight.
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/2112
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Status changed from Pending technical review to Pending release
- Subject changed from When hooks are exiting an error we can have stackoverfloww error if there are many of them to When hooks are exiting with an error we can have stackoverflow error if there are many of them
- Status changed from Pending release to Released
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by