PE 3.3 has been released, please add a release compatible with it.
Thanks,
Vadym

The default options you have set for the defaults file breaks rsyslog on my my fedora 18 servers.

I have worked out a fix which I am working on in my fork.
I will let you know when it's ready.

Could you please tag on github the released version on the forge ?

Hello again,

Would you be open to pull requests against this module? I'm thinking of starting with one to align the module with the style guide and then another to add support for RHEL and derivatives.

Thanks for your time,

Ryan

Maybe I'm missing a key feature already provided by this module, but if I want to have all log messages from pulp go to a separate file I'd add the following to '/etc/rsyslog.d/pulp.conf'.

:programname, isequal, "pulp" -/var/log/pulp.log
& ~

That never gets picked up as /var/log/messages continues to contain the logs.

If I rename pulp.conf to 00_pulp.conf then all pulp messages go to /var/log/pulp.log but the timestamp format is not picking up that was defined in /etc/rsyslog.d/client.conf. Is this a case that hasn't been built into the module yet? It seems like the only way to cleanly work around this is to split the contents of client.conf into two separate files. One is 00_client.conf that configures things like ActionFileDefaultTemplate and the remote logging, and the other being 99_local.conf that has the local log rules.

I'd be interested to know how others handle such cases using this module, or if a PR that splits the client configuration up into 2 files would be accepted.

hi,
I think, it's more a Puppet basic question, but I couldn't find a nice way, without bad workarounds.

I have define for example rsyslog::server in LDAP: "puppetClass: rsyslog::server" for one node. The problem is, that I can't overwrite the defaults like server_dir.

The files looks like:
(the rsyslog module is imported with $conf/manifests/site.pp)

/etc/puppet/modules/rsyslog/manifests/{server.pp,client.pp,db.pp}

For example server.pp

class rsyslog::server inherits rsyslog {
'rsyslog::server': enable_tcp => true,
enable_udp => true,
enable_onefile => false,
server_dir => '/var/log/remote/',
}


init.pp

I tried a lot of combinations, but nothing works as expected.

cu denny

The package rsyslog-gnutls is no longer required with rsyslog 8.2 stable, at least not on Ubuntu precise. Trying to install it causes errors.

Error: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install rsyslog-gnutls' returned 100: Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 rsyslog-gnutls : Depends: rsyslog (= 8.2.0-0adiscon1precise3) but 8.2.0-0adiscon1precise4 is to be installed
E: Unable to correct problems, you have held broken packages.
Wrapped exception:
Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install rsyslog-gnutls' returned 100: Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 rsyslog-gnutls : Depends: rsyslog (= 8.2.0-0adiscon1precise3) but 8.2.0-0adiscon1precise4 is to be installed
E: Unable to correct problems, you have held broken packages.
Error: /Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure: change from purged to latest failed: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install rsyslog-gnutls' returned 100: Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 rsyslog-gnutls : Depends: rsyslog (= 8.2.0-0adiscon1precise3) but 8.2.0-0adiscon1precise4 is to be installed
E: Unable to correct problems, you have held broken packages.
Notice: /Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]: Dependency Package[rsyslog-gnutls] has failures: true
Warning: /Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]: Skipping because of failed dependencies
Notice: /Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]: Dependency Package[rsyslog-gnutls] has failures: true
Warning: /Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]: Skipping because of failed dependencies
Notice: /Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]: Dependency Package[rsyslog-gnutls] has failures: true
Warning: /Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]: Skipping because of failed dependencies
Notice: /Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/50-default.conf]: Dependency Package[rsyslog-gnutls] has failures: true
Warning: /Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/50-default.conf]: Skipping because of failed dependencies
Notice: /Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]: Dependency Package[rsyslog-gnutls] has failures: true
Warning: /Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]: Skipping because of failed dependencies
Notice: /Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]: Dependency Package[rsyslog-gnutls] has failures: true
Warning: /Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]: Skipping because of failed dependencies
Notice: /Stage[main]/Rsyslog::Service/Service[rsyslog]: Dependency Package[rsyslog-gnutls] has failures: true
Warning: /Stage[main]/Rsyslog::Service/Service[rsyslog]: Skipping because of failed dependencies
Notice: Finished catalog run in 1.43 seconds

Hello,

We detected a small problem since 8804f3f: the clients were unable to connect for some reason.
After some tests, it seems the remote server hostname should be moved after line 69, in order to get the connection settings before the remote server.

