Skip to content

Account for newer version of rsyslog, and custom app name#14

Open
coreone wants to merge 1 commit intologgly:masterfrom
broadinstitute:newerrsyslog
Open

Account for newer version of rsyslog, and custom app name#14
coreone wants to merge 1 commit intologgly:masterfrom
broadinstitute:newerrsyslog

Conversation

@coreone
Copy link
Copy Markdown

@coreone coreone commented Oct 27, 2015

Some of the syntax and configuration suggestions have changed for rsyslog > 5. For example, template and action are now completely different, and there is now a block of $ActionQueue settings that are suggested for each remote syslog configuration. I was having trouble getting some logs to ship, and updating the configuration with those $ActionQueue settings fixed the issue for me.

Additionally, I added some tests for some new parameters I added (so that the $ActionQueue settings are customizable) and tried to run the tests, but the tests seem to be broken in some way. I ran the tests on master and most of them failed, so either the standard bundle install; bundle exec rake test process doesn't work on my machine (which it does for other modules) or something else is going on with the tests.

@mostlyjason
Copy link
Copy Markdown
Contributor

@psquickitjayant can you review this when you get a chance?

@coreone coreone changed the title Account for newer version of rsyslog Account for newer version of rsyslog, and custom app name Jan 7, 2016
* Update rsyslog.pp to choose correct template for version
* Add more parameters for rsyslog in params.pp
* Whitespace in init.pp
* Add tests for new parameters to rsyslog_spec.rb
* Correct some spacing in loggly.conf.erb
* Allow for adding a custom "app-name" field to the output template
* Update documentation comments in rsyslog.pp
* Add updated tests for appname_string option
* Make sure services restart on cert change
@coreone
Copy link
Copy Markdown
Author

coreone commented Mar 30, 2016

@psquickitjayant @mostlyjason had to update this today to make the syslog service (either rsyslog or syslog_ng) restart if the certificate changed due to the Loggly cert change that happens today. If the restart doesn't happen, rsyslog won't be refreshed with the corrected certificate chain. Please test as soon as possible as this has been hanging out in here for quite a long time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants