Apache Crashing With Increased System Specification

I have been using XAMPP for windows for two years or so, and it works fine, there are no crashes. (Until four months ago.)

About four months ago, we upgraded our server / system to a faster specification.

Here is what the old specification is -

Windows Edition: Windows Server R2 2008 Service Pack 1 (SP1) Standard

System processor: Intel (R) Xeon (R) CPU 5160 @ 3.0GHZ (2 processors) (single core processor)

Installed memory: 7 GB

System type: 64-bit operating system

Specification Updated

Windows Edition: Windows Server R2 2008 Service Pack 1 (SP1) Standard

System: Processor: Intel (R) Xeon (R) Processor X5680 @ 3.33GHZ (2 processors) (Dual Core)

Installed memory: 8 GB

System type: 64-bit operating system

So, as I mentioned earlier, the old specification never had any problems, it never crashed or failed for a year and a half.

As soon as we updated, the following happened.

The accidental crash of Apache makes the site unusable until it is manually reloaded. This would lead to errors when accessing phpMyAdmin, when apache also crashed, preventing you from accessing the database. I even uninstalled XAMPP and installed the latest version with PHP7, this still did not solve the problem.

Here is an example

Pay attention to. \ libraries \ common.inc.php # 253 Undefined variable: _POST

Backtrace

. \ index.php # 12: require_once (. \ libraries \ common.inc.php) Warning c. \ libraries \ common.inc.php # 253 array_merge (): Argument # 2 is not an Array

Backtrace

. \ libraries \ common.inc.php # 253: array_merge (array, NULL,). \ index.php # 12: require_once (. \ libraries \ common.inc.php) Note :. \ libraries \ common.inc.php # 443 Undefined variable: _POST

Backtrace

. \ index.php # 12: require_once (. \ libraries \ common.inc.php) Note :. \ libraries \ common.inc.php # 453 Undefined variable: _POST

Backtrace

. \ index.php # 12: require_once (. \ libraries \ common.inc.php) Note :. \ libraries \ cleanup.lib.php # 26 Undefined variable: _POST

Backtrace

. \ libraries \ common.inc.php # 514: PMA_removeRequestVars (array). \ index.php # 12: require_once (. \ libraries \ common.inc.php) Note :. \ libraries \ cleanup.lib.php # 31 Undefined variable: _POST

Backtrace

. \ libraries \ common.inc.php # 514: PMA_removeRequestVars (array). \ index.php # 12: require_once (. \ libraries \ common.inc.php)

This can happen 1 to 5 times a day, and there are no magazines created to explain why it happened. The only way I could figure this out is to log into the event viewer, which is extremely vague.

Here is an example -

Invalid application name: httpd.exe, version: 2.4.18.0, time stamp: 0x5667f02e Module name error: php7ts.dll, version: 7.0.2.0, time stamp: 0x568d8eb5 Exception code: 0xc0000005 Error offset: 0x0001ab54 Failure process identifier: 0x9bf4 Time application launch: 0x01d18f1d3eed5f7e Application path error: C: \ xampp_ \ apache \ bin \ httpd.exe Module path failure: C: \ xampp_ \ php \ php7ts.dll Report ID: a2a226d0-fb64-11e5-b4cb-005056a97cdf

AND

Invalid application name: httpd.exe, version: 2.4.18.0, timestamp: 0x5667f02e Fault module name: ntdll.dll, version: 6.1.7601.23313, timestamp: 0x5684289c Exception code: 0xc0000374 Error offset: 0x000ce00b Error process ID: 0x3320 Error application start time: 0x01d18b1c1e501368 Application path error: C: \ xampp_ \ apache \ bin \ httpd.exe Module path failure: C: \ Windows \ SysWOW64 \ ntdll.dll Report ID: 77d4bd4a-f723-11e5-9fc8-005056a97cdf

Just to prove that my theory of a faster specification is a problem, I got the specification, dropping it back to its original state, and in 2 weeks XAMPP never crashed once, as soon as we did, but it returned to a higher specification, it crashed during few hours.

Is there anything you would like to do for XAMPP if you move on to a faster spec?

I absolutely lost ideas, I looked and looked online and could not find anyone who was experiencing the same problems as mine, and why.

If anyone could shed light on these issues, I would really appreciate it!

+6
source share
2 answers

You have switched from one to a double core. Check your apache configuration to see which MPM module is being used. Multiple threads can run on a single core, which can no longer run on a multicore server.

+1
source

You must use multicore! Single core no longer supports! Check the configuration I had the same problem

0
source

All Articles