Truncate a runaway wp-content/debug.log

Symptom

BoltAudit reports wp-content/debug.log is larger than 50 MB, or the audit's I/O probe shows the file growing during the scan. Often paired with high disk-I/O reports from the host.

Impact

• Every error_log() call appends to the file — a 500 MB log makes every write slower (the OS keeps tail metadata hot but appends still flush).
• The file is included in backups and FTP downloads, wasting bandwidth.
• Real errors get lost in repetitive plugin notices.

Manual fix

CODE0

Apply Fix

One-click in the dashboard. The fix truncates the file to zero bytes — your logging continues working, you just start fresh.

When not to apply

Don't truncate if you're mid-investigation of a specific error. Grep for the relevant message first, save what you need, then truncate.

Better long-term

Treat the size as a symptom, not the issue. If the log keeps growing, fix the noisiest source:

CODE1

The top lines are your real bugs.