Bug #9182
closed
Multiple errors "The postgresql process was not running and has been restarted"
Added by Alexandre Anriot over 7 years ago.
Updated almost 2 years ago.
Category:
System techniques
Description
Alexis,
As seen on IRC, we have spotted that Rudder checks that its PostgreSQL instance is running through the process list, looking for the postgres: writer process pattern.
(ref: /var/rudder/cfengine-community/inputs/server-roles/1.0/component-check.cf)
But on Debian 8.5 with PostgreSQL 9.5, the writer process appears as postgres: 9.5/main: writer process.
Thanks.
- Category set to System techniques
- Target version set to 3.1.15
Jessie repositories contain PostgreSQL 9.4, are you using a package from backports or an external repo?
Hello,
For the record, I have upgraded the Pg cluster to 9.6 and I'm now using:
"service[rudder_reports][binary]" string => "postgres:.*writer process";
- Target version changed from 3.1.15 to 3.1.16
- Target version changed from 3.1.16 to 3.1.17
- Translation missing: en.field_tag_list set to Sponsored
- Priority changed from N/A to 1
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
a postgres 9.6, from the postgresql official repo, has the following string
postgres: 9.6/main: writer process
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/1087
- 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 4.0.1, 3.1.16 and 3.2.10 which were released today.
- Related to Bug #14742: System technique don't support PostgreSQL from other source than the distribution added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by