logrotate:Linux 記錄檔輪替設定與 -d, -f 測試方法
logrotate 是在 Linux 上把持續變大的記錄檔,依設定的週期或大小換成新檔案,並將舊檔案壓縮或刪除的程式。在 AlmaLinux 9 伺服器的測試資料夾中另外建立記錄檔與設定檔,先用 -d 預覽,再用 -f 進行輪替,結果不必動到正式環境的設定,就能確認 rotate、compress、dateext 等設定指令如何改變記錄檔的名稱與數量。
以下輸出是在 AlmaLinux 9.8 伺服器的 root 帳號與 Debian 12 伺服器上執行的結果。運作中的設定檔與計時器只有讀取,輪替測試只在測試資料夾內的記錄檔上進行。測試資料夾的路徑與時間已改為範例值。
1️⃣ logrotate 運作方式
logrotate 是由 systemd 計時器每天執行一次的指令。執行後會依序檢查設定檔中列出的記錄檔,進行輪替後結束。已安裝的版本與預設路徑可用 --version 確認。
logrotate --versionlogrotate 3.18.0
Default mail command: /bin/mail
Default compress command: /bin/gzip
Default uncompress command: /bin/gunzip
Default compress extension: .gz
Default state file path: /var/lib/logrotate/logrotate.status
ACL support: yes
SELinux support: yesAlmaLinux 9.8 伺服器上的 logrotate 是 3.18.0。壓縮使用 /bin/gzip,每個記錄檔最後一次輪替的時間則記錄在 /var/lib/logrotate/logrotate.status 狀態檔中。
每天執行一次的排程寫在 logrotate.timer 中。
systemctl cat logrotate.timer# /usr/lib/systemd/system/logrotate.timer
[Unit]
Description=Daily rotation of log files
Documentation=man:logrotate(8) man:logrotate.conf(5)
[Timer]
OnCalendar=daily
AccuracySec=1h
Persistent=true
[Install]
WantedBy=timers.targetOnCalendar=daily 是每天 0 點執行的排程。依官方手冊,Persistent=true 的設定是:伺服器關機而錯過執行時間時,會在下次開機時立即執行。
systemctl list-timers logrotate.timerNEXT LEFT LAST PASSED UNIT ACTIVATES
Fri 2026-10-30 00:00:00 UTC 14h left Thu 2026-10-29 00:00:00 UTC 9h ago logrotate.timer logrotate.service
1 timers listed.
Pass --all to see loaded but inactive timers, too.NEXT 欄是下次執行時間,LAST 欄是最後一次執行時間。計時器執行的 logrotate.service 中,有一行把正式環境設定檔 /etc/logrotate.conf 傳入。
grep ExecStart /usr/lib/systemd/system/logrotate.serviceExecStart=/usr/sbin/logrotate /etc/logrotate.conf計時器、設定檔與狀態檔的關係如下。
2️⃣ logrotate.conf 預設設定
/etc/logrotate.conf 是設定所有記錄檔共用預設值的檔案。以下讀取了 AlmaLinux 9.8 伺服器的預設檔案。
cat /etc/logrotate.conf# see "man logrotate" for details
# global options do not affect preceding include directives
# rotate log files weekly
weekly
# keep 4 weeks worth of backlogs
rotate 4
# create new (empty) log files after rotating old ones
create
# use date as a suffix of the rotated file
dateext
# uncomment this if you want your log files compressed
#compress
# packages drop log rotation information into this directory
include /etc/logrotate.d
# system-specific logs may be also be configured here.去掉註解後,設定指令共五行。weekly 每週輪替一次,rotate 4 最多保留四個已輪替的檔案。create 在輪替後立即建立同名的空記錄檔,dateext 則在已輪替檔案的名稱結尾加上日期而非數字。compress 被註解掉,因此預設設定不會壓縮。
include /etc/logrotate.d 這一行會依序讀入該資料夾內的檔案。安裝套件時,這個資料夾會產生包含各服務記錄檔路徑與設定指令的檔案,該檔案中沒寫的設定指令則沿用上面的預設值。
如檔案最上方的註解所說,全域設定指令不會套用到位於它前面的 include。要更改預設值時,寫在 include 行的上方。
3️⃣ logrotate 設定指令
各服務的設定,是在記錄檔路徑後的大括號內,每行寫一個設定指令。在測試資料夾用 printf 建立三行的測試記錄檔 app.log,並撰寫了用來輪替該記錄檔的測試設定 test.conf。
cat /home/user/logtest/test.conf/home/user/logtest/logs/app.log {
daily
rotate 3
compress
delaycompress
missingok
notifempty
create 0640 root root
postrotate
echo "postrotate: app.log rotated"
endscript
}常用的設定指令如下。
| 設定指令 | 作用 |
|---|---|
| daily · weekly · monthly | 輪替週期 — 一天 · 一週 · 一個月 |
| rotate 3 | 最多保留 3 個已輪替檔案,更舊的檔案刪除 |
| size 1k | 不論週期,檔案超過 1KB 時輪替(k · M · G) |
| compress | 以 gzip 壓縮已輪替檔案 |
| delaycompress | 剛輪替的檔案在下次輪替時壓縮 |
| missingok | 記錄檔不存在時不報錯,直接略過 |
| notifempty | 空記錄檔不輪替 |
| create 0640 root root | 輪替後立即以權限 · 擁有者 · 群組建立新的空記錄檔 |
| copytruncate | 複製記錄檔保留後,清空原檔案 |
| dateext | 已輪替檔案名稱結尾以日期取代數字 |
| postrotate … endscript | 輪替結束後執行的指令 |
| su 使用者 群組 | 輪替時使用的使用者與群組 |
postrotate 與 endscript 之間寫入輪替結束後要執行的 shell 指令。官方手冊的範例在這裡傳送 HUP 訊號給 syslogd,讓它重新開啟記錄檔。測試設定中只放了一行 echo,用來確認是否有執行。
4️⃣ logrotate -d 測試
-d 是不實際輪替,只讀取設定並輸出判斷哪些記錄檔要輪替之過程的選項。-s 是指定狀態檔路徑的選項。測試時指定了測試資料夾中的 state 檔案,避免與正式環境的狀態檔紀錄混在一起。
logrotate -d -s /home/user/logtest/state /home/user/logtest/test.confWARNING: logrotate in debug mode does nothing except printing debug messages! Consider using verbose mode (-v) instead if this is not what you want.
reading config file /home/user/logtest/test.conf
Reading state from file: /home/user/logtest/state
error: error opening state file /home/user/logtest/state: No such file or directory
Allocating hash table for state file, size 64 entries
Handling 1 logs
rotating pattern: /home/user/logtest/logs/app.log after 1 days (3 rotations)
empty log files are not rotated, old logs are removed
considering log /home/user/logtest/logs/app.log
Creating new state
Now: 2026-10-29 09:39
Last rotated at 2026-10-29 09:00
log does not need rotating (log has already been rotated)第一行的 WARNING 是提示處於除錯模式、不會變更任何東西。error 那一行是因為狀態檔還不存在而出現的。-d 不會建立狀態檔,所以在沒有狀態檔的情況下用 -d 執行時,就會出現這一行。
rotating pattern 行中的 after 1 days (3 rotations) 是讀取 daily 與 rotate 3 的結果。最後一行是 log has already been rotated。正上方的 Now 行是 09:39,Last rotated at 行是 09:00。狀態檔中沒有紀錄的記錄檔,會像這樣把目前時間的整點當作最後輪替時間,因此 daily 記錄檔要到隔天才會成為輪替對象。所以想在修改設定後立即看到結果時,就用 -f 強制輪替。
5️⃣ logrotate -f 強制輪替與 -v 選項
-f 是不論週期與大小條件立即輪替的選項,-v 則逐行輸出輪替過程。以相同的狀態檔與設定,同時加上 -f 與 -v 執行。
logrotate -f -v -s /home/user/logtest/state /home/user/logtest/test.confreading config file /home/user/logtest/test.conf
Creating stub state file: /home/user/logtest/state
Reading state from file: /home/user/logtest/state
Allocating hash table for state file, size 64 entries
Handling 1 logs
rotating pattern: /home/user/logtest/logs/app.log forced from command line (3 rotations)
empty log files are not rotated, old logs are removed
considering log /home/user/logtest/logs/app.log
Creating new state
Now: 2026-10-29 09:39
Last rotated at 2026-10-29 09:00
log needs rotating
rotating log /home/user/logtest/logs/app.log, log->rotateCount is 3
dateext suffix '-20261029'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
previous log /home/user/logtest/logs/app.log.1 does not exist
renaming /home/user/logtest/logs/app.log.3.gz to /home/user/logtest/logs/app.log.4.gz (rotatecount 3, logstart 1, i 3),
old log /home/user/logtest/logs/app.log.3.gz does not exist
renaming /home/user/logtest/logs/app.log.2.gz to /home/user/logtest/logs/app.log.3.gz (rotatecount 3, logstart 1, i 2),
old log /home/user/logtest/logs/app.log.2.gz does not exist
renaming /home/user/logtest/logs/app.log.1.gz to /home/user/logtest/logs/app.log.2.gz (rotatecount 3, logstart 1, i 1),
old log /home/user/logtest/logs/app.log.1.gz does not exist
renaming /home/user/logtest/logs/app.log.0.gz to /home/user/logtest/logs/app.log.1.gz (rotatecount 3, logstart 1, i 0),
old log /home/user/logtest/logs/app.log.0.gz does not exist
log /home/user/logtest/logs/app.log.4.gz doesn't exist -- won't try to dispose of it
renaming /home/user/logtest/logs/app.log to /home/user/logtest/logs/app.log.1
creating new /home/user/logtest/logs/app.log mode = 0640 uid = 0 gid = 0
running postrotate script
postrotate: app.log rotated由於 rotate 3,先出現把編號逐一往後推到 app.log.4.gz 的 renaming 行,接著因為還沒有已輪替的檔案,出現了 does not exist 行。之後把 app.log 改名為 app.log.1,並依照 create 0640 root root 建立新的空 app.log。最後一行是寫在 postrotate 中的 echo 輸出。
ls -l /home/user/logtest/logs/app.log*-rw-r----- 1 root root 0 Oct 29 09:39 /home/user/logtest/logs/app.log
-rw-r--r-- 1 root root 128 Oct 29 09:39 /home/user/logtest/logs/app.log.1新的 app.log 以 create 中寫的 0640 權限建立,app.log.1 則保留了原檔案的權限。
用 printf 在 app.log 結尾多加一行。
printf '2026-10-29 10:00:01 request GET /index.html 200\n' >> /home/user/logtest/logs/app.log接著不加 -v 再執行一次,只出現 postrotate 的 echo 輸出。
logrotate -f -s /home/user/logtest/state /home/user/logtest/test.confpostrotate: app.log rotatedls -l /home/user/logtest/logs/app.log*-rw-r----- 1 root root 0 Oct 29 09:39 /home/user/logtest/logs/app.log
-rw-r----- 1 root root 48 Oct 29 09:39 /home/user/logtest/logs/app.log.1
-rw-r--r-- 1 root root 96 Oct 29 09:39 /home/user/logtest/logs/app.log.2.gz因為 delaycompress,第一次輪替留下的 app.log.1 在這次輪替時被壓縮成 app.log.2.gz,剛輪替的 app.log.1 則維持未壓縮。
空的 app.log 因為 notifempty,即使加上 -f 也沒有輪替。
logrotate -f -v -s /home/user/logtest/state /home/user/logtest/test.confreading config file /home/user/logtest/test.conf
Reading state from file: /home/user/logtest/state
Allocating hash table for state file, size 64 entries
Creating new state
Handling 1 logs
rotating pattern: /home/user/logtest/logs/app.log forced from command line (3 rotations)
empty log files are not rotated, old logs are removed
considering log /home/user/logtest/logs/app.log
Now: 2026-10-29 09:39
Last rotated at 2026-10-29 09:39
log does not need rotating (log is empty)每次在 app.log 加一行並再輪替兩次後,最後一次輪替時第四個檔案 app.log.4.gz 被刪除了。從 -v 輸出中只挑出 removing 行來確認。
logrotate -f -v -s /home/user/logtest/state /home/user/logtest/test.conf 2>&1 | grep removingremoving old log /home/user/logtest/logs/app.log.4.gzls -l /home/user/logtest/logs/app.log*-rw-r----- 1 root root 0 Oct 29 09:39 /home/user/logtest/logs/app.log
-rw-r----- 1 root root 48 Oct 29 09:39 /home/user/logtest/logs/app.log.1
-rw-r----- 1 root root 68 Oct 29 09:39 /home/user/logtest/logs/app.log.2.gz
-rw-r----- 1 root root 66 Oct 29 09:39 /home/user/logtest/logs/app.log.3.gz依照 rotate 3,已輪替的檔案只剩 app.log.1、app.log.2.gz、app.log.3.gz 三個。壓縮檔的內容用 zcat 確認。
zcat /home/user/logtest/logs/app.log.2.gz2026-10-29 11:00:01 request GET /index.html 200狀態檔中,每個記錄檔各有一行,記錄最後一次輪替的日期與時間。
cat /home/user/logtest/statelogrotate state -- version 2
"/home/user/logtest/logs/app.log" 2026-10-29-9:39:9logrotate 下次執行時,會比對這個時間與 daily · weekly 等週期,決定是否輪替。
🔲 logrotate 模擬器
在下方的模擬器中,可以用 -d、-f、-v 執行測試資料夾的 test.conf、size.conf、date.conf、copy.conf,並在 logs 資料夾確認已輪替的檔案。
6️⃣ logrotate size, dateext, copytruncate
size 以檔案大小取代週期來決定是否輪替。對 1,515 位元組的測試記錄檔 size.log,不加 -f 執行寫有 size 1k 的 size.conf。
cat /home/user/logtest/size.conf/home/user/logtest/logs/size.log {
size 1k
rotate 2
missingok
}logrotate -v -s /home/user/logtest/state-size /home/user/logtest/size.confreading config file /home/user/logtest/size.conf
Creating stub state file: /home/user/logtest/state-size
Reading state from file: /home/user/logtest/state-size
Allocating hash table for state file, size 64 entries
Handling 1 logs
rotating pattern: /home/user/logtest/logs/size.log 1024 bytes (2 rotations)
empty log files are rotated, old logs are removed
considering log /home/user/logtest/logs/size.log
Creating new state
Now: 2026-10-29 09:28
Last rotated at 2026-10-29 09:00
log needs rotating
rotating log /home/user/logtest/logs/size.log, log->rotateCount is 2
dateext suffix '-20261029'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
renaming /home/user/logtest/logs/size.log.2 to /home/user/logtest/logs/size.log.3 (rotatecount 2, logstart 1, i 2),
old log /home/user/logtest/logs/size.log.2 does not exist
renaming /home/user/logtest/logs/size.log.1 to /home/user/logtest/logs/size.log.2 (rotatecount 2, logstart 1, i 1),
old log /home/user/logtest/logs/size.log.1 does not exist
renaming /home/user/logtest/logs/size.log.0 to /home/user/logtest/logs/size.log.1 (rotatecount 2, logstart 1, i 0),
old log /home/user/logtest/logs/size.log.0 does not exist
log /home/user/logtest/logs/size.log.3 doesn't exist -- won't try to dispose of it
renaming /home/user/logtest/logs/size.log to /home/user/logtest/logs/size.log.1rotating pattern 行出現 1024 bytes,雖然是新建狀態檔的第一次執行,但因大小超過 1KB 而立即輪替。size.conf 沒有寫 create,因此沒有建立新的 size.log。
把 size.log 重新建立成只有一行的檔案後,執行相同指令,沒有輪替。
logrotate -v -s /home/user/logtest/state-size /home/user/logtest/size.confreading config file /home/user/logtest/size.conf
Reading state from file: /home/user/logtest/state-size
Allocating hash table for state file, size 64 entries
Creating new state
Handling 1 logs
rotating pattern: /home/user/logtest/logs/size.log 1024 bytes (2 rotations)
empty log files are rotated, old logs are removed
considering log /home/user/logtest/logs/size.log
Now: 2026-10-29 09:28
Last rotated at 2026-10-29 09:28
log does not need rotating (log size is below the 'size' threshold)寫上 dateext 後,已輪替檔案名稱結尾會加上日期而非數字。date.conf 中寫了 weekly、rotate 4、dateext、compress。
logrotate -f -v -s /home/user/logtest/state-date /home/user/logtest/date.confreading config file /home/user/logtest/date.conf
Creating stub state file: /home/user/logtest/state-date
Reading state from file: /home/user/logtest/state-date
Allocating hash table for state file, size 64 entries
Handling 1 logs
rotating pattern: /home/user/logtest/logs/date.log forced from command line (4 rotations)
empty log files are rotated, old logs are removed
considering log /home/user/logtest/logs/date.log
Creating new state
Now: 2026-10-29 09:28
Last rotated at 2026-10-29 09:00
log needs rotating
rotating log /home/user/logtest/logs/date.log, log->rotateCount is 4
dateext suffix '-20261029'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
glob finding old rotated logs failed
renaming /home/user/logtest/logs/date.log to /home/user/logtest/logs/date.log-20261029
compressing log with: /bin/gzipls -l /home/user/logtest/logs | grep date-rw-r--r-- 1 root root 56 Oct 29 09:28 date.log-20261029.gz日期以天為單位,所以同一天再次輪替時名稱會重複。在 date.log 加入新的一行,再用 -f 執行一次後,跳過輪替並以結束碼 1 結束。
logrotate -f -v -s /home/user/logtest/state-date /home/user/logtest/date.confreading config file /home/user/logtest/date.conf
Reading state from file: /home/user/logtest/state-date
Allocating hash table for state file, size 64 entries
Creating new state
Handling 1 logs
rotating pattern: /home/user/logtest/logs/date.log forced from command line (4 rotations)
empty log files are rotated, old logs are removed
considering log /home/user/logtest/logs/date.log
Now: 2026-10-29 09:28
Last rotated at 2026-10-29 09:28
log needs rotating
rotating log /home/user/logtest/logs/date.log, log->rotateCount is 4
dateext suffix '-20261029'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
error: destination /home/user/logtest/logs/date.log-20261029.gz already exists, skipping rotationcopytruncate 會把記錄檔複製保留為 .1,然後清空原檔案的內容。由於原檔案保持不動,適用於無法重新開啟記錄檔的程式。
logrotate -f -v -s /home/user/logtest/state-copy /home/user/logtest/copy.confreading config file /home/user/logtest/copy.conf
Creating stub state file: /home/user/logtest/state-copy
Reading state from file: /home/user/logtest/state-copy
Allocating hash table for state file, size 64 entries
Handling 1 logs
rotating pattern: /home/user/logtest/logs/copy.log forced from command line (2 rotations)
empty log files are rotated, old logs are removed
considering log /home/user/logtest/logs/copy.log
Creating new state
Now: 2026-10-29 09:28
Last rotated at 2026-10-29 09:00
log needs rotating
rotating log /home/user/logtest/logs/copy.log, log->rotateCount is 2
dateext suffix '-20261029'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
renaming /home/user/logtest/logs/copy.log.2 to /home/user/logtest/logs/copy.log.3 (rotatecount 2, logstart 1, i 2),
old log /home/user/logtest/logs/copy.log.2 does not exist
renaming /home/user/logtest/logs/copy.log.1 to /home/user/logtest/logs/copy.log.2 (rotatecount 2, logstart 1, i 1),
old log /home/user/logtest/logs/copy.log.1 does not exist
renaming /home/user/logtest/logs/copy.log.0 to /home/user/logtest/logs/copy.log.1 (rotatecount 2, logstart 1, i 0),
old log /home/user/logtest/logs/copy.log.0 does not exist
log /home/user/logtest/logs/copy.log.3 doesn't exist -- won't try to dispose of it
copying /home/user/logtest/logs/copy.log to /home/user/logtest/logs/copy.log.1
truncating /home/user/logtest/logs/copy.logls -l /home/user/logtest/logs | grep copy-rw-r--r-- 1 root root 0 Oct 29 09:28 copy.log
-rw-r--r-- 1 root root 72 Oct 29 09:28 copy.log.1copy.log 變成 0 位元組,內容移到了 copy.log.1。官方手冊寫道,在複製與清空之間寫入的行可能會遺失,因此對於可以讓它重新開啟記錄檔的服務,使用 create 與 postrotate。
7️⃣ 確認 logrotate 錯誤
logrotate 不輪替記錄檔時,用 -d 執行相同設定,確認 considering log 下方的最後一行。測試中出現的訊息有四種。
| considering log 下方的最後一行 | 說明 |
|---|---|
| log needs rotating | 輪替對象 |
| log does not need rotating (log has already been rotated) | 週期尚未經過 · 狀態檔中首次記錄的記錄檔 |
| log does not need rotating (log is empty) | 設有 notifempty 且記錄檔為空檔案 |
| log does not need rotating (log size is below the 'size' threshold) | 小於 size 中寫的大小 |
記錄檔不存在時,由 missingok 決定結果。沒有 missingok 卻寫了不存在檔案的 miss.conf 以錯誤結束。
logrotate -f -s /home/user/logtest/state-miss /home/user/logtest/miss.conferror: stat of /home/user/logtest/logs/none.log failed: No such file or directory對相同路徑加上 missingok 的 miss2.conf,留下 does not exist -- skipping 行,並以結束碼 0 結束。
存放記錄檔的資料夾權限過於開放時,也不會輪替。在測試資料夾內建立權限為 777 的 logs-open 資料夾,輪替其中的記錄檔後,出現以下錯誤。
logrotate -f -s /home/user/logtest/state-open /home/user/logtest/open.conferror: skipping "/home/user/logtest/logs-open/open.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.依照錯誤訊息,在設定中用 su 設定指令寫上輪替時使用的使用者與群組後,同一個記錄檔就輪替了。
cat /home/user/logtest/open2.conf/home/user/logtest/logs-open/open.log {
su root root
daily
rotate 2
}logrotate -f -s /home/user/logtest/state-open /home/user/logtest/open2.conf這次沒有錯誤就結束了,logs-open 資料夾中出現了 open.log.1。
ls -l /home/user/logtest/logs-opentotal 4
-rw-r--r-- 1 root root 5 Oct 29 09:28 open.log.1設定檔中的設定指令寫錯時,logrotate 只會捨棄那一行,用其餘設定指令執行。用 -d 讀取了把 rotate 寫成 rotat 的 bad.conf。
logrotate -d -s /home/user/logtest/state-bad /home/user/logtest/bad.confWARNING: logrotate in debug mode does nothing except printing debug messages! Consider using verbose mode (-v) instead if this is not what you want.
reading config file /home/user/logtest/bad.conf
error: /home/user/logtest/bad.conf:3 unknown option 'rotat' -- ignoring line
Reading state from file: /home/user/logtest/state-bad
error: error opening state file /home/user/logtest/state-bad: No such file or directory
Allocating hash table for state file, size 64 entries
Handling 1 logs
rotating pattern: /home/user/logtest/logs/app.log after 1 days (no old logs will be kept)
empty log files are rotated, old logs are removed
considering log /home/user/logtest/logs/app.log
Creating new state
Now: 2026-10-29 09:33
Last rotated at 2026-10-29 09:00
log does not need rotating (log has already been rotated)錯誤行中顯示了檔案名稱與行號,而且因為少了 rotate 行,被讀成 (no old logs will be kept)。照這樣輪替的話,一個舊記錄檔都不會保留,所以修改設定後,先用 -d 從 rotating pattern 行開始確認。
🔢 FAQ & 推薦內容
ℹ️ 聯盟行銷說明
本站內容包含聯盟行銷連結。訪客透過這些連結購買商品或服務時,本站會從賣家獲得佣金。在這個過程中,購買者支付的金額(遇到活動折扣時金額會降低↓)並不會因此提高。刊登的價格、折扣與庫存資訊以撰寫當時為準,可能與實際情況不同,購買前請向賣家做最後確認。商品的挑選與評價依本站自訂的標準撰寫,是否支付佣金不會影響介紹順序或評價內容。