User Tools

Site Tools


apache:troubleshooting:determine_why_an_apache_process_hung

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
apache:troubleshooting:determine_why_an_apache_process_hung [2021/02/02 11:05] – [Use gcore utility to force a hung process to dump its core] peterapache:troubleshooting:determine_why_an_apache_process_hung [2021/02/02 11:05] (current) – [Use gdb utility to retrieve a stack backtrace from the core file] peter
Line 127: Line 127:
 **NOTE:**  This shows: **NOTE:**  This shows:
  
-  * **accept ()**:  Apache was in the accept() system call when a SIGSEGV signal was received, and accept() was called by the portable runtime method **apr_socket_accept()**. +  * **accept ()**:  Apache was in the **accept()** system call when the SIGSEGV signal was received.
- +
-  * **accept ()**:  Apache was in the **accept()** system call when the error was received.+
     * **accept()** was called by the portable runtime method **apr_socket_accept()**.     * **accept()** was called by the portable runtime method **apr_socket_accept()**.
 </WRAP> </WRAP>
apache/troubleshooting/determine_why_an_apache_process_hung.1612263919.txt.gz · Last modified: 2021/02/02 11:05 by peter

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki