Search found 69 matches: Faulting application apache.exe

Searched query: +Faulting +application +apache +exe

Return to advanced search

Error: MySQL shutdown unexpectedly.

Hi.

Just installed Xampp on my new Windows Box. Got Apache up, but when I start MySQL I get the following :

1:11:40 PM [mysql] Error: MySQL shutdown unexpectedly.
1:11:40 PM [mysql] This may be due to a blocked port, missing dependencies,
1:11:40 PM [mysql] improper privileges, a crash, or a shutdown by another method.
1:11:40 PM [mysql] Press the Logs button to view error logs and check
1:11:40 PM [mysql] the Windows Event Viewer for more clues
1:11:40 PM [mysql] If you need more help, copy and post this
1:11:40 PM [mysql] entire log window on the forums

Mysql_error.log:

2023-12-05 13:11:38 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 18480
2023-12-05 13:11:38 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2023-12-05 13:11:38 0 [Note] InnoDB: Uses event mutexes
2023-12-05 13:11:38 0 [Note] InnoDB: Compressed tables use zlib 1.3
2023-12-05 13:11:38 0 [Note] InnoDB: Number of pools: 1
2023-12-05 13:11:38 0 [Note] InnoDB: Using SSE2 crc32 instructions
2023-12-05 13:11:38 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2023-12-05 13:11:38 0 [Note] InnoDB: Completed initialization of buffer pool
2023-12-05 13:11:38 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=300423
2023-12-05 13:11:38 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2023-12-05 13:11:38 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2023-12-05 13:11:38 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2023-12-05 13:11:38 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2023-12-05 13:11:38 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2023-12-05 13:11:38 0 [Note] InnoDB: Waiting for purge to start
2023-12-05 13:11:38 0 [Note] InnoDB: 10.4.32 started; log sequence number 300432; transaction id 170
2023-12-05 13:11:38 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2023-12-05 13:11:38 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-12-05 13:11:38 0 [Note] Server socket created on IP: '127.0.0.1'.
2023-12-05 13:11:38 0 [Note] InnoDB: Buffer pool(s) load completed at 231205 13:11:38
231205 13:11:38 [ERROR] mysqld got exception 0xc0000005 ;
Sorry, we probably made a mistake, and this is a bug.

Your assistance in bug reporting will enable us to fix this for the next release.
To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.4.32-MariaDB source revision: c4143f909528e3fab0677a28631d10389354c491
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=65537
thread_count=6
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 20304 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x17ed3d19f68
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
VCRUNTIME140.dll!memcpy()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!?ha_rnd_next@handler@@QEAAHPEAE@Z()
mysqld.exe!?rr_sequential@@YAHPEAUREAD_RECORD@@@Z()
mysqld.exe!?acl_init@@YA_N_N@Z()
mysqld.exe!?acl_reload@@YA_NPEAVTHD@@@Z()
mysqld.exe!?acl_init@@YA_N_N@Z()
mysqld.exe!?win_main@@YAHHPEAPEAD@Z()
mysqld.exe!?mysql_service@@YAXPEAX@Z()
ucrtbase.dll!_crt_at_quick_exit()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x0):
Connection ID (thread ID): 0
Status: NOT_KILLED

Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on

The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains
information that should help you find out what is causing the crash.
Writing a core file at C:\xampp\mysql\data
Minidump written to C:\xampp\mysql\data\mysqld.dmp

Event Viewer Application Log:

Faulting application name: mysqld.exe, version: 10.4.32.0, time stamp: 0x653fa81d
Faulting module name: VCRUNTIME140.dll, version: 14.36.32532.0, time stamp: 0xc94bf788
Exception code: 0xc0000005
Fault offset: 0x000000000000142c
Faulting process id: 0x0x4830
Faulting application start time: 0x0x1DA27A67D49E9B2
Faulting application path: C:\xampp\mysql\bin\mysqld.exe
Faulting module path: C:\xampp\mysql\bin\VCRUNTIME140.dll
Report Id: c1de7e39-aaff-41db-9aa8-4aaa261b5927
Faulting package full name:
Faulting package-relative application ID:

Anyone have any insights?
by BlairS
05. December 2023 19:26
 
Forum: XAMPP for Windows
Topic: Error: MySQL shutdown unexpectedly.
Replies: 0
Views: 20030

Error: Apache shutdown unexpectedly

