Bug 55022 - child pid 3123 exit signal Bus error (10) - Apache not responding
Summary: child pid 3123 exit signal Bus error (10) - Apache not responding
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: All (show other bugs)
Version: 2.2.22
Hardware: Sun Solaris
: P2 critical (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2013-05-28 08:35 UTC by aks
Modified: 2018-11-07 21:08 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description aks 2013-05-28 08:35:52 UTC
Apache is stuck on Solaris 10 OS.
We are seeing below error in Apache error_log file 

Mon May 27 17:47:49 2013] [warn] FastCGI: server "/usr/apache2_cgems/cgi-bin-putusers/put.fcgi" started (pid 23185)
[Mon May 27 17:47:50 2013] [warn] FastCGI: server "/usr/apache2_cgems/cgi-bin-putusers/put.fcgi" started (pid 23205)
[Mon May 27 17:47:51 2013] [warn] FastCGI: server "/usr/apache2_cgems/cgi-bin-putusers/put.fcgi" started (pid 23208)
[Mon May 27 18:23:04 2013] [error] [client] Invalid method in request \x16\x03
[Mon May 27 19:43:28 2013] [notice] child pid 3123 exit signal Bus error (10)
[Mon May 27 19:43:28 2013] [notice] child pid 2475 exit signal Bus error (10)

Could you please let us know the root cause of this issue.

Comment 1 Eric Covener 2013-05-28 10:16:34 UTC
You'll have to configure your system to capture coredumps, recreate, and send in pstack output against the core.
Comment 2 William A. Rowe Jr. 2018-11-07 21:08:30 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.