Bug 47723 - suEXEC and low RLimitMem gives "crit: invalid uid" failures
Summary: suEXEC and low RLimitMem gives "crit: invalid uid" failures
Status: RESOLVED LATER
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_suexec (show other bugs)
Version: 2.2.13
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: MassUpdate
Depends on:
Blocks:
 
Reported: 2009-08-22 03:51 UTC by the hatter
Modified: 2018-11-07 21:09 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description the hatter 2009-08-22 03:51:45 UTC
Using the same httpd.conf and file system from a httpd-2.2.9 install under an old 32-bit slackware and moving to httpd-2.2.12 under slackware64, VHosts with "RLimitMem 10000000 15000000" stopped running CGIs, each CGI issuing "[2009-08-22 09:48:46]: crit: invalid uid: (80)" to suexec_log  VHosts with a higher RLimitMem function as normal.  (Filed under 2.2.13 because it does the same under the current release)

For clarity, 80 is a valid UID, adding:

else {log_err("uid ok - (%d)\n",uid);}

after the clause produced "[2009-08-22 09:02:22]: uid ok - (80)" for VHosts with a higher RLimitCPU set, and ran the CGIs as expected

Removing exit(112) from support/suexec.c and reinstalling didn't stop the CGIs from failing.  No errors in any files pointed to a process being reaped due to memory constraints, under the shipped code or my debugging modifications.

Increasing to RLimitMem 50000000 75000000 seems to work fine for now.
Comment 1 William A. Rowe Jr. 2018-11-07 21:09:20 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.