Dear forum, I have a problem with my Apache server on XAMPP version 3.3.0
I know this issue is very common, but the solution seems to be more unique for each client user or different for each XAMPP version

By now I have already tried changing the port numbers in both config files from 80 to 800 and 8080; and 443 to 4433 and 1443 to no avail.

Please help!

Operating system: Windows 11 x64-bit
XAMPP Version: 3.3.0

Full XAMPP control panel log window contents:
4:47:05 PM [main] Initializing Control Panel
4:47:05 PM [main] Windows Version: Home 64-bit
4:47:05 PM [main] XAMPP Version: 8.0.12
4:47:05 PM [main] Control Panel Version: 3.3.0 [ Compiled: Apr 6th 2021 ]
4:47:05 PM [main] You are not running with administrator rights! This will work for
4:47:05 PM [main] most application stuff but whenever you do something with services
4:47:05 PM [main] there will be a security dialogue or things will break! So think
4:47:05 PM [main] about running this application with administrator rights!
4:47:05 PM [main] XAMPP Installation Directory: "c:\xampp\"
4:47:05 PM [main] Checking for prerequisites
4:47:05 PM [main] All prerequisites found
4:47:05 PM [main] Initializing Modules
4:47:05 PM [main] The FileZilla module is disabled
4:47:05 PM [main] The Mercury module is disabled
4:47:05 PM [main] The Tomcat module is disabled
4:47:05 PM [main] Starting Check-Timer
4:47:05 PM [main] Control Panel Ready
4:47:09 PM [Apache] Attempting to start Apache app...
4:47:09 PM [Apache] Status change detected: running
4:47:10 PM [Apache] Status change detected: stopped
4:47:10 PM [Apache] Error: Apache shutdown unexpectedly.
4:47:10 PM [Apache] This may be due to a blocked port, missing dependencies,
4:47:10 PM [Apache] improper privileges, a crash, or a shutdown by another method.
4:47:10 PM [Apache] Press the Logs button to view error logs and check
4:47:10 PM [Apache] the Windows Event Viewer for more clues
4:47:10 PM [Apache] If you need more help, copy and post this
4:47:10 PM [Apache] entire log window on the forums

Apache error log: (There is nothing with a recent date. The last error entry was on March 2022 - apache was working fine back then)
[Tue Mar 08 20:26:20.420495 2022] [ssl:warn] [pid 15184:tid 328] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Tue Mar 08 20:26:20.530445 2022] [core:warn] [pid 15184:tid 328] AH00098: pid file C:/xampp/apache/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Tue Mar 08 20:26:20.546361 2022] [ssl:warn] [pid 15184:tid 328] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Tue Mar 08 20:26:21.062947 2022] [mpm_winnt:notice] [pid 15184:tid 328] AH00455: Apache/2.4.51 (Win64) OpenSSL/1.1.1l PHP/8.0.12 configured -- resuming normal operations
[Tue Mar 08 20:26:21.062947 2022] [mpm_winnt:notice] [pid 15184:tid 328] AH00456: Apache Lounge VS16 Server built: Oct 7 2021 16:27:02
[Tue Mar 08 20:26:21.062947 2022] [core:notice] [pid 15184:tid 328] AH00094: Command line: 'c:\\xampp\\apache\\bin\\httpd.exe -d C:/xampp/apache'
[Tue Mar 08 20:26:21.075105 2022] [mpm_winnt:notice] [pid 15184:tid 328] AH00418: Parent: Created child process 4592
[Tue Mar 08 20:26:22.124482 2022] [ssl:warn] [pid 4592:tid 680] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Tue Mar 08 20:26:22.221123 2022] [ssl:warn] [pid 4592:tid 680] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Tue Mar 08 20:26:22.263602 2022] [mpm_winnt:notice] [pid 4592:tid 680] AH00354: Child: Starting 150 worker threads.


