Project

General

Profile

Actions

Bug #3260

closed

The distributePolicy is broken on RHEL based machines

Added by Matthieu CERDA almost 10 years ago. Updated almost 10 years ago.

Status:
Released
Priority:
1
Assignee:
-
Category:
System techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Regression:

Description

The distributePolicy is broken on RHEL based machines, some adjustments need to be done (incorrect groups, PostgreSQL configuration failure ...)

It needs to be refreshed a bit.

Actions #1

Updated by Matthieu CERDA almost 10 years ago

Adjustments:

  • Update the htpasswd group to "apache" on RHEL machines
  • Update the initCheck promise with "httpd" as apache binary and init, and use chkconfig instead of insserv to set the service to start on boot
  • Update the rsyslogConf not to edit the /etc/rsyslog.d/psql.conf file (harmless but will output false errors)
Actions #2

Updated by Matthieu CERDA almost 10 years ago

  • % Done changed from 0 to 80

The first pass of modification has been made. => https://github.com/Kegeruneku/rudder-techniques/tree/bug_3260/dev/3260_correct_the_distributepolicy_on_rhel

Now, only some tiny things remain to be done:
  • Check why cf-serverd seems to restart all the time
  • Check why the server is unable to download his own uuid (seems like an apache misconfiguration)
Actions #3

Updated by Matthieu CERDA almost 10 years ago

  • Assignee changed from Matthieu CERDA to Jonathan CLARKE

Pull request available here for validation: https://github.com/Normation/rudder-techniques/pull/55

HOWEVER, the cf-serverd glitch is still present !!! I do need to correct this.

The apache bug was a host resolution problem, not linked to the Techniques.

Actions #4

Updated by Matthieu CERDA almost 10 years ago

  • Status changed from In progress to Pending technical review
  • % Done changed from 80 to 100

Hum, there was a simple reason for this: I did launch cf-serverd as /opt/rudder/sbin/cf-serverd ... as Rudder is expecting the /var version, it desperatly tries to launch it again, which collides with my instance and dies immediately because the cfengine port is already taken ...

This is a mistake for me, not CFEngine. Thus, all should be OK !

Technical review required here please.

Actions #5

Updated by Fran├žois ARMAND almost 10 years ago

  • Status changed from Pending technical review to Pending release
  • Assignee deleted (Jonathan CLARKE)
Actions #6

Updated by Nicolas PERRON almost 10 years ago

  • Status changed from Pending release to Released
Actions

Also available in: Atom PDF