Project

General

Profile

Actions

Bug #7821

closed

Unexpected reports on "Check jetty process" component of system techniques

Added by Jonathan CLARKE over 5 years ago. Updated about 5 years ago.

Status:
Released
Priority:
N/A
Category:
System techniques
Target version:
Severity:
User visibility:
Effort required:
Priority:

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 issues

Related to Rudder - Bug #7813: Reporting in server-components missing when restarting some services (ie jetty)ReleasedNicolas CHARLES2016-01-20Actions
Actions #1

Updated by Jonathan CLARKE over 5 years ago

  • Related to Bug #7813: Reporting in server-components missing when restarting some services (ie jetty) added
Actions #2

Updated by Jonathan CLARKE over 5 years ago

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.

Actions #3

Updated by Jonathan CLARKE over 5 years ago

  • Status changed from New to In progress
Actions #4

Updated by Jonathan CLARKE over 5 years ago

  • 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
Actions #5

Updated by Jonathan CLARKE over 5 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions #6

Updated by Vincent MEMBRÉ about 5 years ago

  • 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.

Actions

Also available in: Atom PDF