Windows event log entries (although I don't think these are relevant)
The program xampp-control.exe version 3.3.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
Process ID: 1f94
Start Time: 01d8d051c3555028
Termination Time: 3
Application Path: C:\xampp\xampp-control.exe
Report Id: 94f0b150-8a67-4b1c-8512-9aac03fd0b86
Faulting package full name:
Faulting package-relative application ID:
Hang type: Unknown

Faulting application name: xampp-control.exe, version: 3.3.0.0, time stamp: 0x606c4833
Faulting module name: xampp-control.exe, version: 3.3.0.0, time stamp: 0x606c4833
Exception code: 0xc0000005
Fault offset: 0x0025b292
Faulting process id: 0x1f94
Faulting application start time: 0x01d8d051c3555028
Faulting application path: C:\xampp\xampp-control.exe
Faulting module path: C:\xampp\xampp-control.exe
Report Id: f4cef20d-6a03-49a3-b40b-67982a584e11
Faulting package full name:
Faulting package-relative application ID:
by dinunez9313
24. September 2022 22:11
 
Forum: XAMPP for Windows
Topic: Error: Apache shutdown unexpectedly
Replies: 0
Views: 4097

MySQL Unexpected Shutdown - temp fix?

XAMPP version 7.4.21
+ Apache 2.4.48
+ MariaDB 10.4.20
+ PHP 7.4.21 (VC15 X86 64bit thread safe) + PEAR

I have not changed xampp or apache config except for adding a local certificate and enabling ssl. I have modified php.ini slightly and added xdebug.

I had been experiencing the MySQL unexpected shutdown error on xampp v 7.4.5 and tried to resolve it by backing up my sites and databases and restoring them to xampp 7.4.21. This did not solve the problem. I tried some other methods to fix that I found online including
- executing some database repair commands from the command line
- checking and repairing databases from within phpmyadmin
- renaming mysql\data, copying files from mysql\backup to mysql\data, copying database folders from mysql\data_orig to mysql\data.

These sometimes seem to fix the problem temporarily but the problem does return. Here is what I see when the problem occurs:

1. Reboot machine
2. Start Apache
3. Start MySQL
4. Get the following error:

2:30:31 PM [main] Initializing Control Panel
2:30:31 PM [main] Windows Version: Enterprise 64-bit
2:30:31 PM [main] XAMPP Version: 7.4.21
2:30:31 PM [main] Control Panel Version: 3.3.0 [ Compiled: Apr 6th 2021 ]
2:30:31 PM [main] Running with Administrator rights - good!
2:30:31 PM [main] XAMPP Installation Directory: "c:\xampp7421\"
2:30:31 PM [main] Checking for prerequisites
2:30:31 PM [main] All prerequisites found
2:30:31 PM [main] Initializing Modules
2:30:31 PM [main] Starting Check-Timer
2:30:31 PM [main] Control Panel Ready
2:30:33 PM [Apache] Attempting to start Apache app...
2:30:33 PM [Apache] Status change detected: running
2:30:35 PM [mysql] Attempting to start MySQL app...
2:30:35 PM [mysql] Status change detected: running
2:30:42 PM [mysql] Status change detected: stopped
2:30:42 PM [mysql] Error: MySQL shutdown unexpectedly.
2:30:42 PM [mysql] This may be due to a blocked port, missing dependencies,
2:30:42 PM [mysql] improper privileges, a crash, or a shutdown by another method.
2:30:42 PM [mysql] Press the Logs button to view error logs and check
2:30:42 PM [mysql] the Windows Event Viewer for more clues
2:30:42 PM [mysql] If you need more help, copy and post this
2:30:42 PM [mysql] entire log window on the forums

See the following in mysql_error.log:

2021-09-04 14:30:36 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2021-09-04 14:30:36 0 [Note] InnoDB: Uses event mutexes
2021-09-04 14:30:36 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-09-04 14:30:36 0 [Note] InnoDB: Number of pools: 1
2021-09-04 14:30:36 0 [Note] InnoDB: Using SSE2 crc32 instructions
2021-09-04 14:30:36 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2021-09-04 14:30:36 0 [Note] InnoDB: Completed initialization of buffer pool
2021-09-04 14:30:36 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=326416538
2021-09-04 14:30:41 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2021-09-04 14:30:41 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2021-09-04 14:30:41 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2021-09-04 14:30:41 0 [Note] InnoDB: Setting file 'C:\xampp7421\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2021-09-04 14:30:41 0 [Note] InnoDB: File 'C:\xampp7421\mysql\data\ibtmp1' size is now 12 MB.
2021-09-04 14:30:41 0 [Note] InnoDB: Waiting for purge to start
2021-09-04 14:30:41 0 [Note] InnoDB: 10.4.20 started; log sequence number 326416547; transaction id 81018
2021-09-04 14:30:41 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp7421\mysql\data\ib_buffer_pool
2021-09-04 14:30:41 0 [Note] Plugin 'FEEDBACK' is disabled.
2021-09-04 14:30:41 0 [Note] InnoDB: Buffer pool(s) load completed at 210904 14:30:41
2021-09-04 14:30:41 0 [Note] Server socket created on IP: '::'.

From the Windows Event Viewer:

Faulting application name: mysqld.exe, version: 10.4.20.0, time stamp: 0x60c0c152
Faulting module name: mysqld.exe, version: 10.4.20.0, time stamp: 0x60c0c152
Exception code: 0x80000003
Fault offset: 0x000000000066b992
Faulting process ID: 0x4e7c
Faulting application start time: 0x01d7a1d4193aac44
Faulting application path: c:\xampp7421\mysql\bin\mysqld.exe
Faulting module path: c:\xampp7421\mysql\bin\mysqld.exe
Report ID: 4faa1a8b-8faf-4f71-860b-c2d592021498
Faulting package full name:
Faulting package-relative application ID:

The most reliable method I have found to fix the problem for the longest period of time is this:
1. Stop MySQL
2. Rename mysql\aria_log_control to mysql\aria_log_controlHIDEME
3. Start MySQL

With these steps, MySQL reliably keeps running until the next time the computer reboots. It does not matter whether I just reboot, or whether I shut down MySQL and Apache first.

My question is what can I do to properly troubleshoot this issue so that it stops occurring?

Cheers
Paul
by paul@orangecubed.ca
04. September 2021 22:58
 
Forum: XAMPP for Windows
Topic: MySQL Unexpected Shutdown - temp fix?
Replies: 1
Views: 6121

httpd.exe APPCRASH on exit

I've downloaded and installed Xampp v7.4.19 (64 bit) using this link: https://www.apachefriends.org/download.html

I have multiple instances of Xampp installed, so the Xampp folder name reflects that. After running setup and tweaking a few things, the application launches (as administrator) and functions as expected. But, when I exit before shutting down the computer for the night, I get this error. It's predictable and it occurs on two different computers. It is not hindering my work, but it is annoying and I would like to have a clean exit from Xampp. How do I solve this?

The problem seems to be pointing at php7ts.dll.

Here's the error as reported through from the Event Viewer.
Code: Select all
Log Name:      Application
Source:        Application Error
Date:          5/22/2021 3:59:51 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Optiplex9020
Description:
Faulting application name: httpd.exe, version: 2.4.47.0, time stamp: 0x6087d2bb
Faulting module name: php7ts.dll, version: 7.4.19.0, time stamp: 0x60916735
Exception code: 0xc0000005
Fault offset: 0x0000000000561f4b
Faulting process id: 0x4384
Faulting application start time: 0x01d74f432be56c80
Faulting application path: C:\xampp-VC15a\apache\bin\httpd.exe
Faulting module path: C:\xampp-VC15a\php\php7ts.dll
Report Id: 78d30020-1d23-4441-acec-ce48728deae1
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-05-22T22:59:51.1996950Z" />
    <EventRecordID>79462</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>Optiplex9020</Computer>
    <Security />
  </System>
  <EventData>
    <Data>httpd.exe</Data>
    <Data>2.4.47.0</Data>
    <Data>6087d2bb</Data>
    <Data>php7ts.dll</Data>
    <Data>7.4.19.0</Data>
    <Data>60916735</Data>
    <Data>c0000005</Data>
    <Data>0000000000561f4b</Data>
    <Data>4384</Data>
    <Data>01d74f432be56c80</Data>
    <Data>C:\xampp-VC15a\apache\bin\httpd.exe</Data>
    <Data>C:\xampp-VC15a\php\php7ts.dll</Data>
    <Data>78d30020-1d23-4441-acec-ce48728deae1</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>


And here's what's showing up in the Windows Reliability application:
Code: Select all
Source
Apache HTTP Server

Summary
Stopped working

Date
‎5/‎21/‎2021 11:49 PM

Status
Report sent

Description
Faulting Application Path:   C:\xampp-vc15a\apache\bin\httpd.exe

Problem signature
Problem Event Name:   APPCRASH
Application Name:   httpd.exe
Application Version:   2.4.47.0
Application Timestamp:   6087d2bb
Fault Module Name:   php7ts.dll
Fault Module Version:   7.4.19.0
Fault Module Timestamp:   60916735
Exception Code:   c0000005
Exception Offset:   0000000000561f4b
OS Version:   10.0.19041.2.0.0.256.48
Locale ID:   1033
Additional Information 1:   f942
Additional Information 2:   f942f6748555cac7de1eb74b64624431
Additional Information 3:   9468
Additional Information 4:   946847bcf02d9beb2089fcb8d9383190

Extra information about the problem
Bucket ID:   be9642e2429cd6c3fff8d924fcd72415 (2303829962284016661)
by MarjWyatt
25. May 2021 19:06
 
Forum: XAMPP for Windows
Topic: httpd.exe APPCRASH on exit
Replies: 0
Views: 4621

Apache stopped working - After upgrade to Windows 10 1903

I was running Xampp 7.3.6 and then i upgraded to Window 10 Pro 1903 from 1803. Apache in Xampp would not longer start.

This is my solution

In the Apache error.log I had the following which I could not see anything unusual.
Code: Select all
[Sat Aug 24 09:44:44.295165 2019] [ssl:warn] [pid 1540:tid 644] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Sat Aug 24 09:44:44.342037 2019] [core:warn] [pid 1540:tid 644] AH00098: pid file D:/websites/apache/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Sat Aug 24 09:44:44.342037 2019] [ssl:warn] [pid 1540:tid 644] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name


