Project

General

Profile

Bug #8178

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

Added by Vincent MEMBRÉ about 4 years ago. Updated almost 4 years ago.

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

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

#1

Updated by Vincent MEMBRÉ about 4 years ago

  • Project changed from ncf 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

#2

Updated by Vincent MEMBRÉ about 4 years ago

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)

#3

Updated by Jonathan CLARKE about 4 years ago

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

Updated by Jonathan CLARKE about 4 years ago

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

Updated by Jonathan CLARKE about 4 years ago

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

Updated by Jonathan CLARKE about 4 years ago

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

Updated by Jonathan CLARKE about 4 years ago

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.

#8

Updated by Jonathan CLARKE about 4 years ago

  • Assignee changed from Nicolas CHARLES to Benoît PECCATTE
#9

Updated by Jonathan CLARKE about 4 years ago

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

Updated by Vincent MEMBRÉ almost 4 years ago

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

Also available in: Atom PDF