I have been using XAMPP on windows for the two year or so and it has been running perfectly, no crashes no problems. (Up until four month ago.)
Around four months ago, we upgraded our server/system to a faster specification.
Here is what the old spec was -
Windows Edition: Windows Server R2 2008 Standard with Service Pack 1
System Processor: Intel(R) Xeon(R) CPU 5160 #3.0GHZ (2 Processors) (Single Core)
Installed Memory: 7GB
System Type: 64 Bit Operating System
Upgraded Spec
Windows Edition: Windows Server R2 2008 Standard with Service Pack 1
System: Processor: Intel(R) Xeon(R) CPU X5680 #3.33GHZ (2 Processors) (Dual Core)
Installed Memory: 8GB
System Type: 64 Bit Operating System
So like I mentioned before, the old spec never had any problems, it never crashed or failed over one and a half years.
As soon as we upgraded the following happened.
Random Apache crashes, making the site un-usable until it is manually restarted. It would throw errors up when accessing phpMyAdmin when apache had crashed too, stopping you from querying the DB. I even uninstalled XAMPP and installed the latest version with PHP7, this still didn't solve the problem.
Heres an example
Notice in .\libraries\common.inc.php#253 Undefined variable: _POST
Backtrace
.\index.php#12: require_once(.\libraries\common.inc.php) Warning in
.\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) Notice in
.\libraries\common.inc.php#443 Undefined variable: _POST
Backtrace
.\index.php#12: require_once(.\libraries\common.inc.php) Notice in
.\libraries\common.inc.php#453 Undefined variable: _POST
Backtrace
.\index.php#12: require_once(.\libraries\common.inc.php) Notice in
.\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) Notice in
.\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 from 1-5 times a day, and there are no logs produced to give any reason why it happened. The only way I could find out was go into the event viewer which is extremely vague.
Heres an example --
Faulting application name: httpd.exe, version: 2.4.18.0, time stamp:
0x5667f02e Faulting module name: php7ts.dll, version: 7.0.2.0, time
stamp: 0x568d8eb5 Exception code: 0xc0000005 Fault offset: 0x0001ab54
Faulting process id: 0x9bf4 Faulting application start time:
0x01d18f1d3eed5f7e Faulting application path:
C:\xampp_\apache\bin\httpd.exe Faulting module path:
C:\xampp_\php\php7ts.dll Report Id:
a2a226d0-fb64-11e5-b4cb-005056a97cdf
And
Faulting application name: httpd.exe, version: 2.4.18.0, time stamp:
0x5667f02e Faulting module name: ntdll.dll, version: 6.1.7601.23313,
time stamp: 0x5684289c Exception code: 0xc0000374 Fault offset:
0x000ce00b Faulting process id: 0x3320 Faulting application start
time: 0x01d18b1c1e501368 Faulting application path:
C:\xampp_\apache\bin\httpd.exe Faulting module path:
C:\Windows\SysWOW64\ntdll.dll Report Id:
77d4bd4a-f723-11e5-9fc8-005056a97cdf
Just to prove my theory of the faster spec being the issue, I got the Specification lowered back to its original state, and for 2 weeks XAMPP never crashed once, as soon as we but it back to the higher spec, it crashed within hours.
Is there anything you are speicificly meant to do to XAMPP if you upgrade to faster spec?
I am absolutely lost for ideas, I have looked and looked online and can't seem to find anyone who is experiencing the same problems that I am having and why.
If anyone could shed some light on these issues, I would greatly appreciate it!
You went from single to dual core. Check the apache configuration to find out what MPM module is being used. Multiple threads might work on a single core that may no longer work on multicore server.
You must use multicore! Single core isn't supportet any longer! Check the config I had the same problem
Related
In Windows 7, a process started with CreateProcessAsUser by a windows service with a local system account crashes, but the same process started manually runs fine. The CreateProcessAsUser functionality is in a separate COM component [64 bit C++ dll], and the windows service [dot net 4.6.1] has platform target [Any CPU]. The process does not write anything to the event log either, suggesting that no code is executed, and it crashes immediately. This code works perfectly in windows 10.
I tried to attach to the process but it ends too soon to do anything. I do get a message "Module not found" , suggesting that it doesnt find a library. But I cant figure out which one. I gave it all the libraries it needs, which can be seen by the fact that the program runs ok when started manually from the same folder. I also tried to specify the startup folder in the function CreateProcessAsUser, but there was no difference, but I think it starts in the correct folder by default [where it is located]
I found the following link on SO
Why is this process crashing as soon as it is launched?
But it did not help either. ProcMon does not show where a module was not found [It says PATH NOT FOUND if I remove a known module]
The process exit status is -1066598274
and the stack trace is
0 ntoskrnl.exe RtlNtStatusToDosError + 0x1086 0xfffff8000712f206 C:\Windows\system32\ntoskrnl.exe
1 ntoskrnl.exe RtlCopySidAndAttributesArray + 0x1789 0xfffff8000714b0d9 C:\Windows\system32\ntoskrnl.exe
2 ntoskrnl.exe RtlNtStatusToDosError + 0x1538 0xfffff8000712f6b8 C:\Windows\system32\ntoskrnl.exe
3 ntoskrnl.exe KeSynchronizeExecution + 0x3a23 0xfffff80006e75e53 C:\Windows\system32\ntoskrnl.exe
The event viewer shows the following information
Faulting application name: BizBrainAgentPluginHost.exe, version: 1.0.0.0, time stamp: 0x5b88084d
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18015, time stamp: 0x50b8479b
Exception code: 0xc06d007e
Fault offset: 0x0000000000009e5d
Faulting process id: 0x484
Faulting application start time: 0x01d440746491e037
Faulting application path: C:\Program Files\Avinashi Ventures Pvt Ltd\myTallyApp Agent\BizBrainAgentPluginHost.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: a2f39c97-ac67-11e8-94f1-0023ae9747d0
Thanks
I am running diskspd.exe tool which you can download from:
Diskspd Utility: A Robust Storage Testing Tool (superseding SQLIO)
https://github.com/Microsoft/diskspd
Operating system: Windows 2016 standard
I first get this:
D:\Diskspd\amd64fre>diskspd.exe -d15 -o4 -t4 -b8k -r -L -w50 testdiskspd.dat
Error opening file: testdiskspd.dat [2]
Error opening file: testdiskspd.dat [2]
Error opening file: testdiskspd.dat [2]
Error opening file: testdiskspd.dat [2]
After 15 seconds I get this:
There has been an error during threads execution
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
At the same time I get following pop up window:
I have write permission in folder D:\Diskspd\amd64fre\. I tested this by creating a .txt file.
This is what I can see in my windows log.
Faulting application name: diskspd.exe, version: 0.0.0.0, time stamp: 0x54b9a313
Faulting module name: msvcrt.dll, version: 7.0.14393.0, time stamp: 0x57899b47
Exception code: 0x40000015
Fault offset: 0x000000000000c2c2
Faulting process id: 0x4b40
Faulting application start time: 0x01d3e2437778fe7f
Faulting application path: D:\Diskspd\amd64fre\diskspd.exe
Faulting module path: C:\Windows\System32\msvcrt.dll
Report Id: 2190f963-f533-4805-b23a-e3224c56e72d
Faulting package full name:
Faulting package-relative application ID:
Any suggestions?
I needed to provide the file size switch and a value. Then it ran fine. From the document it was not clear that it was a mandatory parameter.
D:\Diskspd\amd64fre>diskspd.exe -d15 -o4 -t4 -b8k -r -L -w50 -c1G testdiskspd
I recently learned that the app I'm working on frequently crashes Internet Explorer 10 - no error messages, just Windows' "The application stopped working". Looking at the Event Viewer shows what I gather is a null reference in mshtml.dll:
Faulting application name: iexplore.exe, version: 10.0.9200.17267, time stamp: 0x54e7f156
Faulting module name: MSHTML.dll, version: 10.0.9200.17267, time stamp: 0x54e803bf
Exception code: 0xc0000005
Fault offset: 0x004f9b17
Faulting process id: 0xeec
Faulting application start time: 0x01d0657e1d8a29f6
Faulting application path: C:\Program Files\Internet Explorer\iexplore.exe
Faulting module path: C:\Windows\system32\MSHTML.dll
I've discovered that this happens when loading the first script on the page, which is jQuery. I've tried two different versions: 1.10.2 and 1.11.2, with the same result.
It turns out that introducing a small delay before loading jQuery (and the rest of the scripts) solves the issue. I've added this snippet before all other scripts:
if (navigator.userAgent.indexOf('MSIE 10') >= 0) {
var t = new Date().getTime();
while (new Date().getTime() - t < 300);
}
This seemingly solves the problem. However, it is clearly very inelegant and I still don't know what the actual problem is.
Has anyone experienced something similar, and is there a better solution?
I appear to be in a bit of a bind. I have been working on some simple design changes to our website and having finished went to release them live. No sooner than I uploaded the affected pages, the MySQL Daemon service crahsed. I did a restart and then restarted the service as it didn't restart automatically and managed to navigate to the website. It crashed again and has been doing so nearly every ten minutes like clockwork.
The windows event log is listed here:
Log Name: Application
Source: Application Error
Date: 14/06/2013 10:03:47
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DEDICAT-3JPUQIF
Description:
Faulting application name: mysqld.exe, version: 5.5.28.0, time stamp: 0x503ddca5
Faulting module name: mysqld.exe, version: 5.5.28.0, time stamp: 0x503ddca5
Exception code: 0xc0000005
Fault offset: 0x00000000000fd869
Faulting process id: 0x428
Faulting application start time: 0x01ce68dc51cff4c0
Faulting application path: C:Program FilesMySQLMySQL Server 5.5binmysqld.exe
Faulting module path: C:Program FilesMySQLMySQL Server 5.5binmysqld.exe
Report Id: 525bda97-d4d1-11e2-95f3-525400bb8b87
Event Xml:
1000
2
100
0x80000000000000
6821
Application
DEDICAT-3JPUQIF
mysqld.exe
5.5.28.0
503ddca5
mysqld.exe
5.5.28.0
503ddca5
c0000005
00000000000fd869
428
01ce68dc51cff4c0
C:Program FilesMySQLMySQL Server 5.5binmysqld.exe
C:Program FilesMySQLMySQL Server 5.5binmysqld.exe
525bda97-d4d1-11e2-95f3-525400bb8b87
Does anybody have any clues what might be causing this?
As always thanks in advance.
Graham
This turned out to be an erroneous space character at the end of several lines of a stored procedure generated by SqlYog. Removing the characters fixed the problem.
Cheers
Graham
When I researched, this error means your database is probably corrupt and needs rebuilding.
Have a look at MySQL suddenly not working on Windows Server 2003 server fault question.
Hope this helps.
I have the following two error logs in the Windows Event Viewer of our IIS production server:
Source: Application Error
Category: (100)
Event ID: (1000)
Description: Faulting application w3wp.exe, version 6.0.3790.3959, faulting module mscorwks.dll, version 2.0.50727.3603, fault address 0x0001da8f.
Seconds later:
Source: .NET Runtime 2.0 Error Reporting
Category: None
Event ID: 1000
Description: Faulting application w3wp.exe, version 6.0.3790.3959, stamp 45d6968e, faulting module mscorwks.dll, version 2.0.50727.3603, stamp 4a7cd88e, debug? 0, fault address 0x0001da8f.
What can I do with these error messages? I see that I have a fault address and a dll name - are there any tools that will show me what is at this address in the dll? Would this be the correct approach to figuring out what caused the crash? I've so far not been able to replicate it.
Thanks.