Managing Large Error Log Files in WordPress: An Essential Guide for Troubleshooting and Maintenance

WordPress sites collect log files quietly: the WordPress debug.log, and PHP's own error_log files in the folders where scripts fail. Left alone, they can grow to hundreds of megabytes, eat your disk space and, in the case of debug.log, expose details anyone can download. This guide shows how to find them, read what they are telling you, and keep them small.

1. Which log files a WordPress site creates

On our cPanel and DirectAdmin servers PHP logs errors by default, so an error_log file can appear even if you never turned anything on. For where each log lives, see reviewing error logs in cPanel and DirectAdmin.

2. Find the large files

• cPanel: the Disk Usage tool shows which folders are largest. In the File Manager, open public_html, public_html/wp-admin and public_html/wp-content and look at the size column for error_log and debug.log.
• DirectAdmin and Webuzo: use the panel's File Manager in the same way.
• SSH: if jailed SSH is enabled on your account, one command lists every large log:

find ~ -type f \( -name 'error_log' -o -name 'debug.log' -o -name '*.error.log' \) -size +10M -exec ls -lh {} \;

A log counts towards your account's disk space like any other file, so a full disk from logs can stop uploads, email and backups.

3. Read the log before you delete it

A large log is almost always the same few lines repeated. Download the file and find the most frequent message rather than scrolling:

# Most repeated messages, with counts, ignoring the timestamp
sed 's/^\[[^]]*\] //' debug.log | sort | uniq -c | sort -rn | head -20

A typical top line looks like this:

  48213 PHP Deprecated:  Creation of dynamic property My_Plugin::$cache is deprecated in /home/youruser/public_html/wp-content/plugins/my-plugin/class-cache.php on line 42

The path tells you the culprit: a folder inside wp-content/plugins/ or wp-content/themes/ names the plugin or theme.

Deprecation notices after a PHP version change are the most common cause of runaway logs. Updating the plugin or theme usually stops them. If no update exists, report it to the developer, and check how to change your PHP version for the versions available.

4. Stop the growth at the source

Step-by-step instructions for the WordPress switches are in how to enable debugging in WordPress.

5. Keep debug.log private if it must stay on

By default debug.log sits at https://yourdomain.com/wp-content/debug.log, where anyone who knows the address can download it. If you need logging on for a while, write the log outside your website by giving WP_DEBUG_LOG a path instead of true:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', '/home/youruser/wp-debug.log' );
define( 'WP_DEBUG_DISPLAY', false );

Replace youruser with your hosting username, shown on the Access tab of your hosting service in the client area. Check the file every few days and empty it once you have read it.

6. Rotating logs

On shared hosting you can't configure the server's logrotate or reload Apache, and PHP code on our servers can't run shell commands, because exec and similar functions are disabled (see PHP disabled functions). So the old advice to rotate logs from a PHP snippet that calls shell commands does not work. Keep logs small by fixing the cause and deleting old files, as above. If you want a scheduled clean-up, ask support what your account can run from the panel's cron jobs.

On your own VPS you control the server, so use logrotate. A file in /etc/logrotate.d/ such as this rotates the log weekly, keeps four compressed copies and truncates in place, so PHP keeps writing to the same file without a web server reload:

/var/www/example.com/wp-content/debug.log {
    weekly
    rotate 4
    compress
    missingok
    notifempty
    copytruncate
}

Better still on a VPS, point WP_DEBUG_LOG at a path outside the web root such as /var/log/wordpress/, owned by the user PHP runs as.

7. Where Domain India hosting fits

Domain India cPanel hosting gives you File Manager, Disk Usage, the error logs and WP Toolkit in one panel, which covers everything in this guide. On a VPS you manage the server yourself, including logrotate; VPS plans are self-managed and come without cPanel. The card shows the live price, excluding 18% GST.

Ready to clean up? Find the largest log, fix what it repeats, then delete it, or open a support ticket if you can't tell what the log is pointing to.