Bug #7821
closed
Unexpected reports on "Check jetty process" component of system techniques
Added by Jonathan CLARKE almost 9 years ago.
Updated over 8 years ago.
Category:
System techniques
Description
If jetty is restarted because one of the applications (endpoint or webapp) weren't reponding, we'll get a duplicate report for this component:
Files
|
1.png (11.6 KB)
1.png |
|
Jonathan CLARKE, 2016-01-21 23:22
|
|
- Related to Bug #7813: Reporting in server-components missing when restarting some services (ie jetty) added
The cause for this is that the bundle that detects an application is not responding (in server-roles/1.0/alive-check.st) calls a "generic" bundle named "generic_process_check_process" to force restart it, although this bundle is the one that provides reporting for the actual process checks.
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from Jonathan CLARKE to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/857
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.11.19, 3.0.14, 3.1.8 and 3.2.1 which were released today.
Also available in: Atom
PDF
Updated by Jonathan CLARKE 
Updated by