Cookbook adds logs, but does not add rotation policy

[jkugler]

Cookbook version

4.0.0

Chef-client version

12.x

Platform Details

Ubuntu 14.04

Scenario:

Tried to use cookbook, ended up with full disk

Steps to Reproduce:

Use cookbook. Observe lack of rotation policy for added cookbooks.

Expected Result:

rsyslog should add rotation policy for any logs it adds

Actual Result:

Used cookbook with defaults. It adds, among others, boot.log, but doesn't add a rotation policy for the log file. In our case, due to a misbehaving app (or mis-logging app) boot.log grew to over 13G, and along with other log files, filled the disk. I confirmed that boot.log is not in the Ubuntu rsyslog package, so it is being added by this cookbook. The rsyslog package does define rotation policy for any logs that are in its default config.

[iennae]

@jkugler Thanks for filing this. We'll take a look and get this cleaned up. Getting a full disk is never a great experience. We appreciate you letting us know of the problem.

[vorgusa]

Technically the RPM creates /etc/logrotate.d/syslog which is pointing to /var/run/syslogd.pid for the restart of services. I think the main issue or related issue is that that needs to be pointed to the correct PID file so that files are released. lsof | grep delete shows a lot of log files sitting on the partition still. This might not be exactly the same as jkugler, but related to the new feature.

[docwhat]

In addition, it should be pointed at the correct logfiles (if they are changed via the attributes).