Observed Signal · Aug 19, 2026 · Technical Release · Source: DEV Community · Impact: 1/5 · Sentiment: Positive
Laravel Queue Stopped — Root Cause Was PHP-FPM
A developer debugging a Laravel application on a cPanel server discovered that recurring queue stoppages and Make.com request timeouts were caused by infrastructure issues rather than the queue itself. The queue worker had been started with nohup and disappeared after server restarts; moving execution to a cPanel Cron job with /bin/flock and --stop-when-empty made the worker lifecycle more resilient. Separately, slow or queued HTTP requests were traced to an overly conservative PHP-FPM configuration (pm.max_children = 5, pm.max_requests = 20, pm.process_idle_timeout = 10) on a 65 GB / 20-core server. The author recommends tuning PHP-FPM to match server capacity and diagnosing each layer independently.
Practical engineering post describing queue-worker lifecycle and PHP-FPM tuning; useful for ops but not industry-shifting for AdTech/MarTech.
Track Make Signals & Market Shifts in Real-Time
Polaris7 autonomous intelligence agents track regulatory filings, primary sources, executive changes, and deal flow 24/7. Create your free Explorer workspace to monitor these entities.
Key Takeaways & Evidence Grounding
- Laravel application ran on a cPanel server and used Redis for queueing.
- Initial queue worker was started with nohup and was killed by server restarts, requiring manual restarts.
- Queue execution was moved to cPanel Cron using /bin/flock and php artisan queue:work with --stop-when-empty.
- PHP-FPM was configured with pm.max_children = 5, pm.max_requests = 20, pm.process_idle_timeout = 10, creating an HTTP request capacity bottleneck despite abundant server RAM/CPU.
- Fixes included Cron-managed workers and tuning PHP-FPM to match actual server resources and workload.
Connected Companies & Entities
3 Entities mapped“The application also had an integration with Make.com. Make.com periodically sent requests to the Laravel application, which then dispatched...”
“This is a submission for DEV's Summer Bug Smash: Clear the Lineup powered by Sentry....”
“This is a submission for DEV's Summer Bug Smash: Clear the Lineup powered by Sentry....”
Ontology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
Tuning PHP-FPM for Laravel Performance
This technical guide explains how to tune PHP-FPM for Laravel applications, covering process manager modes (static, dynamic, ondemand), how PHP-FPM worker processes handle requests, and the key settings that determine throughput and stability. It provides a formula for calculating pm.max_children from available RAM and average worker memory, guidance on PHP memory_limit, pm.max_requests for process recycling, request timeouts, and slow-log configuration for diagnosing slow requests. The article includes recommended example configurations for 1GB, 2GB, 4GB and 8GB servers (Deploynix-managed), monitoring tips using the PHP-FPM status page and Deploynix integration, and validation/restart/test commands (php-fpm8.4 -t, systemctl restart, wrk/ab). Practical recommendations emphasize measuring real worker memory, leaving headroom, and iterating based on observability metrics.
PHP-FPM Tuning: 5 Settings That Decide p99
A technical guide explains five php-fpm configuration settings that heavily influence p99 latency for PHP web apps: pm.max_children, pm.max_requests, request_terminate_timeout, pm.process_idle_timeout (ondemand only), and listen.backlog. The author explains how to calculate pm.max_children from available RAM and average worker RSS, why pm.max_requests protects against memory growth, why request_terminate_timeout is the reliable kill switch, when ondemand is appropriate, and how listen.backlog interacts with the kernel (net.core.somaxconn) during bursts. A real-world c5.large Laravel 12 tuning example shows p99 improving from ~4800ms to ~380ms after switching to static pools, lowering max_children and increasing backlog and recycle settings. The article also summarizes when to consider Laravel Octane as an architectural alternative after tuning.
Stuck Postgres Lock Caused Site Outage; One-Line Fix
A developer's site returned HTTP 500 on every request due to a Postgres lock timeout (error 55P03) occurring while a background worker tried to create a pg-boss queue during process boot. Because the worker boot was awaited inside a Next.js instrumentation hook, the worker failure aborted the whole server. The immediate recovery was to restart Postgres and redeploy; the long-term fix was to start the worker in a fire-and-forget fashion and add a resilient retry loop that only marks the worker as started after a successful boot.
Track Real-Time Market Signals & Shifts
Set up custom watchlists to receive automated, evidence-grounded executive digests whenever material signals or shifts occur across your tracked landscape.