Bug #14110: Broken server install in 4.1 on ubuntu14 - Rudder - Issue Tracker

Actions

Copy link

Bug #14110

closed

Broken server install in 4.1 on ubuntu14

Added by Félix DALLIDET almost 6 years ago. Updated over 5 years ago.

Status:

Rejected

Priority:

N/A

Assignee:

Category:

Server components

Target version:

4.1.22

Pull Request:

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

I tried an install of the nightly on a ubuntu14 machine, I had an error at install time about postgres,
unfortunatly I have not the message error anymore.
Then, rsyslog stopped at next agent run because it was not bale to connect to the postgres database.
Restarting the rsyslog service fixed the problem.

Error in syslog about the rsyslog unable to connect to the database:

syslog:Jan  8 16:35:29 server rsyslogd: rsyslogd's groupid changed to 104
syslog:Jan  8 16:35:29 server rsyslogd: rsyslogd's userid changed to 101
syslog:Jan  8 16:35:29 server rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
syslog:Jan  8 16:35:29 server rudder[10754]: CFEngine(agent) rudder Q: "...in/service rsys": rsyslog stop/waiting
syslog:Q: "...in/service rsys": rsyslog start/running, process 12595
syslog:Jan  8 16:35:29 server rudder[10754]: CFEngine(agent) rudder R: Info : Restarted rsyslog
syslog:Jan  8 16:35:30 server rsyslogd: db error (1): no connection to the server