Actions
Bug #5237
closed
Reports cannot be stored in local postgresql on a server Rudder in stand alone configuration
Status:
Released
Priority:
1
Assignee:
Category:
System integration
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
On a node installed with rudder-server-root, on a Debian system, localhost = 127.0.0.1 and machine hostname = 127.0.1.1.
By default, PostgreSQL binds to localhost only, and using the machine hostname leads to a connection refused. The the promises configure rsyslog to hit on the machine hostname by default when roles are installed, we should use localhost instead if the role rudder-server-root is present.
Updated by Matthieu CERDA almost 10 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Matthieu CERDA to Jonathan CLARKE
- % Done changed from 0 to 100
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/440
PR is ready !
Updated by Matthieu CERDA almost 10 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset policy-templates:commit:0170a42af562b234a4448ffbd3bcfe549858c541.
Updated by Matthieu CERDA almost 10 years ago
Applied in changeset policy-templates:commit:c34411d6c2704eb93420dc12bf0cffc3be77a5d7.
Updated by Vincent MEMBRÉ almost 10 years ago
- Subject changed from We should use localhost as a postgresql logging target if the role rudder-server-root is installed to Reports cannot be stored in local postgresql on a server Rudder in stand alone configuration
Updated by Vincent MEMBRÉ almost 10 years ago
- Category changed from 39 to System integration
Updated by Vincent MEMBRÉ almost 10 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.11.0~rc2 (announcement , changelog), which was released today.
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Actions