Differences

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

--- apache:troubleshooting:determine_why_an_apache_process_hung [2021/02/02 11:02] – [Apache - Troubleshooting - Determine why an Apache process hung] peter
+++ apache: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 53: / Line 53: @@
   * **accept**:  Apache was in the **accept()** system call when the error was received.
-Some systems do not have the **pstack** utility.
+Some systems do not have the **pstack** utility.  In these cases try using the **gdb** and **gcore** utilities to get a stack backtrace from a process.
-  * In these cases try using the **gdb** and **gcore** utilities to get a stack backtrace from a process.
 </WRAP>
@@ Line 90: / Line 88: @@
 **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()**.
 </WRAP>
@@ Line 101: / Line 97: @@
 <code bash>
-gcore 5649
+gcore 4932
 </code>
@@ Line 131: / Line 127: @@
 **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()**.
 </WRAP>