In the windows event log I had:
Code: Select all
Faulting application name: httpd.exe, version: 2.4.39.0, time stamp: 0x5cee4f90
Faulting module name: ADVAPI32.dll, version: 10.0.18362.1, time stamp: 0x96f604e5
Exception code: 0xc0000005


After researching I came across this page (https://www.apachelounge.com/viewtopic.php?p=38154) where mdeggers was having a similiar issue with apache.

MeSo2 at the end says "I had to reinstall Apache to 2.4.39 and PHP to 7.3.8, and that fixed it."


So i got the latest version of Xampp with Apache 2.4.39 and PHP 7.3.8 and tested that it worked on my PC, which it did. I then proceeded to upgraded my Xampp to this version and now Apache is running correctly.

This looks like it is an inssue with Apache or PHP rather than Xampp.

shoulders
by shoulders
24. August 2019 13:22
 
Forum: XAMPP for Windows
Topic: Apache stopped working - After upgrade to Windows 10 1903
Replies: 0
Views: 5267

Re: Apache not work: SSL:warn

I run xampp-control and i press start and xampp logs;

10:14:33 [Apache] Error: Apache shutdown unexpectedly.
10:14:33 [Apache] This may be due to a blocked port, missing dependencies,
10:14:33 [Apache] improper privileges, a crash, or a shutdown by another method.
10:14:33 [Apache] Press the Logs button to view error logs and check
10:14:33 [Apache] the Windows Event Viewer for more clues
10:14:33 [Apache] If you need more help, copy and post this
10:14:33 [Apache] entire log window on the forums

And apache error.logs;

[Mon Dec 17 10:14:30.442142 2018] [ssl:warn] [pid 14628:tid 676] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Mon Dec 17 10:14:30.465081 2018] [core:warn] [pid 14628:tid 676] AH00098: pid file C:/xampp/apache/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Mon Dec 17 10:14:30.466078 2018] [ssl:warn] [pid 14628:tid 676] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name

