Re: [Mailman-Users] Web interface stopped working after ubuntu update

[Richard Shetron]

I had this problem during a ubuntu update.  IIRC:  I discovered that the 
update changed the user/group id's of mailman from mailman:www-data to 
list:list (or something like that) as it did a mailman update that 
messed up the id's.  It has been too long to remember the exact details. 
 The default ubuntu mailman install uses different permissions from a 
regular mailman install from the mailman tarball.  I may have removed 
and then reinstalled mailman from the tarball/source.  The ubuntu 
mailman package was pretty old, IIRC.


I remember systemd and apparmor breaking a running system and spending 
weeks fixing everything that was broken.  It broke enough stuff and 
caused enough problems that ubuntu has convinced me to find another *nix 
distribution or even switch to bsd to get away from the disaster that is 
systemd.


On 3/29/2017 3:31 PM, Nick Wyman wrote:

Mark,

Thank you for looking.


The error is "Operation not permitted". My best guess is this is
occurring at this point in the wrapper

#ifdef HAVE_SETREGID
 status = setregid(getegid(), -1);
 if (status)
 fatal(logident, SETREGID_FAILURE, "%s", strerror(errno));
#endif /* HAVE_SETREGID */


Indeed this is the case.  I recompiled the wrapper with this code block 
disabled and the web interface functioned again.

Note that the mailman user and group are "list" while apache runs as user and group 
"www-data".



Do other CGIs (e.g. admin, admindb, private, options) fail the same way.


Yes, all the cgi-bin executables return the same error message.



There should at least be something logged in /var/log/apache2/error.log
or wherever the error log is for the vhost. There is a 'syslog' call in
the wrapper, but it only writes the "Operation not permitted" message
that was displayed in the browser.

If you can find the exit status of the wrapper in the apache log, those
codes are defined as

/* Exit codes, so it's easier to distinguish what caused fatal errors when
  * looking at syslogs.
  */
#define GROUP_MISMATCH 2
#define SETREGID_FAILURE 3
#define EXECVE_FAILURE 4
#define MAIL_USAGE_ERROR 5
#define MAIL_ILLEGAL_COMMAND 6
#define ADDALIAS_USAGE_ERROR 7
#define GROUP_NAME_NOT_FOUND 8


I could not find this information in any log file.  However, via print 
instrumentation, I have reduced the problem to the setregid call.

I'm unable to explain why this command is suddenly failing.


--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/guest2%40sgeinc.com


--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Web interface stopped working after ubuntu update

[Carl Zwanzig]

On 3/29/2017 3:08 PM, Nick Wyman wrote:

The setregid call simply returns -1.  What is odd is that it is the
wrapper is attempting to set the GID to the current value.


I don't have the linux kernel source handy, but in the freebsd code if the 
calling process doesn't have the right credentials, looks like it'll bounce 
regardless of what you're trying to change. That is (slightly 
reformatted, and I may be wrong, too)


egid = uap->egid;
rgid = uap->rgid;
...
  if (
(
 (rgid != (gid_t)-1 &&
  rgid != oldcred->cr_rgid &&
  rgid != oldcred->cr_svgid)
 ||
 (egid != (gid_t)-1 &&
  egid != oldcred->cr_groups[0] &&
  egid != oldcred->cr_rgid &&
  egid != oldcred->cr_svgid)
)
&&
(error = priv_check_cred(oldcred, PRIV_CRED_SETREGID, 0)) != 0
)
goto fail;
(/usr/src/sys/kern/kern_prot.c on a 10.3 system)

Sort of sounds to me that either the calling process isn't actually the IDs 
it should be or that the kernel semantics changed.


Instead of using the wrapper itself, have you written a simple test program 
to play around with combinations of UID/GID? Might be faster just to try 
some variations and see what happens (and maybe try the same on a slightly 
older system).


Later,

z!
who really isn't a BSD kernel hacker
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Web interface stopped working after ubuntu update

[Mark Sapiro]

