Project

General

Profile

Actions

Bug #8876

closed

The file rsyslog.d/rudder.conf might not be embedded in rudder-reports (db on a separate server)

Added by Alexandre Anriot over 4 years ago. Updated over 4 years ago.

Status:
Released
Priority:
N/A
Category:
Packaging
Target version:
Severity:
User visibility:
Effort required:
Priority:

Description

Hello,

The documentation Use a database on a separate server [*] is mentionning that rudder-reports:
  • should be removed from the root server ;
  • should be installed on the database server.

But the file rsyslog.d/rudder.conf, needed on the root / relay servers, is within this package.

It can be fixed on the root / relay servers with an agent run, but the file has to be deleted by hands on the database server.

Thanks.

[*] http://www.rudder-project.org/doc-3.2/_use_a_database_on_a_separate_server.html

Actions #1

Updated by Jonathan CLARKE over 4 years ago

  • Category set to Packaging
  • Assignee set to Alexis MOUSSET
  • Target version set to 308

After some thought, it appears the best approach here is to simply remove this config file from the rudder-reports package.

The reasoning is simple: rudder-reports can have 3 different uses:

  1. As part of the rudder-server-root "everything on one server" approach. That's fine.
  2. As part of an install with a separate DB server. In this case, we don't want this file on the DB server, just on the main server.
  3. As part of a distributed install (split server components). In this case, the server that forwards rsyslog logs to the PGSQL server can be either on each DB node or on the central webapp node.

In order to simplify this, we're going to remove the packaged version of this file. It will be installed automatically by the agent's system policies at the first run (at the end of rudder-init). That way we have just one place to change the behaviour and it can be runtime configurable.

Actions #2

Updated by Alexis MOUSSET over 4 years ago

  • Status changed from New to In progress
Actions #3

Updated by Alexis MOUSSET over 4 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Alexis MOUSSET to Jonathan CLARKE
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/1023
Actions #4

Updated by Alexis MOUSSET over 4 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions #5

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 308 to 3.1.14
Actions #6

Updated by Vincent MEMBRÉ over 4 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.1.15/14 and 3.2.8/7 which were released today.

Actions

Also available in: Atom PDF