Windows event viewer;

- System
- Provider
[ Name] Application Error
- EventID 1000
[ Qualifiers] 0
Level 2
Task 100
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2018-12-17T07:21:08.023272000Z
EventRecordID 45898
Channel Application
Computer DESKTOP-35CJMCM
Security
- EventData
httpd.exe
2.4.37.0
5bc8a3ef
ntdll.dll
10.0.17134.471
fe852bc4
c0000005
00043654
2d10
01d495d913e98db4
C:\xampp\apache\bin\httpd.exe
C:\WINDOWS\SYSTEM32\ntdll.dll
ca149450-a4ee-48e4-866e-bb8e2bee34a3


*****

Faulting application name: httpd.exe, version: 2.4.37.0, time stamp: 0x5bc8a3ef
Faulting module name: ntdll.dll, version: 10.0.17134.471, time stamp: 0xfe852bc4
Exception code: 0xc0000005
Fault offset: 0x00043654
Faulting process id: 0x5780
Faulting application start time: 0x01d495d9158a9df0
Faulting application path: c:\xampp\apache\bin\httpd.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll

apache dont start. What is my problem, how can i find problem ?
*My ports are open for 80.

If i can press start button 8-9 times apache work, but Why doesn't it work the first time ?
by baskiki
17. December 2018 08:25
 