On 03/29/2017 06:09 PM, Nick Wyman wrote:
> 
> Yes, sorry, that was captured when I tried setting the apache gid to 38 (list 
> group).   Below is the output from standard apache config (running for 
> months) with apache gid 33 (www-data).
> 
> check_caller: start
> check_caller: end
> run_script: start
> effective GID 38
> real GID 33
> setregid returned -1
> errno: 1 Operation not permitted
> 
> listinfo is owned by group 'list' and chmod g+s 


That is all exactly what I would expect except for the recent appearance
of "Operation not permitted", and I don't know what might be causing that.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Web interface stopped working after ubuntu update

[Nick Wyman]

> 
> What group is GID 38?
> 
> I would expect the wrapper to see the effective GID is that of "list"
> and the real GID is that of "www-data" and then to be trying to set the
> real GID to be the effective GID.
> 

Yes, sorry, that was captured when I tried setting the apache gid to 38 (list 
group).   Below is the output from standard apache config (running for months) 
with apache gid 33 (www-data).

check_caller: start
check_caller: end
run_script: start
effective GID 38
real GID 33
setregid returned -1
errno: 1 Operation not permitted

listinfo is owned by group 'list' and chmod g+s 

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Web interface stopped working after ubuntu update

[Mark Sapiro]

On 03/29/2017 03:08 PM, Nick Wyman wrote:
> 
> The setregid call simply returns -1.  What is odd is that it is the wrapper 
> is attempting to set the GID to the current value.  Here is some debugging 
> output:
> 
> check_caller: start
> check_caller: end
> run_script: start
> effective GID 38
> real GID 38
> setregid returned -1
> errno: 1 Operation not permitted


What group is GID 38?

I would expect the wrapper to see the effective GID is that of "list"
and the real GID is that of "www-data" and then to be trying to set the
real GID to be the effective GID.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Web interface stopped working after ubuntu update

[Nick Wyman]

> > Why this would start occurring following an OS update, I
> > don't know. Possibly it is some apparmor config or something similar.
> 
> Or SELinux became enabled?
> 

I've been able to eliminate apparmor (disabled) and selinux (not installed).  

The setregid call simply returns -1.  What is odd is that it is the wrapper is 
attempting to set the GID to the current value.  Here is some debugging output:

check_caller: start
check_caller: end
run_script: start
effective GID 38
real GID 38
setregid returned -1
errno: 1 Operation not permitted


--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Web interface stopped working after ubuntu update

[Carl Zwanzig]

On 3/29/2017 1:44 PM, Mark Sapiro wrote:

Why this would start occurring following an OS update, I
don't know. Possibly it is some apparmor config or something similar.


Or SELinux became enabled?

z!

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Web interface stopped working after ubuntu update

[Mark Sapiro]

On 03/29/2017 12:31 PM, Nick Wyman wrote:
> 
> Indeed this is the case.  I recompiled the wrapper with this code block 
> disabled and the web interface functioned again.
> 
> Note that the mailman user and group are "list" while apache runs as user and 
> group "www-data".


That is expected. The wrappers themselves are group "list" and SETGID.
They are compiled binaries rather than scripts so SETGID is honored.
Apache invokes the wrapper as group "www-data" so when it is invoked its
effective group is "list" and its real group is www-data which is
checked against the compiled in expected group.

All that is OK, but then the wrapper attempts to set the real GID to
that of "list". The reason for this is

/* We need to set the real gid to the effective gid because
there are
 * some Linux systems which do not preserve the effective gid across
 * popen() calls.  This breaks mail delivery unless the
~mailman/data
 * directory is chown'd to the uid that runs mail programs, and that
 * isn't a viable alternative.
 */

Based on that comment, it's really only important for the mail wrapper,
but in any case, this is what is failing in your case with "Operation
not permitted". Why this would start occurring following an OS update, I
don't know. Possibly it is some apparmor config or something similar.


-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Web interface stopped working after ubuntu update

[Nick Wyman]

Mark,

Thank you for looking.

