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

Actions

Copy link

Bug #8178

closed

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

Added by Vincent MEMBRÉ about 8 years ago. Updated almost 8 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 ...

Actions

Copy link

Updated by Vincent MEMBRÉ about 8 years ago

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

Actions

Copy link

Updated by Vincent MEMBRÉ about 8 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)

Actions

Copy link

Updated by Jonathan CLARKE almost 8 years ago

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

Actions

Copy link

Updated by Jonathan CLARKE almost 8 years ago

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

Actions

Copy link

Updated by Jonathan CLARKE almost 8 years ago

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

Actions

Copy link

Updated by Jonathan CLARKE almost 8 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

PR https://github.com/Normation/rudder-techniques/pull/912

Actions

Copy link

Updated by Jonathan CLARKE almost 8 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.

Actions

Copy link