Forum: XAMPP for Windows
Topic: Apache not work: SSL:warn
Replies: 2
Views: 6778

XAMPP perl has mysteriously stopped working

so XAMPP is installed and working fine for a couple of months along with a smattering of Perl. Nothing changes, the perl runs fine, Apache runs fine. Then one day I get the Error 500 message on a perl script. It's annoying the hell out of me but before I can start looking to fix, it starts working again. A month or so later, same problem. Only it's permanent Error 500. I'm flummoxed. Throwing a clean install of XAMPP on the system throws up the same result. Trolling the Event Viewer I come across this:

Faulting application name: perl.exe, version: 0.0.0.0, time stamp: 0x513f2742
Faulting module name: perl516.dll, version: 0.0.0.0, time stamp: 0x513f2741
Exception code: 0xc0000005
Fault offset: 0x0011e7e5
Faulting process ID: 0x1a68
Faulting application start time: 0x01d41889c30be427
Faulting application path: C:\usr\xaphod0\iDev\_xampp\perl\bin\perl.exe
Faulting module path: C:\usr\xaphod0\iDev\_xampp\perl\bin\perl516.dll
Report ID: aa938569-ed5d-4493-907c-8ebfcf081ab8
Faulting package full name:
Faulting package-relative application ID:


So... Any here present care to take a stab in the dark and suggest a fix?
by xaphod
10. July 2018 21:43
 
Forum: XAMPP for Windows
Topic: XAMPP perl has mysteriously stopped working
Replies: 1
Views: 3996

Re: Apache has stopped working before I've finished installa

Faulting application name: httpd.exe, version: 2.4.28.0, time stamp: 0x59d4a9ab
Faulting module name: mod_version.so, version: 2.4.28.0, time stamp: 0x59d4a9b0
Exception code: 0xc0000005
Fault offset: 0x00000870
Faulting process id: 0x15a0
Faulting application start time: 0x01d3586ed92e5787
Faulting application path: c:\xampp\apache\bin\httpd.exe
Faulting module path: C:\xampp\apache\modules\mod_version.so
Report Id: 18c711d5-c462-11e7-84f0-cb55049d9b8a

This is the error I found using event viewer (windows).
by Supercon22
08. November 2017 10:04
 
Forum: XAMPP for Windows
Topic: Apache has stopped working before I've finished installation
Replies: 27
Views: 38580

Re: Apache suddenly stops working

I have the same problem:

Faulting application name: httpd.exe, version: 2.4.23.0, time stamp: 0x577631b1
Faulting module name: ntdll.dll, version: 6.1.7601.23864, time stamp: 0x595fa490
Exception code: 0xc0000374
Fault offset: 0x000ce8fb
Faulting process id: 0xa54
Faulting application start time: 0x01d310fdecddb997
Faulting application path: C:\xampp\apache\bin\httpd.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: ba3f5bfe-7cfe-11e7-b6a1-005056864a79

other info:

Informazioni di sistema
Impostazione Valore

PHP attivo su Windows NT SRVPORT1 6.1 build 7601 (Windows Server 2008 R2 Datacenter Edition Service Pack 1) i586
Versione database 5.5.5-10.1.16-MariaDB
Collation database utf8_general_ci
Collation connessione database utf8mb4_general_ci
Versione PHP 7.0.9
Web Server Apache/2.4.23 (Win32) OpenSSL/1.0.2h PHP/7.0.9
WebServer interfaccia PHP apache2handler
Versione di Joomla! Joomla! 3.6.5 Stable [ Noether ] 1-December-2016 22:46 GMT
Versione piattaforma Joomla! Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT
User Agent Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36
by nirovi
14. September 2017 08:35
 
Forum: XAMPP for Windows
Topic: Apache suddenly stops working
Replies: 1
Views: 8190

Apache suddenly stops working

Hi all,

Can anyone help me with my problem?
Apache sometimes stop working. Please see the log message from the event viewer.

