Bug 65628 - AH00051 - [core:notice] [pid 117745:tid 140692937303872] AH00051: child pid 117751 exit signal Segmentation fault (11), possible coredump in /opt/app/t1c1w177/opt/app/apache
Summary: AH00051 - [core:notice] [pid 117745:tid 140692937303872] AH00051: child pid 1...
Status: RESOLVED INVALID
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Core (show other bugs)
Version: 2.4.48
Hardware: Other Linux
: P2 critical (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-10-12 12:04 UTC by VINAY S
Modified: 2021-10-28 20:12 UTC (History)
0 users



Attachments
Segmentation error log (3.85 KB, text/plain)
2021-10-12 12:04 UTC, VINAY S
Details
Core dump file (3.82 KB, text/plain)
2021-10-14 07:42 UTC, VINAY S
Details
Complete thread log file (36.29 KB, text/plain)
2021-10-14 11:33 UTC, VINAY S
Details
Gdb commands output file (3.30 KB, text/plain)
2021-10-28 15:04 UTC, VINAY S
Details

Note You need to log in before you can comment on or make changes to this bug.
Description VINAY S 2021-10-12 12:04:29 UTC
Created attachment 38062 [details]
Segmentation error log

Hi ,

We are facing segmentation fault error in apache 2.4.48. This is happening post openssl upgrade from 1.1.1K tp 1.1.1.L

Below is the error we are getting,
[Tue Oct 12 03:57:02.667437 2021] [:notice] [pid 117745:tid 140692937303872] Advertise initialized for process 117745
[Tue Oct 12 03:57:02.668705 2021] [mpm_event:notice] [pid 117745:tid 140692937303872] AH00489: Apache/2.4.48 (Unix) OpenSSL/1.1.1l mod_cluster/1.3.10.Final configured -- resuming normal operations
[Tue Oct 12 03:57:02.668752 2021] [core:notice] [pid 117745:tid 140692937303872] AH00094: Command line: '/opt/app/t1c1w177/opt/app/apache/bin/httpd'
[Tue Oct 12 03:57:06.673051 2021] [core:notice] [pid 117745:tid 140692937303872] AH00051: child pid 117751 exit signal Segmentation fault (11), possible coredump in /opt/app/t1c1w177/opt/app/apache


We are using Apache 2.4.48 on RHEL 7.
Comment 1 VINAY S 2021-10-14 07:42:27 UTC
Created attachment 38067 [details]
Core dump file
Comment 2 Ruediger Pluem 2021-10-14 08:08:56 UTC
(In reply to VINAY S from comment #1)
> Created attachment 38067 [details]
> Core dump file

Please provide the full output. You only provided full output from one thread and that thread did not cause the crash.
Comment 3 VINAY S 2021-10-14 11:33:27 UTC
Created attachment 38068 [details]
Complete thread log file

Please find the complete thread log file
Comment 4 Ruediger Pluem 2021-10-14 15:11:13 UTC
Thanks. In gdb please issue the following commands:

thread 1
frame 3
print *r
print *(r->connection)
print *(r->connection->conn_config)
Comment 5 VINAY S 2021-10-28 15:04:33 UTC
Created attachment 38081 [details]
Gdb commands output file

thread 1
frame 3
print *r
print *(r->connection)
print *(r->connection->conn_config)
Comment 6 Ruediger Pluem 2021-10-28 20:12:09 UTC
This is a bug in mod_proxy_cluster. You are using a very old version of mod_proxy_cluster. It was fixed in mod_proxy_cluster here: https://github.com/modcluster/mod_proxy_cluster/commit/7a62cbf471bcfaf3aff0860418ee7871e2d4c5e6