|Summary:||Apache hanging on system calls for php and perl|
|Product:||Apache httpd-2||Reporter:||Russel Olinger <rolinger1>|
|Component:||Core||Assignee:||Apache HTTPD Bugs Mailing List <bugs>|
|OS:||Windows Server 2003|
|URL:||Internal application development|
Description Russel Olinger 2009-01-29 10:46:15 UTC
While researching my problem using Perl 5.10, I came across another thread on the php.net site related to this issue as well. http://bugs.php.net/bug.php?id=44942 Using perl's backtick (ie: @files = `dir ../config /O:D /A:-D`;) command to do a system call hangs Apache's CGI. Once it hangs any other Perl script that uses a system call will hang leaving both 'cmd' and 'perl' process hung in memory. And any other Perl script that doesn't have a system call will execute, return the data, but the 'perl' process will stay resident in memory. Eventually if enough cmd and/or perl processes remain in memory the system CPU pegs at 100% or Apache completely locks up requiring a system reboot. A: No log or error messages are created B: Sometimes it goes 10 days without a hang or just two days, and sometimes scripts with system/exec calls will run fine 100 times, and then just 5 times, before hanging. C: After a hang, a sevice restart usually works to get everything working again. But occassionally a full system reboot is required. The above link to the PHP article refers to a similar problem with PHPs 'exec' system calls causing Apache to hang. PS: My apologies if this is already a documented issue, I searched bugzilla and found nothing similar in nature to what I (and the PHP users) are experiencing.
Comment 1 William A. Rowe Jr. 2018-11-07 21:09:13 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.