Faulting application name: apache.exe, version: 2.2.4.0, time stamp: 0x45ebef86
Faulting module name: ntdll.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba58
Exception code: 0xc0000005
Fault offset: 0x0002e39e
Faulting process id: 0x17d0
Faulting application start time: 0x01d247aecbd584d4
Faulting application path: C:\xampp\apache\bin\apache.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 49ba053a-b3a4-11e6-b356-0cc47a78ecd1

I am new to this and I don't have any idea what to do. Hope someone can help me.
Thanks!
by jdelfin
28. November 2016 10:05
 
Forum: XAMPP for Windows
Topic: Apache suddenly stops working
Replies: 1
Views: 8190

Apache/Mysql Crashing When increasing System Specification

Hi all,

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!
by CodeFluffer
07. April 2016 09:10
 
Forum: XAMPP for Windows
Topic: Apache/Mysql Crashing When increasing System Specification
Replies: 1
Views: 8409

Re: XAMPP installation problem

Good afternoon,

Further to my original post, I thought I would add the text from the CP.
2:19:30 PM [main] Initializing Control Panel
2:19:30 PM [main] Windows Version: Windows 7 Professional SP1 32-bit
2:19:30 PM [main] XAMPP Version: 5.5.33
2:19:30 PM [main] Control Panel Version: 3.2.2 [ Compiled: Nov 12th 2015 ]
2:19:30 PM [main] Running with Administrator rights - good!
2:19:30 PM [main] XAMPP Installation Directory: "c:\xampp\"
2:19:30 PM [main] Checking for prerequisites
2:19:49 PM [main] All prerequisites found
2:19:49 PM [main] Initializing Modules
2:19:49 PM [main] The FileZilla module is disabled
2:19:49 PM [main] The Mercury module is disabled
2:19:49 PM [main] The Tomcat module is disabled
2:19:49 PM [main] Starting Check-Timer
2:19:49 PM [main] Control Panel Ready
2:19:54 PM [Apache] Attempting to start Apache app...
2:19:54 PM [Apache] Status change detected: running
2:20:13 PM [Apache] Status change detected: stopped
2:20:13 PM [Apache] Error: Apache shutdown unexpectedly.
2:20:13 PM [Apache] This may be due to a blocked port, missing dependencies,
2:20:13 PM [Apache] improper privileges, a crash, or a shutdown by another method.
2:20:13 PM [Apache] Press the Logs button to view error logs and check
2:20:13 PM [Apache] the Windows Event Viewer for more clues
2:20:13 PM [Apache] If you need more help, copy and post this
2:20:13 PM [Apache] entire log window on the forums

Between the 2:19:54 and the 2:20:13 entries, the Windows Apache failed pop-up occurs.

From the apache_start.bat the only text that appears (in German and English) is 'Please close this command only for Shutdown. Apache 2 is starting...'. Then the Windows 'Apache HTTP Server has stopped working' etc and when the program closes the Command window disappears.

The Windows log on the General tab follows:
Faulting application name: httpd.exe, version: 2.4.17.0, time stamp: 0x561cc534
Faulting module name: libapr-1.dll, version: 1.5.2.0, time stamp: 0x561cc6a2
Exception code: 0xc0000005
Fault offset: 0x00011fcb
Faulting process id: 0x14e4
Faulting application start time: 0x01d1857dc9c53cc4
Faulting application path: C:\xampp\apache\bin\httpd.exe
Faulting module path: C:\xampp\apache\bin\libapr-1.dll
Report Id: 0a03d1a6-f171-11e5-81bc-000d613fb08d

Starting the httpd.exe directly opens a Command window that stays open until the Windows pop-ups are finished with, but no text or commands appear.

This is probably as much light as I can throw on the problem at the moment but if there is anything else that might be of use, please let me know.

Thanks in advance for any assistance.

HarryB
by HarryB
24. March 2016 04:45
 
Forum: XAMPP for Windows
Topic: XAMPP installation problem
Replies: 12
Views: 23220

Re: Apache keep crashing without any special behavior

gsmith wrote:I think you should check the windows event log in your administrator tools. You should see something similar to this in there somewhere.
Description:
Faulting application httpd.exe, version 2.4.13.0, faulting module mod_telemetry.so, version 1.0.5.0, fault address 0x00001004.

This should give you some idea as to what is crashing. The access log then may lead you to what request is crashing it at the timestamp just before the error log note about child exiting. Look back through a few of them and you should have a pretty decent picture.

My guess is some third party module doesn't like something.


