Do not raise MaxRequestWorkers as your first reaction. The message means Apache has reached its configured ceiling for simultaneous requests. That can indicate a ceiling that is too low, but it can also be the visible symptom of slow upstream requests, excessive keep-alive connections, memory pressure, a faulty module, or a crashing child process. Capture the logs, identify the active multi-processing module (MPM), check CPU and memory capacity, and then make one measured, reversible change.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
On Ubuntu, the reliable sequence is: preserve the failure evidence, identify whether Apache uses mpm_prefork, mpm_worker, or mpm_event, run a configuration test, determine whether capacity or a crash is the primary fault, apply MPM-appropriate limits, and verify the result under representative traffic.
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →What the MaxRequestWorkers message means
Apache’s MaxRequestWorkers directive sets the maximum number of simultaneous requests Apache will serve. Once that number is occupied, a new request cannot immediately obtain a worker process or thread. It may wait, queue, or fail depending on the rest of the configuration and the duration of the existing requests.
The unit depends on the active MPM:
- prefork: the value is the maximum number of Apache child processes.
- worker: the value is the total number of request-handling threads across the child processes.
- event: the value is also the total thread ceiling, with the MPM designed to handle idle keep-alive connections more efficiently than a process-per-request model.
Hitting the limit does not prove that the number should be increased. If each process or thread is waiting on a slow application, proxy, database, or network operation, raising the ceiling simply allows more waiting work and consumes more memory. Apache’s own guidance warns that values beyond what the host can handle can prevent startup or make the system unstable.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
Capture the failure before editing Apache
Collect evidence while the failure is still visible. Keep timestamps in every log so an Apache event can be compared with kernel and application messages.
- Check the service state:
sudo systemctl status apache2 --no-pager - Read this boot’s service journal:
sudo journalctl -u apache2 -b --no-pager - Inspect Apache’s error log, normally
/var/log/apache2/error.logunless the configuredErrorLogpoints elsewhere. - Search the Apache and system logs for
AH00161,MaxRequestWorkers,segfault,child pid,out of memory,OOM,signal,proxy_fcgi, and the names of recently changed modules.
The Apache Software Foundation describes the server error log as the first place to look when a problem occurs while starting or running the server. A startup syntax error, a module-load failure, a child-process crash, and worker exhaustion often leave different signatures, so do not rely on the single MaxRequestWorkers line.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsHow to read the signatures
A repeated MaxRequestWorkers entry indicates that all configured workers were occupied at that moment; it does not identify what kept them busy. Pair the timestamp with access-log request duration, upstream logs, and system resource observations. An AH00161 entry is especially useful when Apache reports that it reached the ceiling, while segfault, signal, or repeated child-PID exits point toward a crash path. Messages containing out of memory or OOM require kernel and service correlation before any limit is raised.
Identify the active MPM and loaded modules
Run both commands before changing a limit:
apache2ctl -M
apache2ctl -VLook for exactly one of mpm_prefork, mpm_worker, or mpm_event. Apache requires one MPM and only one; attempting to load more than one produces a startup configuration error. Modern Ubuntu installations commonly use the event MPM, but the enabled choice is determined by the installed configuration rather than by the Ubuntu name alone.
On Ubuntu, inspect /etc/apache2/mods-enabled/ and the enabled MPM symlink to confirm what the service will load. Record the current MPM, its limit directives, and the module list before touching them. A switch from prefork to worker or event can affect PHP integrations and other modules: verify thread-safety first, and make the change only in a controlled maintenance window with a documented rollback.
Validate configuration before a reload or restart
Run a syntax check after every edit:
sudo apache2ctl configtestDo not reload until this reports a valid configuration. Fix duplicate directives, missing files, syntax mistakes, and module-load errors first. Keep the previous configuration so you can restore it quickly.
Recommended Free Tools
When the change does not require rebuilding the process model, apply it with:
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
sudo systemctl reload apache2Use a full restart only when the module or process-model change requires it. Immediately check the service state and error log after either operation. A limit increase that makes Apache fail to start is not a repair.
Decide whether capacity is the symptom or the cause
Before selecting a new number, compare the MaxRequestWorkers events with request latency, keep-alive behavior, upstream wait time, CPU, RAM, swap activity, process counts, and HTTP 5xx responses. The important question is whether Apache is busy doing useful work or merely holding connections open while another component is slow.
Signs that the ceiling may be too low
- Requests are healthy and short when capacity is available, but traffic peaks repeatedly consume every worker.
- CPU and memory remain within safe levels while requests queue at the limit.
- Upstream services respond promptly and there is no evidence of child crashes or kernel out-of-memory activity.
- Observed concurrency is consistently close to the configured value during normal peaks.
Signs that raising it is dangerous
- Resident memory rises with every additional child or process group, or the host begins swapping.
- The kernel reports OOM activity, Apache children are killed, or the service becomes unstable after concurrency rises.
- Requests remain blocked on PHP, a proxy backend, a database, or another upstream service.
- Keep-alive connections occupy workers for long periods without corresponding application throughput.
- Apache logs show segmentation faults, signals, or repeated child-PID exits.
For prefork, measure the real resident memory of Apache children with the complete production module set. Leave headroom for the operating system, databases, PHP-FPM, proxies, and monitoring. For worker and event, account for both per-process memory and thread behavior, including stack and module requirements. Any memory estimate is only a starting point: confirm it against observed resident memory and the actual workload.
Separate queueing from saturation
A queue at the ceiling can result from a brief traffic burst or from requests whose service time has increased. Compare the periods immediately before and during the warning: if latency and upstream wait time rose first, the worker limit is likely exposing a bottleneck elsewhere. If requests remain short, upstreams are healthy, and memory stays comfortably below capacity while the same peak repeatedly fills the pool, a cautiously higher ceiling may be justified. Record both peak concurrency and the conditions under which it occurred; a single instantaneous count is not enough to choose a permanent value.
Apply MPM-specific limits
| MPM | What MaxRequestWorkers counts | Documented Apache value or relationship | Tuning constraint |
|---|---|---|---|
| prefork | Child processes | Default 256 in current Apache 2.5 module documentation (Apache Software Foundation, 2026) | Values above 256 require a suitable ServerLimit; each process can consume substantial memory. |
| worker | Total request threads | Documented relationship: 16 ServerLimit × 25 ThreadsPerChild = 400 MaxRequestWorkers |
The value should respect ThreadsPerChild and normally be an integer multiple. |
| event | Total request threads | Documented relationship: 16 ServerLimit × 25 ThreadsPerChild = 400 MaxRequestWorkers |
The value should respect ThreadsPerChild and normally be an integer multiple. |
These are Apache documentation defaults, not guarantees for every Ubuntu release. Verify the installed Apache version and active configuration before treating them as current settings.
Prefork
With prefork, increasing MaxRequestWorkers permits more child processes. If the documented default of 256 is exceeded, ServerLimit must provide a corresponding ceiling. Raise both only when measured memory and workload data justify it. A high process count can exhaust RAM long before CPU reaches saturation.
Worker and event
These MPMs count threads. MaxRequestWorkers must be at least ThreadsPerChild and should be an integer multiple of it. If an invalid value is supplied, Apache rounds it down and logs a warning. For example, a value that does not divide evenly into the configured thread count will not provide the concurrency you intended. Check the effective values in the startup log after reloading.
Rank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
ServerLimit
ServerLimit is a process ceiling, not a substitute for measuring capacity. Apache warns that unnecessarily high values allocate extra shared memory and that setting both ServerLimit and MaxRequestWorkers above system capacity can prevent startup or destabilize the host. Increase it only when the selected MPM and a justified worker ceiling require it.
A safe, reversible tuning procedure
- Write down the baseline. Record the active MPM,
ServerLimit,ThreadsPerChild,MaxRequestWorkers, current RAM and swap use, peak observed concurrency, latency, and 5xx rate. - Choose one variable. Do not change the MPM, process limit, thread limit, keep-alive behavior, and upstream settings in the same experiment. A single change makes its effect identifiable.
- Check MPM rules. For prefork, confirm the required
ServerLimitif the new value is above 256. For worker or event, choose a value compatible withThreadsPerChild. - Edit the active configuration. Change the file that actually supplies the directive, not an unused example or disabled module file. Keep the old value ready for rollback.
- Run the configuration test.
sudo apache2ctl configtest - Reload when possible.
sudo systemctl reload apache2 - Watch the result. Follow the Apache error log and service journal while monitoring RAM, swap, CPU, latency, 5xx responses, and upstream health.
- Roll back on instability. If swapping, OOM activity, repeated child exits, or worse latency appears, restore the previous value and reload. Investigate the memory-heavy module or upstream service instead of continuing to raise the ceiling.
Keep a rollback record
Save the previous enabled configuration, note the exact directive file, and write down the command that restores it. Record the time of the change and the first post-change observations. This makes it possible to distinguish a limit effect from a coincidental traffic or upstream change and prevents a second operator from guessing which MPM and values were active.
Investigate crashes independently from worker exhaustion
A MaxRequestWorkers message and a crash can occur in the same incident without one proving the other caused it. Treat crash signatures as a separate branch of the investigation.
Segmentation faults, signals, and child exits
Correlate segfault, signal, and repeated child pid entries with journalctl -k, core-dump records, and the loaded module list. Note the exact time and process ID. A child that repeatedly exits may indicate a faulty module, an integration problem, or memory exhaustion rather than an undersized worker ceiling.
Free tools Windows power users keep installed
One-click scans. No signup required.
Modules and integrations to isolate
In a controlled maintenance window, temporarily disable or isolate recently changed third-party modules, PHP integrations, proxy backends, and protocol features. Change one component at a time and keep the MPM and concurrency edits reversible. If crashes stop when one module or integration is removed, the evidence points away from simply raising MaxRequestWorkers.
Kernel out-of-memory events
When the kernel reports OOM activity, reduce concurrency and identify what consumes memory. Increasing Apache’s limits in response to an OOM event gives the kernel more processes or threads to kill. Check Apache, PHP-FPM, databases, proxies, and monitoring together because they share the host’s memory budget.
When an MPM change is appropriate
Changing from prefork to worker or event is an architectural decision, not a quick response to one warning. Compare the alternatives on the following axes:
Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
| Decision factor | Questions to answer |
|---|---|
| Compatibility | Are PHP and every loaded module safe for the target MPM? |
| Memory | What is the measured memory per process and the behavior of each thread under peak traffic? |
| Concurrency | Will the change reduce queueing, or merely permit more blocked requests? |
| Connection behavior | Are keep-alive connections or upstream waits consuming the current workers? |
| Crash evidence | Do logs implicate a module or process model rather than a numerical ceiling? |
| Rollback | Can the former MPM, module set, and limits be restored quickly? |
| Measured outcome | After the change, do latency, memory, and 5xx rates improve under representative traffic? |
Do not switch MPM during an active outage unless you have verified module compatibility and a tested rollback. A process-model change can replace one failure mode with a startup failure or thread-safety crash.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Common failure patterns and the right response
“I raised MaxRequestWorkers and Apache crashed again”
Check resident memory, swap, and kernel OOM messages first. The additional workers may have exceeded the host’s capacity. Restore the prior value, then profile the largest Apache and upstream consumers.
“The value changed, but the warning remains”
Confirm that you edited the enabled configuration, that the reload succeeded, and that the active MPM is the one you expected. For worker or event, check whether Apache rounded the value down because it was not compatible with ThreadsPerChild.
“Apache will not start after changing the limits”
Run sudo apache2ctl configtest and read the service journal and error log. Look for duplicate directives, a missing module, an invalid MPM combination, an insufficient ServerLimit, or values beyond what the system can allocate. Restore the previous configuration if the cause is not immediately clear.
“The warning appears only during long requests”
Measure upstream wait time and request duration. If workers are occupied by a slow backend, fix or scale that backend and review connection behavior before increasing Apache concurrency.
“There are crashes but no clear MaxRequestWorkers pattern”
Follow the crash branch: correlate Apache timestamps with kernel logs, core dumps, and module changes. A segmentation fault or signal requires module and integration isolation, not an automatic limit increase.
Verify that the repair worked
- Run
sudo apache2ctl configtestand confirm it passes. - Check
sudo systemctl status apache2 --no-pagerfor a healthy service. - Review the error log for repeated MaxRequestWorkers exhaustion, startup errors, segmentation faults, signals, and child-PID exits.
- Observe a representative traffic period rather than relying on an immediate post-reload result.
- Track RAM, swap, CPU, request latency, 5xx rate, process or thread counts, and upstream health together.
- Document the selected MPM,
ServerLimit,ThreadsPerChild,MaxRequestWorkers, the observed concurrency, and the rollback command.
A successful repair leaves Apache running, keeps the host out of swap and OOM conditions, and improves or preserves latency and error rates at the traffic level that originally exposed the problem. If only the warning disappears while memory pressure or crashes continue, the incident is not fixed.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
Frequently Asked Questions
Should I increase MaxRequestWorkers when Apache logs that it reached the setting?
Not automatically. First compare concurrency with latency, upstream wait time, RAM, swap, CPU, 5xx responses, and crash or OOM messages. Increase the ceiling only when requests are healthy, the host has measured headroom, and the active MPM’s rules are satisfied.
What does MaxRequestWorkers count on Ubuntu?
It counts child processes with prefork and total request threads with worker or event. Confirm the active MPM with apache2ctl -M; the same numeric value has different memory and capacity consequences under each model.
Why did Apache round down my MaxRequestWorkers value?
Worker and event require a value compatible with ThreadsPerChild. When the value is invalid or not an appropriate multiple, Apache rounds it down and logs a warning. Check the effective setting in the startup or reload log.
Can a MaxRequestWorkers warning cause Apache to crash?
The warning itself reports a concurrency ceiling being reached. A crash may occur at the same time because of memory exhaustion, a faulty module, an integration, or another failure. Correlate timestamps with kernel logs, core dumps, and the loaded module list instead of assuming causation.
What should I do if raising the limit triggers OOM errors?
Restore the previous value, reload Apache, and investigate total host memory use across Apache, PHP-FPM, databases, proxies, and monitoring. Reduce concurrency when necessary and fix the memory-heavy component rather than giving Apache more workers.
When should I change from prefork to event or worker?
Treat an MPM change as an architectural project. Verify PHP and every loaded module are thread-safe, compare measured memory and connection behavior, make the change in a maintenance window, and keep a tested rollback to the former MPM and limits.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →The Bottom Line
MaxRequestWorkers is a ceiling, not a cure. Preserve the Apache, system, and kernel evidence; identify the one active MPM; validate every edit; and change only one measured variable at a time. Raise concurrency only when memory, upstream latency, and crash evidence show the host can safely support it. Otherwise reduce pressure, repair the module or upstream service, and verify the result over representative traffic.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