Can you please have a look? The certificate ($DefaultNetStreamDriverCAFile) may stay as is, as long as it's also before the remote server.

Thank you!

Cheers,

C.

Is there with your module to specify the log spool path for the clients?

Hi,

I have a problem using the system utility /bin/logger when rsyslog is started with option -c4 as specified in /etc/sysconfig/rsyslog. I can only get /bin/logger to work if I set compatibility level to 3 by commenting out the RSYSLOGD_OPTIONS line in /etc/sysconfig/rsyslog

It appears the template rsyslog_default.erb looks at the rsyslog release and adds option -c4 by default with no way to change it.

<% if @rsyslog_version and @rsyslog_version.split('.')[0].to_i < 7 -%>
# Debian, Ubuntu
RSYSLOGD_OPTIONS="-c4"

I see $custom_params has a TODO next to it. Is it intended to use $custom_params in the template to make it more flexible?

Wrong repo.

The module does not relay received messages if both server and client are set up on a server.
Here is my suggestion to solve the issue.
--- saz-rsyslog-3.3.0.org/manifests/server.pp 2014-06-11 13:12:00.000000000 +0200
+++ saz-rsyslog-3.3.0/manifests/server.pp 2014-09-05 18:34:38.512367899 +0200
@@ -7,6 +7,7 @@

[enable_tcp]

[enable_udp]

[enable_onefile]

+# [relay_server]

[server_dir]

[custom_config]

[high_precision_timestamps]

@@ -32,6 +33,7 @@
$enable_tcp = true,
$enable_udp = true,
$enable_onefile = false,

• $relay_server = false,
  $server_dir = '/srv/log/',
  $custom_config = undef,
  $port = '514',
  diff -ur saz-rsyslog-3.3.0.org/README.md saz-rsyslog-3.3.0/README.md
  --- saz-rsyslog-3.3.0.org/README.md 2014-08-14 14:59:10.000000000 +0200
  +++ saz-rsyslog-3.3.0/README.md 2014-09-05 18:38:35.164377894 +0200
  @@ -131,6 +131,7 @@
  enable_tcp => true,
  enable_udp => true,
  enable_onefile => false,

•    relay_server              => false,
   server_dir                => '/srv/log/',
   custom_config             => undef,
   high_precision_timestamps => false,
  

  @@ -148,6 +149,7 @@
  enable_tcp true,false Enable TCP listener. Defaults to true.
  enable_udp true,false Enable UDP listener. Defaults to true.
  enable_onefile true,false Only one logfile per remote host. Defaults to false.
• relay_server true,false If the server should be able to relay the received logs to another server. The rsyslog::client must also be set up.
  server_dir STRING Folder where logs will be stored on the server. Defaults to '/srv/log/'
  custom_config STRING Specify your own template to use for server config. Defaults to undef. Example usage: custom_config => 'rsyslog/my_config.erb'
  high_precision_timestamps true,false Whether or not to use high precision timestamps.
  diff -ur saz-rsyslog-3.3.0.org/templates/server/_default-header.conf.erb saz-rsyslog-3.3.0/templates/server/_default-header.conf.erb
  --- saz-rsyslog-3.3.0.org/templates/server/_default-header.conf.erb 2014-02-06 14:59:47.000000000 +0100
  +++ saz-rsyslog-3.3.0/templates/server/_default-header.conf.erb 2014-09-05 18:36:12.652371875 +0200
  @@ -32,5 +32,7 @@
  $InputTCPServerStreamDriverAuthMode anon
  <% end -%>

+<% if scope.lookupvar('rsyslog::server::relay_server') == false -%>

Switch to remote ruleset

$RuleSet remote
+<% end -%>

Hi,

looking ad the rsyslog docs, relp seems to have InputRELPServerBindRuleset since some 6.X-ish version - could you enable it again? Supporting Relp with tls would also be nice to have, I'm happy to provide and test the necessary changes.

thanks,

bernd

On a base installation of CentOS 7 using this module and the following parameters, double logging can be seen under /var/log/messages.

  class { 'rsyslog::client':
    log_local => true,
    log_auth_local => true,
    log_remote => false,
  }

Example:

$ logger test

yields

Oct 21 16:44:03 mad-west-vcs006 centos: test
Oct 21 16:44:03 mad-west-vcs006 centos: test

This seems to be something to do with the journal integration added in el7.

One of the configuration items in the stock config (removed under puppet) fixes this behaviour

