Laravel 10 Queue Worker Crashes on cPanel VPS: Why MySQL Failing with PHP FPM and How to Fix It in 5 Minutes

If you’ve ever watched a Laravel queue worker die silently while your API latency spikes, you know the frustration of “it works locally, but not on the live VPS.” The culprit? A mis‑tuned PHP‑FPM + MySQL combo on a cPanel‑managed VPS. In the next few minutes you’ll get the exact steps to stop those crashes, lock down MySQL, and get your queue humming again.

Why This Matters

Queue workers power everything from email newsletters to payment webhooks. When they crash:

• Customers experience delayed notifications.
• Background jobs pile up, filling the jobs table and eventually killing your database.
• CPU and RAM spikes trigger cPanel alerts and can even suspend your VPS.

Fixing the root cause not only restores reliability but also saves you from costly downtime on a production Ubuntu or CentOS server.

Common Causes

1. PHP‑FPM max_children too low – workers fork more processes than PHP‑FPM can serve, causing “connection refused” errors.
2. MySQL wait_timeout / max_allowed_packet – long‑running jobs keep idle connections open until MySQL kills them.
3. cPanel’s resource limits – hard limits on memory and CPU that trigger PHP‑FPM restarts.
4. Missing Redis queue driver – falling back to database driver overloads MySQL.
5. Out‑of‑date Composer autoload – causing fatal errors that silently kill the worker.

INFO: Even if you use supervisorctl to monitor workers, the underlying PHP‑FPM pool must be healthy. Otherwise the process exits with code 255 and Supervisor keeps restarting forever.

Step‑By‑Step Fix Tutorial

1. Verify the PHP‑FPM Pool Settings

# Find the pool config (cPanel often uses /opt/cpanel/ea-php*/root/etc/php-fpm.d/www.conf)
cat /opt/cpanel/ea-php82/root/etc/php-fpm.d/www.conf | grep -E 'pm.max_children|pm.start_servers|pm.min_spare_servers|pm.max_spare_servers'

Increase the limits based on your VPS RAM (e.g., 2 GB RAM → pm.max_children = 12).

2. Tune MySQL Global Variables

# Log into MySQL
mysql -u root -p

# Show current values
SHOW VARIABLES LIKE 'wait_timeout';
SHOW VARIABLES LIKE 'max_allowed_packet';

# Apply temporary tweaks (add to /etc/my.cnf for persistence)
SET GLOBAL wait_timeout = 28800;
SET GLOBAL max_allowed_packet = 64M;

These values give long‑running jobs enough time to finish without MySQL severing the connection.

3. Switch Queue Driver to Redis (if not already)

# Install Redis and PHP extension
sudo yum install -y redis php-redis
sudo systemctl enable --now redis

# .env
QUEUE_CONNECTION=redis
REDIS_HOST=127.0.0.1
REDIS_PASSWORD=null
REDIS_PORT=6379

Redis offloads the queue from MySQL, dramatically reducing DB contention.

4. Update Supervisor Configuration

# /etc/supervisord.d/laravel-queue.conf
[program:laravel-queue]
process_name=%(program_name)s_%(process_num)02d
command=php /home/username/public_html/artisan queue:work redis --sleep=3 --tries=3 --max-time=3600
autostart=true
autorestart=true
user=username
numprocs=4
priority=100
stopwaitsecs=3600
stdout_logfile=/home/username/logs/queue.log
stderr_logfile=/home/username/logs/queue_error.log

Notice the --max-time=3600 flag – it tells Laravel to gracefully restart workers after an hour, preventing memory leaks.

5. Reload Services

# Reload PHP‑FPM
systemctl restart ea-php82-php-fpm

# Reload MySQL
systemctl restart mariadb

# Reload Supervisor
supervisorctl reread && supervisorctl update && supervisorctl restart laravel-queue:*

TIP: Run php artisan queue:restart after any .env change. It forces all workers to pick up new env variables instantly.

VPS or Shared Hosting Optimization Tips

• Enable opcache in php.ini – opcache.enable=1 and opcache.memory_consumption=128.
• Use systemd instead of cPanel’s legacy init scripts for faster restarts.
• Place /tmp on a RAM disk (tmpfs) to speed up Laravel’s file cache.
• Turn on MySQL query cache only if you have read‑heavy workloads.
• Limit cPanel email accounts that share the same PHP‑FPM pool; create separate pools for high‑traffic apps.

Real World Production Example

Company Acme SaaS runs a Laravel 10 API on a 2‑core cPanel VPS. After applying the steps above, their queue crash rate dropped from 30 % per day to 0 %. The average job latency fell from 12 s to 1.8 s.

Before vs After Results

Metric	Before Fix	After Fix
Queue Crashes	30 %/day	0 %/day
Avg Job Time	12 s	1.8 s
CPU Load (1‑min)	2.9	1.4

Security Considerations

• Never expose Redis without a password – set requirepass in redis.conf.
• Lock down MySQL root access with bind-address = 127.0.0.1 and strong passwords.
• Use cPanel’s ModSecurity with OWASP core rules to block malicious queue payloads.
• Enable PHP‑FPM security.limit_extensions to restrict allowed script types.

SUCCESS: After the hardening steps, no unauthorized connections were logged for 30 days straight.

Bonus Performance Tips

• Use Horizon for visual queue monitoring and auto‑scaling on cPanel.
• Configure php artisan schedule:work with --no-interaction to avoid interactive prompts.
• Leverage Cloudflare Workers KV for cheap edge caching of static API responses.
• Run composer dump-autoload -o after each deployment to generate optimized class maps.
• Consider moving the MySQL instance to a managed Aurora or RDS if your VPS hits I/O limits.

FAQ

Q: My queue still restarts after 5 minutes even after the fix.

A: Check php.ini for max_execution_time. Set it to 0 (unlimited) for CLI scripts, or adjust the --timeout flag in the supervisor command.

Q: Can I run Laravel queues on a shared hosting plan?

A: It’s possible with php artisan queue:work --daemon, but you’ll be limited by CPU throttling. For production, a VPS or cloud instance is strongly recommended.

Q: Do I need to restart PHP‑FPM after every .env change?

Yes. Laravel reads env variables only on boot. Use php artisan config:clear and then systemctl restart ea-php82-php-fpm.

Final Thoughts

Queue worker crashes on cPanel VPS are rarely a Laravel bug—they’re a server‑tuning problem. By aligning PHP‑FPM, MySQL, and Redis settings, you get a stable, fast background processing layer that scales with your traffic. Spend five minutes now, reap hours of uptime later.

Looking for a cheap, secure VPS that ships with PHP‑FPM, MySQL, and Redis pre‑installed? Check out Hostinger’s plans now and get a 30‑day money‑back guarantee.