Ubuntu .log.gz 上的 Tomcat8 已经存在未覆盖 [英] Tomcat8 on Ubuntu .log.gz already exists not overwritten

问题描述

在我们的 Tomcat 服务器上，我经常看到如下警告:

On our Tomcat servers I regularly see warnings like below:

/etc/cron.daily/tomcat8:
gzip: /var/log/tomcat8/app1/app1.log.gz already exists; not overwritten
gzip: /var/log/tomcat8/app2/app2.log.gz already exists; not overwritten
gzip: /var/log/tomcat8/app3/app3.log.gz already exists; not overwritten
gzip: /var/log/tomcat8/app4/app4.log.gz already exists; not overwritten

我发现了与 Tomcat7 logrotate: superx_default_xml.log.gz 已经存在 但是从未提供答案.

I found a similar issue as discussed in Tomcat7 logrotate: superx_default_xml.log.gz already exists however an answer was never provided.

虽然在寻找答案，但我似乎无法找到解决此问题的方法，希望这里有人能指出我正确的方向.

Although search for an answer I can't seem to find a solution for this problem and was hoping if someone here could point me in the right directlion.

我们正在 Ubuntu 16.04.1 LTS 上的 Tomcat8 服务器上运行我们的 Tomcat 8 服务器.

We are running our Tomcat 8 servers on Tomcat8 servers on Ubuntu 16.04.1 LTS.

亲切的问候.

推荐答案

我的 2cents 解决方案:

My 2cents solution:

在/etc/default/tomcat8 中添加以下行

Add the following line in /etc/default/tomcat8

LOGEXT="20[0-9][0-9]-[0-9][0-9]-[0-9][0-9].log log.20[0-9][0-9]-[0-9][0-9]-[0-9][0-9] txt"

这将选择用于压缩和清除的文件，例如

This will select, for compression and purging, files like

/var/log/tomcat8/localhost.2019-09-09.log
/var/log/tomcat8/app1/app1.log.2019-09-09
/var/log/tomcat8/localhost_access_log.2019-09-09.txt

并留下 app1.log 文件，这些文件可能会被 log4j appender 重命名.

and leave alone app1.log files, which presumably will be renamed by a log4j appender.

因此 /etc/cron.daily/tomcat8 不需要更改.

适用于 Debian 9 (stretch) 发行版的 tomcat8.天啊.

Works with the tomcat8 of the Debian 9 (stretch) distribution. YMMV.

这篇关于Ubuntu .log.gz 上的 Tomcat8 已经存在未覆盖的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！