Project

General

Profile

Actions
Copy link

Bug #8178

closed

Missing reporting in "check postgresql process" on rudder-db role

Bug #8178: Missing reporting in "check postgresql process" on rudder-db role

Added by Vincent MEMBRÉ over 10 years ago. Updated about 10 years ago.

Status:
Released
Priority:
N/A
Assignee:
Benoît PECCATTE
Category:
System techniques
Target version:
2.11.21
Pull Request:
https://github.com/Normation/rudder-t...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

I have a distributed setup and a missing report in my server-roles directive "Check postgresql process"

It may only be prduced on a root server ...

Updated by Vincent MEMBRÉ over 10 years ago Actions
Copy link
 #1

  • Project changed from 41 to Rudder
  • Category set to System techniques
  • Target version set to 2.11.21

I target 2.11, but i only reproduced it in 3.2

Updated by Vincent MEMBRÉ over 10 years ago Actions
Copy link
 #2

problem is that reporting in bundle agent "generic_process_check_process" is done only in root server (file techniques/system/server-roles/1.0/init-check.st)

Updated by Jonathan CLARKE about 10 years ago Actions
Copy link
 #3

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

Updated by Jonathan CLARKE about 10 years ago Actions
Copy link
 #4

  • Status changed from New to In progress
  • Assignee set to Jonathan CLARKE

Updated by Jonathan CLARKE about 10 years ago Actions
Copy link
 #5

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

Updated by Jonathan CLARKE about 10 years ago Actions
Copy link
 #6

  • Status changed from In progress to Pending technical review
  • Assignee changed from Jonathan CLARKE to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/912

Updated by Jonathan CLARKE about 10 years ago Actions
Copy link
 #7

OK, it took me a while to figure this one out. It seems that the logic for "should we check this process or not" is in two separate places: 1) in the init-check/service-check.st file, and once in the component-check.st file that calls out to the method in init-check/service-check.

They hadn't been updated synchronously, so in some cases, too much filtering didn't match up and reports could be missing on distributed installations.

Updated by Jonathan CLARKE about 10 years ago Actions
Copy link
 #8

  • Assignee changed from Nicolas CHARLES to Benoît PECCATTE

Updated by Jonathan CLARKE about 10 years ago Actions
Copy link
 #9

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

Updated by Vincent MEMBRÉ about 10 years ago Actions
Copy link
 #10

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.11.21, 3.0.16, 3.1.10 and 3.2.3 which were released on 2016-06-01, but not announced.

Actions
Copy link

Also available in: PDF Atom