Operation not permitted in cgi scripts, unkown mailer error 126 (PR#183)
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| GNU Mailman |
Invalid
|
Low
|
Unassigned | ||
Bug Description
Jitterbug-Id: 183
Submitted-By: <email address hidden>
Date: Tue, 4 Jan 2000 19:40:52 -0500 (EST)
Version: 1.1
OS: Red Hat Linux 5.1 (2.2.13)
While trying to access the web interface i got a "500 Internal Server
Error" and
the following
entry in the apache (1.3.6) error log:
[Wed Jan 5 01:34:45 2000] [error] (1)Operation not permitted: exec of
/home/mailman/
[Wed Jan 5 01:34:45 2000] [error] [client 194.143.233.50] Premature end of
script headers: /home/mailman/
if i run it as httpd or another user on the commandline i get:
[cranx@flerp cgi-bin]$ ./listinfo
bash: ./listinfo: Operation not permitted
[cranx@flerp cgi-bin]$ strace ./listinfo
execve(
0
strace: exec: Operation not permitted
[cranx@flerp cgi-bin]$
and the typical stuff under mailman:
[mailman@flerp cgi-bin]$ ./listinfo
Content-type: text/html
<head>
<title>Mailman CGI error!!!</title>
</head><body>
<h1>Mailman CGI error!!!</h1>
The expected gid of the Mailman CGI wrapper did not match the gid as set by
the
Web server.<p>The most likely cause is that Mailman was configured
and installed
incorrectly. Please read the INSTALL instructions again, paying close
attention
to the <tt>--with-
being stored in
your syslog:
<pre>
Failure to exec script. WANTED gid 617, GOT gid 614. (Reconfigure to take
614?)</pre>
[mailman@flerp cgi-bin]$
needless to say that --with-mail-gid and --with-cgi-gid were well
configured,
and
we ran 5 lists on that server using mailman 1.0 for half a year when
suddenly it
made something
strange and started to generate these errors, and also "unknown mailer
error
126"
messages in the maillog.. it also locked down the server with a lot of
CROND
proces..
thank you.
=======
Audit trail:
None
[http://
| Barry Warsaw (barry) wrote | #1 |
I don't believe this is a Mailman problem. Something must have changed in
your OS environment that is causing this.