Actions
Bug #17145
closedRudder 6 check postgresql process failes
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
Description
Hi,
after a fresh installation of the Rudder 6.0.4 on SLES12 SP4 there the following error with "Check postgresql process".
Best regards
Alex
OS: SLES12 SP4
Rudder agent: 6.0.4
Rudder server: 6.0.4
rudder:~ # rudder agent run -q
Rudder agent 6.0.4.release
Node uuid: root
Start execution with config [20200416-142857-9962ba1e]
M| State Technique Component Key Message
E| error server-roles Check postgresql process postgresql service running could not be repaired
## Summary #####################################################################
36 components verified in 6 directives
=> 36 components in Enforce mode
-> 30 compliant
-> 5 not-applicable
-> 1 error
Execution time: 2.14s
################################################################################
rudder:~ #
rudder:~ # chkconfig |egrep postgres
rudder:~ # systemctl status postgresql.service
● postgresql.service - PostgreSQL database server
Loaded: loaded (/usr/lib/systemd/system/postgresql.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2020-04-16 14:27:59 CEST; 19h ago
Main PID: 5127 (postgres)
Tasks: 20 (limit: 512)
CGroup: /system.slice/postgresql.service
[...]
rudder:~ #
Updated by Alexander Brunhirl over 4 years ago
- after a fresh Rudder 6.0.4 installation on SLES12 SP4 the following error occurred with "Check postgresql process".
Updated by Alexander Brunhirl over 4 years ago
rudder:/var/rudder/configuration-repository/techniques/system/server-roles/1.0 # cat component-check.cf
[...]
!sles_12::
"postgresql_service_name" string => execresult("${paths.systemctl} --no-ask-password list-unit-files --type service | ${paths.awk} -F'.' '{print $1}' | ${paths.grep} -E \"^postgresql-?[0-9]*$\" | tail -n 1", "useshell");
sles_12::
"postgresql_service_name" string => execresult("chkconfig 2>/dev/null | ${paths.awk} '{ print $1 }' | ${paths.grep} 'postgresql' | tail -n 1", "useshell");
[...]
rudder:/var/rudder/configuration-repository/techniques/system/server-roles/1.0 #
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 6.0.5 to 6.0.6
Updated by Alexis Mousset over 4 years ago
- Status changed from New to In progress
- Assignee set to Alexis Mousset
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 6.0.6 to 6.0.7
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 6.0.7 to 6.0.8
Updated by Nicolas CHARLES over 4 years ago
- Assignee changed from Alexis Mousset to Nicolas CHARLES
Updated by Nicolas CHARLES over 4 years ago
- Related to Bug #16470: Postgresql service name is not detected properly on SLES 12 added
Updated by Nicolas CHARLES over 4 years ago
- 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/1612
Updated by Nicolas CHARLES over 4 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-techniques|800e9db460c2213a6481d694d8e91d8b28645c8e.
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 6.0.8 to 6.0.7
Updated by Vincent MEMBRÉ over 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.0.7 and 6.1.1 which were released today.
Actions