After noticing a recent post with sample logrotate configuration
for chef-server log files, I poked around the Opscode bug tracking
system, then the Chef source code repository, and found what I think are
indications that such configuration is provided for Red-Hat-based
distributions, but not for Debian-based distributions.
Am I interpreting this correctly? If so, what is the rationale for
providing them in one case but not the other?
The stuff in that folder is all deprecated I think. chef-server packages are built using the omnibus-chef-server project, and I don’t think it includes log rotation stuff beyond the OS defaults at all (from my 5 seconds of checking the templates folder).
After noticing a recent post with sample logrotate configuration
for chef-server log files, I poked around the Opscode bug tracking
system, then the Chef source code repository, and found what I think are
indications that such configuration is provided for Red-Hat-based
distributions, but not for Debian-based distributions.
Am I interpreting this correctly? If so, what is the rationale for
providing them in one case but not the other?
I don’t think [the omnibus-chef-server project, from chef-server
packages are built nowadays] includes log rotation stuff beyond
the OS defaults at all
I don’t see any logrotate configuration there, either. That’s
unfortunate. Various Web searches didn’t turn up any discussion of this
for me.
I don’t think [the omnibus-chef-server project, from chef-server
packages are built nowadays] includes log rotation stuff beyond
the OS defaults at all
I don’t see any logrotate configuration there, either. That’s
unfortunate. Various Web searches didn’t turn up any discussion of this
for me.
chef-server just logs to syslog I think, what you do with syslog is up to you
That’s not entirely true, with nginx and postgres and whatnot bundled with the chef server, it will also log to places like /var/log/chef-server/erchef or /var/log/chef-server/nginx. Our /var/log/chef-server/nginx/acces.log was taking up several gigabytes before manually setting a logrotate config.
I don’t think [the omnibus-chef-server project, from chef-server
packages are built nowadays] includes log rotation stuff beyond
the OS defaults at all
I don’t see any logrotate configuration there, either. That’s
unfortunate. Various Web searches didn’t turn up any discussion of this
for me.
On Wed, Feb 5, 2014 at 3:37 AM, Steven De Coeyer steven@banteng.be wrote:
chef-server just logs to syslog I think, what you do with syslog is up
to you
That’s not entirely true, with nginx and postgres and whatnot bundled with
the chef server, it will also log to places like
/var/log/chef-server/erchef or /var/log/chef-server/nginx. Our
/var/log/chef-server/nginx/acces.log was taking up several gigabytes before
manually setting a logrotate config.
I don’t think [the omnibus-chef-server project, from chef-server
packages are built nowadays] includes log rotation stuff beyond
the OS defaults at all
I don’t see any logrotate configuration there, either. That’s
unfortunate. Various Web searches didn’t turn up any discussion of this
for me.