> The error is "Operation not permitted". My best guess is this is
> occurring at this point in the wrapper
> 
> #ifdef HAVE_SETREGID
> status = setregid(getegid(), -1);
> if (status)
> fatal(logident, SETREGID_FAILURE, "%s", strerror(errno));
> #endif /* HAVE_SETREGID */

Indeed this is the case.  I recompiled the wrapper with this code block 
disabled and the web interface functioned again.

Note that the mailman user and group are "list" while apache runs as user and 
group "www-data".

> 
> Do other CGIs (e.g. admin, admindb, private, options) fail the same way.

Yes, all the cgi-bin executables return the same error message.

> 
> There should at least be something logged in /var/log/apache2/error.log
> or wherever the error log is for the vhost. There is a 'syslog' call in
> the wrapper, but it only writes the "Operation not permitted" message
> that was displayed in the browser.
> 
> If you can find the exit status of the wrapper in the apache log, those
> codes are defined as
> 
> /* Exit codes, so it's easier to distinguish what caused fatal errors when
>  * looking at syslogs.
>  */
> #define GROUP_MISMATCH 2
> #define SETREGID_FAILURE 3
> #define EXECVE_FAILURE 4
> #define MAIL_USAGE_ERROR 5
> #define MAIL_ILLEGAL_COMMAND 6
> #define ADDALIAS_USAGE_ERROR 7
> #define GROUP_NAME_NOT_FOUND 8

I could not find this information in any log file.  However, via print 
instrumentation, I have reduced the problem to the setregid call.

I'm unable to explain why this command is suddenly failing. 


--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Web interface stopped working after ubuntu update

[Mark Sapiro]

On 03/28/2017 08:28 PM, Nick Wyman wrote:
> Hello,
> 
> I have an Ubuntu 14.04 server running apache2.4 and mailman.  This server has 
> been running a few lists with no problems for over a year.  After updating 
> some Ubuntu packages for security maintenance (unfortunately I don't know all 
> that changed, but apache2 and mailman were unaltered), the web interface, 
> e.g. mailman/listinfo now displays:
> 
> Mailman CGI error!!!
> 
> The Mailman CGI wrapper encountered a fatal error. This entry is being stored 
> in your syslog:
> Operation not permitted
> 
> The apache2 config files are unchanged:
> 
> I have checked that the vhost for this domain is running with uid and gid 
> www-data.
> Verified that I can run mailman/listinfo from the shell as www-data and 
> receive a proper HTML response.
> 
> I enabled apache2 LogLevel trace3 and see that the request is getting through 
> to mailman/listinfo, but no other info is logged.
> 
> No meaningful info is logged to syslog or mailman/logs.
> 
> It seems that something is failing inside the listinfo executable causing it 
> to return error to the driver leading to the above response.  Is it possible 
> to get more logging info from this process?   Perhaps a Python update has 
> caused a script malfunction?


The error is "Operation not permitted". My best guess is this is
occurring at this point in the wrapper

#ifdef HAVE_SETREGID
status = setregid(getegid(), -1);
if (status)
fatal(logident, SETREGID_FAILURE, "%s", strerror(errno));
#endif /* HAVE_SETREGID */

Do other CGIs (e.g. admin, admindb, private, options) fail the same way.

There should at least be something logged in /var/log/apache2/error.log
or wherever the error log is for the vhost. There is a 'syslog' call in
the wrapper, but it only writes the "Operation not permitted" message
that was displayed in the browser.

If you can find the exit status of the wrapper in the apache log, those
codes are defined as

/* Exit codes, so it's easier to distinguish what caused fatal errors when
 * looking at syslogs.
 */
#define GROUP_MISMATCH 2
#define SETREGID_FAILURE 3
#define EXECVE_FAILURE 4
#define MAIL_USAGE_ERROR 5
#define MAIL_ILLEGAL_COMMAND 6
#define ADDALIAS_USAGE_ERROR 7
#define GROUP_NAME_NOT_FOUND 8

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Web interface stopped working after ubuntu update

[Nick Wyman]

Hello,

