Revision e62b9e07
Added by Alexis Mousset over 6 years ago
10_installation/10_install_server/11_install_root_server_debian.txt | ||
---|---|---|
==== Install Rudder Root server on Debian or Ubuntu
|
||
|
||
[WARNING]
|
||
|
||
=====
|
||
|
||
Any nodes running *syslogd* (not syslog-ng or rsyslog) will *fail* to send any
|
||
reports about the configuration rules they have applied to a Rudder Server running
|
||
on Ubuntu (and only on Ubuntu). Rudder will apply rules on nodes but will never get
|
||
reports from them. Therefore Rudder will not be able to calculate compliance.
|
||
|
||
The only supported platform using syslogd by default is *RHEL/CentOS 5*, and several
|
||
workarounds are available to fix this:
|
||
|
||
. Install another syslog server on your nodes, such as rsyslog or syslog-ng.
|
||
. Change the rsyslog configuration on the Rudder server (running Ubuntu 12.04
|
||
or later) to use port 514 and authorize this in the rsyslog configuration.
|
||
. Setup iptables on the node to send syslog traffic to the correct port on
|
||
your Rudder server.
|
||
. Use a different OS for your Rudder server that Ubuntu Server 12.04 or later.
|
||
|
||
=====
|
||
|
||
===== Add the Rudder packages repository
|
||
|
||
include::snippets/apt_key.txt.snippet[]
|
||
... | ... | |
|
||
----
|
||
|
||
[WARNING]
|
||
|
||
=====
|
||
|
||
Any nodes running *syslogd* (not syslog-ng or rsyslog) will *fail* to send any
|
||
reports about the configuration rules they have applied to a Rudder Server running
|
||
on Ubuntu (and only on Ubuntu). Rudder will apply rules on nodes but will never get
|
||
reports from them. Therefore Rudder will not be able to calculate compliance.
|
||
|
||
The only supported platform using syslogd by default is *RHEL/CentOS 5*, and several
|
||
workarounds are available to fix this:
|
||
|
||
. Install another syslog server on your nodes, such as rsyslog or syslog-ng.
|
||
. Change the rsyslog configuration on the Rudder server (running Ubuntu 12.04
|
||
or later) to use port 514 and authorize this in the rsyslog configuration.
|
||
. Setup iptables on the node to send syslog traffic to the correct port on
|
||
your Rudder server.
|
||
. Use a different OS for your Rudder server that Ubuntu Server 12.04 or later.
|
||
|
||
=====
|
||
|
||
include::snippets/initial_config.txt.snippet[]
|
||
|
10_installation/10_install_server/12_install_root_server_sles.txt | ||
---|---|---|
|
||
include::snippets/zypper_segfault.txt.snippet[]
|
||
|
||
[WARNING]
|
||
|
||
====
|
||
|
||
Zypper seems to be quite tolerant to missing dependencies and will let you install rudder-server-root even if you are missing
|
||
something like +git-core+ for example, if nothing provides it or you did not install it beforehand.
|
||
|
||
Special care should be taken during initial installation not to say "Continue anyway" if Zypper does complain a dependency can
|
||
not be resolved and asks what to do.
|
||
|
||
====
|
||
|
||
===== Add the Rudder packages repository
|
||
|
||
include::snippets/rpm_key.txt.snippet[]
|
||
... | ... | |
|
||
----
|
||
|
||
[WARNING]
|
||
|
||
====
|
||
|
||
Zypper seems to be quite tolerant to missing dependencies and will let you install rudder-server-root even if you are missing
|
||
something like +git-core+ for example, if nothing provides it or you did not install it beforehand.
|
||
|
||
Special care should be taken during initial installation not to say "Continue anyway" if Zypper does complain a dependency can
|
||
not be resolved and asks what to do.
|
||
|
||
====
|
||
|
||
include::snippets/initial_config.txt.snippet[]
|
||
|
||
|
Also available in: Unified diff
Fixes #11162: Put warnings (about dependencies for example) before install/upgrade instructions