Hi,
thank you,

i have found this:

Faulting application name: httpd.exe, version: 2.4.12.0, time stamp: 0x54c90386
Faulting module name: ntdll.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba58
Exception code: 0xc0000005
Fault offset: 0x0002e39e
Faulting process id: 0x7a8
Faulting application start time: 0x01d0a1e832bfaef7
Faulting application path: C:\xampp\apache\bin\httpd.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 8c6f0701-11ee-11e5-bd87-005056b36612

any idea how to proceed ?

time stamp is 6/13/2015 8:06:37 PM (before the restart)
but i think that this is the real time that the server went down. (the Apache log only updated after i approved the windows message )
by shayt
15. June 2015 09:35
 
Forum: XAMPP for Windows
Topic: Apache keep crashing without any special behavior
Replies: 5
Views: 15149

Re: Apache keep crashing without any special behavior

I think you should check the windows event log in your administrator tools. You should see something similar to this in there somewhere.
Description:
Faulting application httpd.exe, version 2.4.13.0, faulting module mod_telemetry.so, version 1.0.5.0, fault address 0x00001004.

This should give you some idea as to what is crashing. The access log then may lead you to what request is crashing it at the timestamp just before the error log note about child exiting. Look back through a few of them and you should have a pretty decent picture.

My guess is some third party module doesn't like something.
by gsmith
14. June 2015 19:46
 
Forum: XAMPP for Windows
Topic: Apache keep crashing without any special behavior
Replies: 5
Views: 15149

Apache 2.4 in XAMPP 1.8.1/2 - crash w/status 3221225477

I apologize for the lengthy post. This is about a web server crash I encountered after upgrading from XAMPP 1.7.3. I first suspected my own code as I am teaching myself PHP. Although I still may have some bad code, I finally regression-tested it down to the Firefox HTTP Pipelining setting I had carried since probably version 2.

I don't know who should be contacted about this, Apache, or PHP devs, but I'll start here. Maybe this will help some people seeing the same Apache error code in Windows.

OS: Windows XP Pro SP3, and Vista Home SP2

What: Apache 2.4 can crash when serving certain pages to browsers with HTTP pipelining enabled

apache/logs/error.log:
[mpm_winnt:notice] [pid 3672:tid 316] AH00428: Parent: child process exited with status 3221225477 -- Restarting.

Windows event log (XAMPP 1.8.1): Event ID: 1000
Faulting application httpd.exe, version 2.4.3.0, faulting module php5ts.dll, version 5.4.7.0, fault address 0x0007fbbf.
or ...0x0004ed09.
or ...0x0004b1c7.
The address has been consistently one of the three.

Vista event log (XAMPP 1.8.1): ...fault address 0x0004b1c7

Windows event log (XAMPP 1.8.2):
Faulting application httpd.exe, version 2.4.4.0, faulting module php5ts.dll, version 5.4.16.0, fault address 0x0005cf57.

Steps (for me) to reproduce with minimal setup:
  1. Make sure HTTP Pipelining is enabled
    Opera: in opera:config -> Performance, enable Pipelining, restart
    Firefox: in about:config, set http.network.pipelining to true, restart
  2. un-7zip XAMPP 1.8.1 or 1.8.2 to C:\ (so you have c:\xampp)
  3. unzip box-error.zip to htdocs folder (so you have c:\xampp\htdocs\box-error)
    The file is at brewpups.org/files/box-error.zip, sorry I don't know how to add a link here yet, or even if it's permitted.
  4. from CMD window, cd \xampp, and run apache_start.bat
  5. browse to /localhost/box-error
    depending on your machine/network performance, you may have to refresh several times for the error to happen.

Currently known workarounds:
  • Disable HTTP pipelining - Currently I know of only Opera and Firefox allowing access to that feature.
  • Use Apache 2.2 - As an experiment, I took the Apache 2.2 from XAMPP 1.7.3 and used it in 1.8.1 without any issues so far. I don't think this is a recommended method, but it did work.

Oh, if you do venture to burn your eyes out on my code, please feel free to point out any terrible things I should not be doing :)

Cheers!
by holomon
02. July 2013 23:57
 
Forum: XAMPP for Windows
Topic: Apache 2.4 in XAMPP 1.8.1/2 - crash w/status 3221225477
Replies: 0
Views: 7466
Next

Return to advanced search

cron