I have an Ubuntu 14.04 server running apache2.4 and mailman.  This server has 
been running a few lists with no problems for over a year.  After updating some 
Ubuntu packages for security maintenance (unfortunately I don't know all that 
changed, but apache2 and mailman were unaltered), the web interface, e.g. 
mailman/listinfo now displays:

Mailman CGI error!!!

The Mailman CGI wrapper encountered a fatal error. This entry is being stored 
in your syslog:
Operation not permitted

The apache2 config files are unchanged:

I have checked that the vhost for this domain is running with uid and gid 
www-data.
Verified that I can run mailman/listinfo from the shell as www-data and receive 
a proper HTML response.

I enabled apache2 LogLevel trace3 and see that the request is getting through 
to mailman/listinfo, but no other info is logged.

No meaningful info is logged to syslog or mailman/logs.

It seems that something is failing inside the listinfo executable causing it to 
return error to the driver leading to the above response.  Is it possible to 
get more logging info from this process?   Perhaps a Python update has caused a 
script malfunction?

Thanks in advance for your help. 


--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Web interface not working

[Johnny Dahlén]

Hi
I have set up mailman on gentoo Linux and can't get the web interface 
working. The cgi-scripts are running as reading information works ok, ie 
I can log in, list subscribers, view all settings. But update doesn't 
work. I change a setting, press submit, but the change doesn't show. I 
can see no messenges in any of the logs as to what went wrong.

The system is running Mailman 2.1.5-r2, Gentoo 1.4.6, Apache 2.0.50.
Any pointers?
/Johnny
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

Re: [Mailman-Users] Web interface not working

[Brad Knowles]

At 10:50 AM +0100 2005-01-25, Johnny Dahlén wrote:
 I have set up mailman on gentoo Linux and can't get the web interface
 working. The cgi-scripts are running as reading information works ok,
 ie I can log in, list subscribers, view all settings. But update
 doesn't work. I change a setting, press submit, but the change doesn't
 show. I can see no messenges in any of the logs as to what went wrong.
	Did you search the FAQ Wizard at 
http://www.python.org/cgi-bin/faqw-mm.py?

	If so, you should have turned up entries at 
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.045.htp 
and 
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.053.htp 
that may be related to your question.

--
Brad Knowles, [EMAIL PROTECTED]
Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
-- Benjamin Franklin (1706-1790), reply of the Pennsylvania
Assembly to the Governor, November 11, 1755
  SAGE member since 1995.  See http://www.sage.org/ for more info.
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

Re: [Mailman-Users] Web interface not working

[Johnny Dahlén]

Brad Knowles wrote:
At 10:50 AM +0100 2005-01-25, Johnny Dahlén wrote:
 

I have set up mailman on gentoo Linux and can't get the web interface
working. The cgi-scripts are running as reading information works ok,
ie I can log in, list subscribers, view all settings. But update
doesn't work. I change a setting, press submit, but the change doesn't
show. I can see no messenges in any of the logs as to what went wrong.
   

	Did you search the FAQ Wizard at 
http://www.python.org/cgi-bin/faqw-mm.py?

	If so, you should have turned up entries at 
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.045.htp 
and 
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.053.htp 
that may be related to your question.

 

I did read the FAQ, but somehow managed to miss those entries. I was bit 
by the redirect problem. Thanks for the pointers!

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

[Mailman-Users] ? web interface not working

[Kelemen Zoltan]

Hi. I installed mailman 2.0.8. on RedHat 7.2 with apache, and everything's fine, 
Mailman is running without problems, except that the web interface does not work- it's 
there, I can see it, but if I fill out ANY mailman form (incl. passwords for admin 
pages, user-info updates etc...), the next page (wich should 'respond' to the form ) 
acts like if it hasn't gotten anything from the previous form...

it this sounds a bit confusing, try it yourselves: 
http://www.kmdsz.ro/mailman/listinfo/teszt
and try to subscribe for example. It will (probably) tell you that you must supply an 
email address and a password whatever you entered (or not) there...

Actually, it doesn't work the way it's supposed to work... but after I took a look at 
a page's source, and then tried to access the URL of the action of the form, with 
all the variables as a GET query , it works...

