Great Circle Associates Majordomo-Users
(January 2000)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: error messages = broken majordomo :(
From: "Bill Casti (System Admin)" <help @ quality . org>
Date: Wed, 5 Jan 2000 17:34:50 -0500 (EST)
To: "Majordomo Users' List" <majordomo-users @ GreatCircle . com>


Maybe you can help me. I recently installed (new install) v1.94.1 and it
was working fine (after lots of tweaking) until last night. I ran the
wrapper config-test that Jeff mentioned in his posting and it came out
clean.

Here's my problem.....I'm suddenly getting this error message for every
list I support on Majordomo......

--
MAJORDOMO ABORT (mj_resend)!!
shlock: '/usr/local/majordomo/lists' is not writable by UID 1 GID 1 
--

This seems to be telling me that it can't write to the
/usr/local/majordomo/lists directory, but here's the excerpt from
/usr/local/majordomo....

...
drwxrwxr-x   3 majordom      512 May 17  1998 listat/
-rwxrwxr-x   1 majordom   921600 Sep 21  1997 listat_tar*
drwxrwxr-x   4 majordom     5120 Jan  5 10:03 lists/
drwxrwxr-x   7 majordom      512 Mar  3  1999 majorcool/
-rwxrwxr-x   1 majordom   120087 Mar  3  1999 majorcool.pl*
-rwxrwxr-x   1 majordom     8410 Mar 13  1999 majorcool_default.cf*
-rwxrwxr-x   1 majordom     8387 Nov 25  1998 majorcool_fwtk-list.cf*
-rwxrwxr-x   1 majordom     8407 Mar  3  1999 majorcool_info-sec.cf*
-rwxrwxr-x   1 majordom     8410 Nov 29  1998 majorcool_mo-list.cf*
...

and from /usr/local/majordomo/lists

...
-rwxrwxr-x   1 majordom majordomo       6 Dec 31 14:18 mil-qual-d.passwd*
-rwxrwxr-x   1 majordom majordomo     543 Dec 31 14:18 mo*
-rwxrwxr-x   1 majordom majordomo      33 Dec 31 14:18 mo-digest*
-rwxrwxr-x   1 majordom majordomo   14884 Dec 31 14:18 mo-digest.config*
-rwxrwxr-x   1 majordom majordomo       9 Dec 31 14:18 mo-digest.passwd*
-rwxrwxr-x   1 majordom majordomo   14840 Dec 31 14:18 mo.config*
-rwxrwxr-x   1 majordom majordomo     598 Dec 31 14:18 mo.info*
-rwxrwxr-x   1 majordom majordomo     585 Dec 31 14:18 mo.list*
-rwxrwxr-x   1 majordom majordomo   14813 Dec 31 14:18 mo.old.config*
-rwxrwxr-x   1 majordom majordomo      16 Dec 31 14:18 mo.owner*
-rwxrwxr-x   1 majordom majordomo       9 Dec 31 14:18 mo.passwd*
...

The permissions look right to me. Oh, and I'm also occasionally (but not
always) getting this error message....

--
MAJORDOMO ABORT (mj_majordomo)!!

While running with an effective uid of 1 and an effective gid of 1 12 4 2 1,
Majordomo ran into the following problems:
Unable to write to log file, check permissions on /usr/local/majordomo/Log
Unable to write to list directory $listdir, check permissions on
/usr/local/majordomo/lists
--

I haven't changed anything, so now I'm really confused and my lists are
broken until this can be resolved. I don't know what's going on. Can
anyone help me interpret and fix whatever the issue is?

Thanks.
Bill

=============================================================================
 Bill Casti, CQA                                     Email: help@quality.org
 - Domain Owner, QUALITY.ORG                         Pager: +1 800 604 6149
 - List Moderator, "TQM in Manufacturing and Service Industries"
=============================================================================


On Mon, 3 Jan 2000, Jeff Lasman wrote:

> At 10:05 AM 1/3/00  Christopher A. Adams wrote:
> 
> >After a new installtion, I get the following error messages:
> >
> >
> >MAJORDOMO ABORT (mj_majordomo)!!
> >
> >Can't append to /usr/local/majordomo/lists/wriurb: Permission denied
> >
> >
> >MAJORDOMO ABORT (mj_majordomo)!!
> >
> >chown(1, 98, "/usr/local/majordomo/lists/wriurb.new"): Not owner
> 
> 
> Let me guess... that's happening when you try to add to the wriurb list.
> 
> I wrote about this problem a week or two ago.  Did you install majordomo as 
> root?
> 
> Here's what the majordomo FAQ says on this issue:
> 
> >2.2 - I get a MAJORDOMO ABORT with "chown(...): Not owner" or ".. 
> >Operation not permitted"
> >
> >Most likely your wrapper is not installed correctly. Re-check the Makefile 
> >and see if the wrapper was compiled with the right
> >UID and GID. See the README and the above section on how to set the 
> >permissions correctly. Make sure after you fix the
> >wrapper that you remove (or rename) any "listname.new" or "L.listname" 
> >files found in your lists directory. These will likely have
> >the wrong ownerships, and cause you problems.
> >
> >You should have seen an error if you ran "./wrapper config-test" as a 
> >non-root, non-majordom user. If not, it's a bug in config-test
> >and should be fixed.
> 
> You can find the entire faq at 
> <http://www.greatcircle.com/majordomo/FAQ.html>; you can find the general 
> majordomo pages at <http://www.greatcircle.com/majordomo/>.
> 
> If you still can't figure this out, please contact me offlist.
> 
> Thanks.
> 
> Jeff
> 
> --
> Jeff Lasman, nobaloney.net
> <jblists@nobaloney.net>
> <www.nobaloney.net>, <www.mailtraqna.com>, <www.email-lists.com>
> 
> 




Indexed By Date Previous: TLB and MHonArc
From: Jim Reisert <Jim_Reisert@mint-tech.com>
Next: Re: new error messages
From: Seth Kurtzberg <seth@cql.com>
Indexed By Thread Previous: Re: TLB and MHonArc
From: Jim Reisert <Jim_Reisert@mint-tech.com>
Next: Majordomo punting to avoid mail loop?
From: "Christopher A. Adams" <chris@sparkie.osl.state.or.us>

Google
 
Search Internet Search www.greatcircle.com