[Bug 906735] Re: logrotate can't find /var/log/puppet if package was removed and that directory was empty

[Adam Gandelman]

Kenyon--

Looking into this further and other similar bugs, it seems this is the
expected behavior of logrotate.  In this case, the logrotate output is
non-fatal and, although annoying, does not cause logrotate to abort its
run and fail to process other rotate configs.  Puppet is a special case
in that its one of the few package that does not start its service on
package installation, resulting in an empty log directory until the
service is actually configured to start.  If the directory is empty on
package removal, it will be deleted before the logrotate conf file which
isn't deleted until purge.   The correct fix in your case is to --purge
the package from the system when output like this starts popping up from
cron.   If this is an insufficient work around, I'd advise opening a bug
against logrotate to silence such messages (though I believe this has
been discussed in the past but turns out to be a non-trivial change)

If you'd like some context around the general problem and its fix,
please see Bug #256891.

It's also worth noting that this is issue is resolved in the current
Precise release by way of Debian bug #564947: http://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=564947


** Bug watch added: Debian Bug tracker #564947
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=564947

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/906735

Title:
  logrotate can't find /var/log/puppet if package was removed and that
  directory was empty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/906735/+subscriptions