www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Scherg <Rainer.Sch...@rexroth.de>
Subject mod_cgi/3634: Can't Exec Any CGI from Apache (ld.so.1: internal: malloc failed)
Date Fri, 08 Jan 1999 09:21:42 GMT

>Number:         3634
>Category:       mod_cgi
>Synopsis:       Can't Exec Any CGI from Apache (ld.so.1: internal: malloc failed)
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          support
>Submitter-Id:   apache
>Arrival-Date:   Fri Jan  8 01:30:00 PST 1999
>Originator:     Rainer.Scherg@rexroth.de
>Release:        1.3.3
gcc 2.8.1,
Solaris 2.6
This report is just informational to make the problem known to others...

After upgrading from Solaris 2.5.1 to Solaris 2.6 apache showed a strange
behavior: Apache couldn't execute any cgi-scripts.

ErrorLog shows messages like:

To fix this problem, have a look to the "/dev" (aka /devices/...) - directory
and carefully check the access rights to certain devices (or the directory)
for the user/group the apache httpd is running on...
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]

>> ld.so.1: internal: malloc failed[Thu Jan  7 11:58:34 1999] [error]
>> Premature end of script headers: /usr/local/etc/httpd/htddocs/.../....cgi

Error 500 was reported to the web client.

View raw message