Bug #13499
closed
2 logrotate tools beeing active on /var/log/foreman logfiles
Description
Foreman is using the default Rails logging infrastructure
to log to "log/#{Rails.env}.log"
(see /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/application/configuration.rb).
Rails is using the "logging" gem for that, as defined in
/opt/rh/ruby193/root/usr/share/gems/gems/logging-1.8.1/lib/logging.rb which says:
appender =
case dev
when String
::Logging::Appenders::RollingFile.new(name, a_opts)
else
::Logging::Appenders::IO.new(name, dev, a_opts)
end
(dev being the device/filename to log to). As we are passing
Updated by Dominic Cleal about 8 years ago
- Status changed from New to Need more information
The ticket description appears to be truncated. It's very unclear what bug you're trying to report.
Updated by Christian Horn about 8 years ago
Description of the problem:
2 logrotate tools beeing active on /var/log/foreman logfiles:
/var/log/foreman seems to be cared for by 2 mechanisms:
logrotate and a ruby mechanism, this looks like this:
[root@rhel7-sat-61 foreman]# ll /var/log/foreman
[...]rw-r--r-. 1 foreman foreman 0 12月 13 03:50 production.20151211.logrw-r--r-. 1 foreman foreman 40359 12月 13 03:50 production.20151211.log-20151213rw-rw-r-. 1 foreman foreman 86701 12月 17 07:07 production.logrw-rw-r-. 1 foreman foreman 7196 12月 4 03:09 production.log-20151204.gzrw-rw-r-. 1 foreman foreman 7303 12月 5 03:39 production.log-20151205.gz
[...]
Version-Release number of selected component (if applicable):
foreman in Satellite 6.1
Updated by Dominic Cleal about 8 years ago
- Status changed from Need more information to Feedback
Please check a current release, the logging was changed significantly in 1.9. http://theforeman.org/manuals/1.9/index.html#Releasenotesfor1.9