logrotation for wordpress logs

Question

我正在尝试为WordPress日志文件启用日志轮换。我需要启用日志轮换，30天后需要压缩并存档，60天后需要删除。

我在/etc/logrotate.d文件夹中创建了一个文件app.conf，内容如下：

/var/www/firebolt-app/wp-content/*.log {
weekly
rotate 4
maxage 90
}

然后我运行了logrorate -d app.conf，它没有出现在logrotate状态，调试文件中也没有更改。

在/var/log中的文件中是否会发生类似于-只旋转的情况？

Answer 1

我知道这有点死灵术，但对于数百人来说，我在worpress-ubuntu 22-上做了一个工作日志轮换方案

sudo nano /etc/logrotate.d/wordpress

其中包括logrotate命令，我使用了这些命令：

/var/www/<WPsite>/wp-content/*.log {
daily
missingok
rotate 14
compress
delaycompress
notifempty
create 666 <user> <group>
}

测试对象：

sudo logrotate -d -f /etc/logrotate.conf

• -d=打开调试模式(模拟操作，无实际更改(
• -f=强制旋转文件(以检查它是否真正接触到所需的日志(

工作正常：

rotating log /var/www/<WPSITE>/wp-content/debug.log, log->rotateCount is 14
dateext suffix '-20221129'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
previous log /var/www/<WPSITE>/wp-content/debug.log.1 does not exist
renaming /var/www/<WPSITE>/wp-content/debug.log.14.gz to /var/www/<WPSITE>/wp-content/debug.log.15.gz (rotatecount 14, logstart 1, i 14),
renaming /var/www/<WPSITE>/wp-content/debug.log.13.gz to /var/www/<WPSITE>/wp-content/debug.log.14.gz (rotatecount 14, logstart 1, i 13),
renaming /var/www/<WPSITE>/wp-content/debug.log.12.gz to /var/www/<WPSITE>/wp-content/debug.log.13.gz (rotatecount 14, logstart 1, i 12),
renaming /var/www/<WPSITE>/wp-content/debug.log.11.gz to /var/www/<WPSITE>/wp-content/debug.log.12.gz (rotatecount 14, logstart 1, i 11),
renaming /var/www/<WPSITE>/wp-content/debug.log.10.gz to /var/www/<WPSITE>/wp-content/debug.log.11.gz (rotatecount 14, logstart 1, i 10),
renaming /var/www/<WPSITE>/wp-content/debug.log.9.gz to /var/www/<WPSITE>/wp-content/debug.log.10.gz (rotatecount 14, logstart 1, i 9),
renaming /var/www/<WPSITE>/wp-content/debug.log.8.gz to /var/www/<WPSITE>/wp-content/debug.log.9.gz (rotatecount 14, logstart 1, i 8),
renaming /var/www/<WPSITE>/wp-content/debug.log.7.gz to /var/www/<WPSITE>/wp-content/debug.log.8.gz (rotatecount 14, logstart 1, i 7),
renaming /var/www/<WPSITE>/wp-content/debug.log.6.gz to /var/www/<WPSITE>/wp-content/debug.log.7.gz (rotatecount 14, logstart 1, i 6),
renaming /var/www/<WPSITE>/wp-content/debug.log.5.gz to /var/www/<WPSITE>/wp-content/debug.log.6.gz (rotatecount 14, logstart 1, i 5),
renaming /var/www/<WPSITE>/wp-content/debug.log.4.gz to /var/www/<WPSITE>/wp-content/debug.log.5.gz (rotatecount 14, logstart 1, i 4),
renaming /var/www/<WPSITE>/wp-content/debug.log.3.gz to /var/www/<WPSITE>/wp-content/debug.log.4.gz (rotatecount 14, logstart 1, i 3),
renaming /var/www/<WPSITE>/wp-content/debug.log.2.gz to /var/www/<WPSITE>/wp-content/debug.log.3.gz (rotatecount 14, logstart 1, i 2),
renaming /var/www/<WPSITE>/wp-content/debug.log.1.gz to /var/www/<WPSITE>/wp-content/debug.log.2.gz (rotatecount 14, logstart 1, i 1),
renaming /var/www/<WPSITE>/wp-content/debug.log.0.gz to /var/www/<WPSITE>/wp-content/debug.log.1.gz (rotatecount 14, logstart 1, i 0),
log /var/www/<WPSITE>/wp-content/debug.log.15.gz doesn't exist -- won't try to dispose of it
renaming /var/www/<WPSITE>/wp-content/debug.log to /var/www/<WPSITE>/wp-content/debug.log.1
creating new /var/www/<WPSITE>/wp-content/debug.log mode = 0666 uid = 1001 gid = 1003
switching euid from 0 to 0 and egid from 4 to 0 (pid 119221)

ubuntu上的logrotate由cron.daily控制，由主crontab 于协调世界时6.25分启动