# Turn off message reception via local log socket;
# local messages are retrieved through imjournal now.
$OmitLocalLogging on

Should this be made part of the stock config for el7?

On a CentOS 5 system ( I assume other versions of RHEL this may apply), setting the below options:
perm_file => '0640',
perm_dir => '0750',
do not take effect, as they are overridden by the umask of the the rsyslog process. This is typically set by RHEL rsyslog init script.
This can be resolved by setting the $Umask paramater to 0000.
It is well documented here:
http://www.rsyslog.com/doc/rsconf1_filecreatemode.html

I will submit a PR shortly.

Puppet Enterprise 3.7.2
Error when declaring "remote_servers".

Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to parse template rsyslog/client.conf.erb:
  Filepath: /etc/puppetlabs/puppet/environments/testing/modules/rsyslog/templates/client.conf.erb
  Line: 38
  Detail: undefined method `flatten' for "remote_server.domain.com":String
 at /etc/puppetlabs/puppet/environments/testing/modules/rsyslog/manifests/client.pp:48 on node hostname.domain.com
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

puppet master & client 3.7.3
ubuntu 14.04

default settings:
class { 'rsyslog::server':
enable_udp => true,
enable_onefile => false,
server_dir => '/mnt/log/',
custom_config => undef,
high_precision_timestamps => false,
}

Error:
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Duplicate declaration: Package[rsyslog-gnutls] is already declared in file /etc/puppet/modules/loggly/manifests/rsyslog.pp:60; cannot redeclare at /etc/puppet/modules/rsyslog/manifests/install.pp:29 on node redacted.com
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

This is my first submitted issue on github, if I left anything out or placed wrong please let me know so I can update/improve.

Hi,

Thanks for the module. Having implemented it across multiple CentOS 6.4 x86_64 machines, I can report a correctable error is encountered.

In params.pp the default "spool_dir" is defined (which elsewhere defines Work_Dir) as '/var/spool/syslog/' however rsyslogd complains that the trailing slash is invalid and had to be removed.

I cannot verify for freebsd or debian, though I imagine these will act in the same way.

Resolution: Remove trailing slash in string on line 58 of manifests/params.pp

change from stopped to running failed: Could not start Service[rsyslog]: Execution of '/usr/bin/systemctl start rsyslog' returned 1: A dependency job for rsyslog.service failed. See 'journalctl -xn' for details.

^If I do 'systemctl enable rsyslog' everything is fixed and fine. I'm not sure what is causing this currently.

Hi!

Is there a chance that you will implement custom_params soon?

Regards,
p.

Due bug 192 in rsyslog, PreserveFQDN isn't working in CentOS 6.5 (rsyslog 5.8.10).

Bug has been fixed in rsyslog 5.8.13, but the package isn't yet in the CentOS Base repository.

For hostnames like "server1" or "server-r1" and so on using [A-Za-z-] regexp leads to truncated remote host name: "server1" or "server-" in this case.
[A-Za-z0-9-] works like a charm.

With both master and agent running puppet 3.7.4 and future parser enabled, I'm getting

Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Comparison of: String >= Integer, is not possible. Caused by 'A String is not comparable to a non String'. at /etc/puppet/environments/production/librarian/rsyslog/manifests/params.pp:82:42 on node ...

Looks like it's breaking on this line

      elsif $::operatingsystemmajrelease >= 7 {

Maybe use

      elsif versioncmp($::operatingsystemmajrelease, '7') > 0 {

instead?

currently, when sending a set of logs to a remote server, they will also end up in /var/log/syslog

# Sending logs that match <%= pattern %> to <%= host %> via <%= protocol_type %> on <%= port %> using <%=format_type %> format.
<%= pattern %> <%= protocol %><%= host %>:<%= port %><%= format %>

i've tried adding a horrible hack of appending "\n& ~" to port, but that ended up being broken, because of the comment :D

i'd like to be able to only send logs to the remote, since they already exist as files on the host
(i'm using imfiles to forward files to a central logstash server.)

What would be a good name to introduce here, that means, this pattern will only be sent to the remote host?

2014-06-19T03:49:39.976915-04:00 ip-10-236-193-96 rsyslogd-3003: Could not find template 'RSYSLOG_TF_LongTagForwardFormat' - action disabled [try http://www.rsyslog.com/e/3003 ]
2014-06-19T03:49:39.976933-04:00 ip-10-236-193-96 rsyslogd-2207: error during parsing file /etc/rsyslog.d/50-default.conf, on or before line 32: errors occured in file '/etc/rsyslog.d/50-default.conf' around line 32 [try http://www.rsyslog.com/e/2207 ]

I got this error when I tried to use this module. Because we have some configuration requirements in 50-default.conf. We added some configuration with template defined in rsyslog::client => log_templates. But it seems that 50-default is loaded before client.conf which makes it complain the template is not defined. If I move the template definition to /etc/rsyslog.conf, it just works.

rsyslogd -v

rsyslogd 7.6.3, compiled with:
FEATURE_REGEXP: Yes
FEATURE_LARGEFILE: No
GSSAPI Kerberos 5 support: Yes
FEATURE_DEBUG (debug build, slow code): No
32bit Atomic operations supported: Yes
64bit Atomic operations supported: Yes
Runtime Instrumentation (slow code): No
uuid support: Yes
Number of Bits in RainerScript integers: 32 (due to too-old json-c lib)

See http://www.rsyslog.com for more information.

Can we move the template definition to rsyslog.conf instead of client.conf in the module?

Ubuntu does not have xconsole, and xconsole is enabled by default in the client-conf.erb template.

rsyslog log this to syslog:

rsyslogd-2039: Could not open output pipe '/dev/xconsole' [try http://www.rsyslog.com/e/2039 ]

Steps to reproduce:
Install latest stable rsyslog as described at http://www.rsyslog.com/ubuntu-repository/
then:
puppet apply -e 'include rsyslog'

After that, rsyslog service is not running on the system, and it cannot be started at all.

Including rsyslog produces the following error on an agent run

# puppet agent -tv

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Function Call, Error from DataBinding 'hiera' while looking up 'rsyslog::rsyslog_package_name': uncaught throw :undefined_variable at /etc/puppet/environments/production/modules/rc/manifests/base.pp:2:1 on node puppet-03.****.****
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

The offending line in that file is

include rsyslog

when I use imfile more than once I receive:

[try http://www.rsyslog.com/e/2221 ]
2014-07-29T14:29:38.575582+00:00 vagrant-front01 rsyslogd-2221: module 'imfile' already in this config, cannot be added

if I manually remove $ModLoad imfile and leave it only once all of my configurations work for file input.

Thanks

Seems these are configs created by your plugin, but they dont seem to be compatible with my version of rsyslog runing on ubuntu 13.04. How can i disable them from being added every time? Im not sure why its complaining about the group id though as obviously user group 0 exists for root. Suggestions?

rsyslogd: version 5.8.11, config validation run (level 1), master config /etc/rsyslog.conf
rsyslogd: WARNING: rsyslogd is running in compatibility mode. Automatically generated config directives may interfer with your rsyslog.conf settings. We suggest upgrading your config and adding -c5 as the first rsyslogd option.
rsyslogd: ID for group '0' could not be found or error [try http://www.rsyslog.com/e/3003 ]
rsyslogd: the last error occured in /etc/rsyslog.conf, line 26:"$PrivDropToGroupID 0"
rsyslogd: CONFIG ERROR: could not interpret master config file '/etc/rsyslog.conf'. [try http://www.rsyslog.com/e/2124 ]
rsyslogd: Warning: backward compatibility layer added to following directive to rsyslog.conf: ModLoad immark
rsyslogd: Warning: backward compatibility layer added to following directive to rsyslog.conf: MarkMessagePeriod 1200
rsyslogd: Warning: backward compatibility layer added to following directive to rsyslog.conf: ModLoad imuxsock

I've been looking into compatibiity with RHEL7, which uses systemd for service startup. I've found rsyslogd failing to start:

[root@virt-who cfeskens]# systemctl status rsyslog
rsyslog.service - System Logging Service
Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; enabled)
Active: failed (Result: exit-code) since Fri 2014-06-27 06:02:13 PDT; 11min ago
Process: 21339 ExecStart=/usr/sbin/rsyslogd -n $SYSLOGD_OPTIONS (code=exited, > status=1/FAILURE)
Main PID: 21339 (code=exited, status=1/FAILURE)

Jun 27 06:02:13 virt-who.willamette.edu systemd[1]: Starting System Logging Service...
Jun 27 06:02:13 virt-who.willamette.edu systemd[1]: rsyslog.service: main process exited, code=exited, status=1/FAILURE
Jun 27 06:02:13 virt-who.willamette.edu systemd[1]: Failed to start System Logging Service.
Jun 27 06:02:13 virt-who.willamette.edu systemd[1]: Unit rsyslog.service entered failed state.

It looks like rsyslogd handles it's EnvironmentFile a little differently than the normal init process and doesn't interpret environment variables in bash, causing SYSLOGD_OPTIONS to not parse correctly. If I replace that with SYSLOGD_OPTIONS="", it works fine.

I'd be happy to submit a patch, but was wondering whether you'd prefer an additional defaults file for RHEL7, or would prefer to convert it to a template.

I'd like to make rsyslog listen on localhost only.. so haproxy can log to it.

Something like this:

Provides UDP syslog reception

$ModLoad imudp
$UDPServerAddress 127.0.0.1
$UDPServerRun 514

I'm not keen on just hacking rsyslog without upstreaming.. so I'm asking, would you prefer to add a "listenip" to rsyslog::server.. or perhaps a "listen_localhost" to the rsyslog::client ?

(if you at all want this option ofcourse :)

Hello, thank you for this module. I run into this error sometimes when running your module against a system that has ksyslogd installed. Maybe your module can include service syslog stop && chkconfig syslog off ?

Error: Could not start Service[rsyslog]: Execution of '/sbin/service rsyslog start' returned 1: 
Error: /Stage[main]/Rsyslog::Service/Service[rsyslog]/ensure: change from stopped to running failed: Could not start Service[rsyslog]: Execution of '/sbin/service rsyslog start' returned 1: 

[root@myserver ~]# /etc/init.d/rsyslog start
Shut down sysklogd before you run rsyslog
[root@myserver ~]# 

Would it be possible to implement Hiera support similar to what is implemented in your Sudo module? I was thinking it would be really useful to have that type of support to create include files in rsyslog.d.

@saz
saz/rsyslog v1.1.4 was released way back on Jul 2, 2012. Lots of new things have been added since (like RedHat support). Can you cut another Forge release?

WE have the case were the server also forwards the logs, and the documentation mentions that rsyslog::servers has an attribute remote_servers however checking server.pp and github search repo does not show that attribute can be set for the server only client, it would give us much flexibility if it can handle that case too, not just fix the documentation

In some cases, we might need to redirect to ~ in order not to write the logs to /var/log/messages.
The default client template's pattern does not have this option.
Ex: if $syslogfacility-text == 'local6' then ~
If we donot mention the hostname or port , from the init.pp the default values are coming.
or else if we supply empty value, remotehost section is appending @:

hi,

I would like to ask, how I can add a file to the (Debian Squeeze) /etc/rcsyslog.d/ directory. In my case, I want to submit mail.info from the mailserver to another host (for monitoring), which has rsyslog::client & rcsyslog::server on the same time active.

Any suggestions?

While attempting to set a load order for /etc/rsyslog.d/*.conf I ran into an issue changing the "server.conf" and "client.conf" configuration file names.

I had attempted to set a static file load order by prefixing the config files with a number to force the config files to load prior or before other included configuration files. This seemed possible based on the class rsyslog. Ex. /etc/rsyslog.d/25-client.conf or /etc/rsyslog.d/10-server.conf.

Ex manifest to override the defaults set in ::rsyslog: for rsyslog::client:

class client_logging {
  class { '::rsyslog': 
    client_conf => '/etc/rsyslog.d/25-client.conf',
  }

  class { '::rsyslog::client':
    set_client_opts => ...,
  }
}

The above does not result in any errors however the config file for the client is still written as /etc/rsyslog.d/client.conf.

When calling

class { 'rsyslog::client' : }

I get the following error

(Scope(Class[Rsyslog::Config])) Could not look up qualified variable 'rsyslog::client::preserve_fqdn'; class rsyslog::client has not been evaluated

Is there any particular reason why the "Emergencies" line that appears in the default Debian rsyslog config was left out of the default client template?

#
# Emergencies are sent to everybody logged in.
#
*.emerg                         :omusrmsg:*

On amazon ec2 node I'd called

puppet apply --verbose --debug /etc/puppet/site.pp

and got yum update error:

Debug: Executing '/usr/bin/yum -d 0 -e 0 -y install rsyslog-relp'
Error: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y install rsyslog-relp' returned 1: Error: Nothing to do

Error: /Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure: change from absent to latest failed: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y install rsyslog-relp' returned 1: Error: Nothing to do

thx4fix.

Variable access via 'remote_prot' is deprecated. Use '@remote_prot' instead. template[/etc/puppet/environments/production/modules/syslog_ng/templates/syslog-ng.conf.client.erb]:87

I'm trying to get TLS working with the Papertrail logging service. They require authenticating by hostname. Currently the client.conf.erb template only allows for anonymous authentication. (

Would it be possible to add the ability to pass a different auth mode? For this example I'd need to pass x509/name, then also specify a value for $ActionSendStreamDriverPermittedPeer.

It would look like this:

$ActionSendStreamDriverAuthMode x509/name # authenticate by hostname
$ActionSendStreamDriverPermittedPeer *.papertrailapp.com

Hi,

i have this Errormessage on my Debian Installations:
Starting enhanced syslogd: rsyslogdrsyslogd: error: option -c is no longer supported - ignored

I fix the default file '/files/rsyslog_default'
from:

Debian, Ubuntu

RSYSLOGD_OPTIONS="-c4"
to:

Debian, Ubuntu

RSYSLOGD_OPTIONS=""

Hi,

The Modulefile says that puppet-rsyslog uses the Apache2 license, but no LICENSE or NOTICE files are shipped with the module.

According to this guide, you should supply the two files so that they're easy to find:

To apply the ALv2 to a new software distribution, include one copy of the license text by copying the file:

http://www.apache.org/licenses/LICENSE-2.0.txt

into a file called LICENSE in the top directory of your distribution. If the distribution is a jar or tar file, try to add the LICENSE file first in order to place it at the top of the archive. This covers the collective licensing for the distribution.

In addition, a correct NOTICE file MUST be included in the same directory as the LICENSE file.

hi,

I have Debian Squeeze running as client and server and installed the module via "puppet module install saz/rsyslog". After adding my node to class "rsyslog::client" I get only the message:

Feb 12 09:54:13 install puppet-master[4281]: Unsupported platform: Debian at /etc/puppet/environments/production/modules/rsyslog/manifests/params.pp:83 on node client02

What I have done wrong?

cu denny

Wrong repo.

Hello,

I'm running into a bit of a snag declaring both the rsyslog client and server on Ubuntu 10.04 as described in your modules README.

Here are some log messages from /srv/log/ubuntu indicating the problem:
Jan 24 14:33:05 ubuntu kernel: imklog 4.2.0, log source = /proc/kmsg started.
Jan 24 14:33:05 ubuntu rsyslogd: origin software="rsyslogd" swVersion="4.2.0" x-pid="18990" x-info="http://www.rsyslog.com"start
Jan 24 14:33:05 ubuntu rsyslogd-3003: invalid or yet-unknown config file command - have you forgotten to load a module? [try http://www.rsyslog.com/e/3003 ]
Jan 24 14:33:05 ubuntu rsyslogd: the last error occured in /etc/rsyslog.d/server.conf, line 16
Jan 24 14:33:05 ubuntu rsyslogd-3003: invalid or yet-unknown config file command - have you forgotten to load a module? [try http://www.rsyslog.com/e/3003 ]
Jan 24 14:33:05 ubuntu rsyslogd: the last error occured in /etc/rsyslog.d/server.conf, line 43
Jan 24 14:33:05 ubuntu rsyslogd-3003: invalid or yet-unknown config file command - have you forgotten to load a module? [try http://www.rsyslog.com/e/3003 ]
Jan 24 14:33:05 ubuntu rsyslogd: the last error occured in /etc/rsyslog.d/server.conf, line 45
Jan 24 14:33:05 ubuntu rsyslogd-3003: invalid or yet-unknown config file command - have you forgotten to load a module? [try http://www.rsyslog.com/e/3003 ]
Jan 24 14:33:05 ubuntu rsyslogd: the last error occured in /etc/rsyslog.d/server.conf, line 48
Jan 24 14:33:05 ubuntu rsyslogd: the last error occured in /etc/rsyslog.conf, line 28
Jan 24 14:33:05 ubuntu rsyslogd-2123: CONFIG ERROR: could not interpret master config file '/etc/rsyslog.conf'. [try http://www.rsyslog.com/e/2123 ]

The lines from server.conf that it's upset about:
16: $RuleSet remote
43: $RuleSet RSYSLOG_DefaultRuleset
45: $InputUDPServerBindRuleset remote
48: $InputTCPServerBindRuleset remote

It seems like there's just a missing line for loading the module but I wanted to post this issue and hopefully get your thoughts as I dig deeper.

Thanks for producing this!

--Ryan