cPanel Cron Job Analysis

Review of your current cron jobs and recommendations

Your Current Cron Jobs

Here's an analysis of your current cron job configuration:

Minute Hour Day Month Weekday Command Frequency
*/15 * * * * /usr/local/bin/php /home1/aurrukwj/public_html/wp-cron.php Every 15 minutes
5 2 * * * /usr/local/bin/php /home1/aurrukwj/public_html/wp-content/plugins/litespeed-cache/cli/purge.cls.php purge_all Daily at 2:05 AM
0 */6 * * * /usr/local/bin/php /home1/aurrukwj/public_html/wp-content/plugins/litespeed-cache/cli/purge.cls.php gc Every 6 hours
0 3 * * 0 /usr/local/bin/php /home1/aurrukwj/public_html/wp-content/plugins/wp-cli/bin/wp db optimize --quiet Weekly on Sunday at 3:00 AM
*/30 6-22 * * * curl -s -H "X-LSCACHE: on" https://jazila-traders.com/ Every 30 minutes from 6 AM to 10 PM

Identified Issues

WordPress Cron Conflict

Your WordPress cron is set to run every 15 minutes, which might be interfering with your news ticker settings.

Potential Issue: WordPress cron may be triggering your crawler more frequently than expected

Cache Warming

The curl command to your homepage is running every 30 minutes during waking hours, which might be affecting performance measurements.

Root Cause Analysis

WordPress has its own internal cron system that works based on site visits. When you set up a server cron job for wp-cron.php, you're essentially triggering WordPress to run its scheduled tasks every 15 minutes.

If your news ticker plugin relies on WordPress cron, it might be executing more frequently than intended.

Recommended Solutions

Step 1: Disable WordPress Internal Cron

Add this to your wp-config.php file to disable the internal WordPress cron:

define('DISABLE_WP_CRON', true);

This will prevent WordPress from running cron on page visits and rely solely on your server cron.

Step 2: Adjust Your Cron Schedule

Change your WordPress cron job to run at your desired interval (e.g., every 4 hours):

# Current (every 15 minutes) */15 * * * * /usr/local/bin/php /home1/aurrukwj/public_html/wp-cron.php > /dev/null 2>&1 # Recommended (every 4 hours) 0 */4 * * * /usr/local/bin/php /home1/aurrukwj/public_html/wp-cron.php > /dev/null 2>&1

Step 3: Check Plugin-Specific Cron Settings

Some plugins have their own cron settings. Check your news ticker plugin settings to ensure it's not configured to run more frequently.

Recommended Cron Setup

After making these changes, your cron jobs should work together harmoniously:

  • WordPress Core: Every 4 hours (0 */4 * * *)
  • LiteSpeed Cache Purge: Daily at 2:05 AM (5 2 * * *)
  • LiteSpeed Cache GC: Every 6 hours (0 */6 * * *)
  • Database Optimization: Weekly on Sunday at 3:00 AM (0 3 * * 0)
  • Cache Warming: Every 30 minutes from 6 AM to 10 PM (*/30 6-22 * * *) - Optional

Additional Recommendations

Monitor Performance

After making these changes, monitor your site's performance to ensure everything works correctly.

Plugin-Specific Cron

If your news ticker plugin has its own cron system, you might need to:

  1. Check the plugin settings for any interval configuration
  2. Look for plugin-specific cron events in WordPress
  3. Consider using a dedicated cron job for the ticker if needed

Cache Considerations

Since you're using LiteSpeed Cache, ensure that your news ticker content is either:

Need More Help?

If you're still experiencing issues after making these changes, please:

  1. Check your news ticker plugin documentation for cron-related settings
  2. Look for any plugin-specific constants or filters that might control scheduling
  3. Consider reaching out to the plugin support team