Example: instead of entering the password 'teszt' in the proper 'box' on 
http://www.kmdsz.ro/mailman/admin/teszt I've written in the locator bar the address: 
http://www.kmdsz.ro/mailman/admin/teszt?adminpw=teszt 

anybody have a clue?

 best regards,
   zOLtaN

--
Mailman-Users maillist  -  [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users

Re: [Mailman-Users] web interface not working...

[Jon Carnes]

You might want to add the user nobody (or whatever you use to run Apache) 
to the group mailman.  Then make sure that the group mailman can write to 
that dir and those files.

On Friday 12 October 2001 23:12, Ralph Forsythe wrote:
 Permissions on the logs dir are admin:mailman.  (admin was the acct used
 to install the program.)  Permissions on the error logfile are
 mailman:mailman -- this seems like it would work, yes?  Both the dir and
 file are U+G writeable.

 Oh, sorry for the HTML on the previous post.  Didn't think that coped
 over...

 Thanks,
 - Ralph

 At 08:07 PM 10/12/2001 -0700, you wrote:
   Now, the mailman logs don't show anything.  However the httpd error
   log shows the following output (below), which makes me think there is
   some
 
  kind
 
   of permission thing going on.
 
 Yes, certainly.  So surely the permissions on
  /usr/local/mailman/logs/error are gonna be interesting, yes?
 
 So..um...what are they?
 
 They oughta be group-write mailman, because error lives in
 a directory that ought to be group-sticky mailman...


--
Mailman-Users maillist  -  [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users

Re: [Mailman-Users] web interface not working...

[Ralph Forsythe]

Apache is run under 'httpd/httpd' (user/group).  I compiled mailman using 
the --with-cgi-gid=httpd as I thought it was nobody at first and got 
'expected GID xx, got GID xx' errors when viewing the pages.  I think it's 
running with the right GID now however...

- Ralph

At 10:30 AM 10/13/2001 -0400, Jon Carnes wrote:
You might want to add the user nobody (or whatever you use to run Apache)
to the group mailman.  Then make sure that the group mailman can write to
that dir and those files.

On Friday 12 October 2001 23:12, Ralph Forsythe wrote:
  Permissions on the logs dir are admin:mailman.  (admin was the acct used
  to install the program.)  Permissions on the error logfile are
  mailman:mailman -- this seems like it would work, yes?  Both the dir and
  file are U+G writeable.
 
  Oh, sorry for the HTML on the previous post.  Didn't think that coped
  over...
 
  Thanks,
  - Ralph
 
  At 08:07 PM 10/12/2001 -0700, you wrote:
Now, the mailman logs don't show anything.  However the httpd error
log shows the following output (below), which makes me think there is
some
  
   kind
  
of permission thing going on.
  
  Yes, certainly.  So surely the permissions on
   /usr/local/mailman/logs/error are gonna be interesting, yes?
  
  So..um...what are they?
  
  They oughta be group-write mailman, because error lives in
  a directory that ought to be group-sticky mailman...
 


--
Mailman-Users maillist  -  [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users

[Mailman-Users] web interface not working...

[Ralph Forsythe]

Ok, quick system info: Server is a Cobalt Raq3i running Linux
(glibc). Python is version 2.0.1. Other info, the mailman
home directory is '/usr/local/mailman'. Scriptalias and other
apache config was done per the docs.
When I view the page for the list (creatively titled in this case) at the
following URL, I get the message below it:

http://xyz.xyz.com/mailman/admin/pissoff
(domain changed since this is an open list)
Bug in Mailman version 2.0.6
We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem. Printing of
traceback and other system information has been explicitly inhibited, but
the webmaster can find this information in the Mailman error logs. 

Now, the mailman logs don't show anything. However the httpd error
log shows the following output (below), which makes me think there is
some kind of permission thing going on. I compiled with the proper
mail-gid and cgi-gid bits as far as I know... Does anyone have an
idea as to what might be causing this? (I searched in vain in the
archives, but may have missed something...) And I did RTFM, didn't
see anything like this in there. Thanks!


[- Mailman Version: 2.0.6 -]
[- Traceback --]
Traceback (most recent call last):
 File /usr/local/mailman/scripts/driver, line 71, in
run_main
 immediate=1)
 File
/usr/local/mailman/Mailman/Logging/StampedLogger.py, line 49,
in __init__
 Logger.__init__(self, category, nofail,
immediate)
 File /usr/local/mailman/Mailman/Logging/Logger.py,
line 40, in __init__
 self.__get_f()
 File /usr/local/mailman/Mailman/Logging/Logger.py,
line 55, in __get_f
 f = self.__fp = open(self.__filename, 'a+', 1)
IOError: [Errno 13] Permission denied:
'/usr/local/mailman/logs/error'
[- Python Information -]
sys.version = 2.0.1 (#1, Oct 12 2001, 14:26:18)
[GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)]
sys.executable = /usr/bin/python
sys.prefix = /usr/local
sys.exec_prefix= /usr/local
sys.path = /usr/local
sys.platform = linux2
[- Environment Variables -]
 DOCUMENT_ROOT:
/home/sites/home/web
 UNIQUE_ID:
O8es78yFt28AAAlDDvE
 HTTP_ACCEPT_ENCODING: gzip,
deflate
 SERVER_PORT: 80
 PATH_TRANSLATED:
/home/sites/home/web/pissoff
 REMOTE_ADDR: 
63.227.8.161
 HTTP_ACCEPT_LANGUAGE:
en-us
 GATEWAY_INTERFACE:
CGI/1.1
 SERVER_NAME:
blue.centerone.com
 HTTP_CONNECTION:
Keep-Alive
 HTTP_USER_AGENT: Mozilla/4.0
(compatible; MSIE 6.0; Windows NT 5.0)
 HTTP_ACCEPT: */*
 REQUEST_URI:
/mailman/admin/pissoff
 QUERY_STRING:
 SCRIPT_FILENAME:
/usr/local/mailman/cgi-bin/admin
 SCRIPT_URL:
/mailman/admin/pissoff
 HTTP_HOST:
blue.centerone.com
 REQUEST_METHOD: GET
 SERVER_SIGNATURE:
 SCRIPT_URI:
http://blue.centerone.com/mailman/admin/pissoff
 SCRIPT_NAME:
/mailman/admin
 SERVER_ADMIN: admin
 SERVER_SOFTWARE: Apache/1.3.6
(Unix) mod_perl/1.21 mod_ssl/2.2.8 OpenSSL/0.9.2b
 PYTHONPATH:
/usr/local/mailman
 PATH_INFO: /pissoff
 SERVER_PROTOCOL: 
HTTP/1.1
 REMOTE_PORT: 17721

Re: [Mailman-Users] web interface not working...

[Dan Mick]

 Now, the mailman logs don't show anything.  However the httpd error log 
 shows the following output (below), which makes me think there is some kind 
 of permission thing going on.  

Yes, certainly.  So surely the permissions on /usr/local/mailman/logs/error
are gonna be interesting, yes?

So..um...what are they?

They oughta be group-write mailman, because error lives in
a directory that ought to be group-sticky mailman...


--
Mailman-Users maillist  -  [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users

Re: [Mailman-Users] web interface not working...

[Ralph Forsythe]

Permissions on the logs dir are admin:mailman.  (admin was the acct used to 
install the program.)  Permissions on the error logfile are mailman:mailman 
-- this seems like it would work, yes?  Both the dir and file are U+G 
writeable.

Oh, sorry for the HTML on the previous post.  Didn't think that coped over...

Thanks,
- Ralph

At 08:07 PM 10/12/2001 -0700, you wrote:

  Now, the mailman logs don't show anything.  However the httpd error log
  shows the following output (below), which makes me think there is some 
 kind
  of permission thing going on.

Yes, certainly.  So surely the permissions on /usr/local/mailman/logs/error
are gonna be interesting, yes?

So..um...what are they?

They oughta be group-write mailman, because error lives in
a directory that ought to be group-sticky mailman...


--
Mailman-Users maillist  -  [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users