Great Circle Associates Majordomo-Users
(February 1995)
 

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

Subject: Re: Returned mail: unknown mailer error 139
From: "Franklin R. Jones" <frjones @ nma . mnet . uswest . com>
Date: Mon, 27 Feb 1995 14:39:32 -0700
To: majordomo-users @ greatcircle . com
Cc: frjones @ nma
In-reply-to: Your message of "Mon, 27 Feb 1995 11:22:28 EST." <Pine.3.89.9502271129.G16041-0100000@bell>

Re:

> > =>   ----- Transcript of session follows -----
> > =>Segmentation Fault
> > =>554 "|/home/server/wrapper majordomo"... unknown mailer error 139
> 
> Ahh.. That looks familiar to me.  I once had a problem with a directory 
> permission that cuase majorodomo's file locking mechanism to enter a 
> state of infinite recursion util it died (after a hundred or so 
> iterations, according to perl4's debugger).
> 
> I don't remember the exact directory, but I believe it had something to 
> do with accidentally turning off group "majodomo" write on one diretory.
> 
> I know that's all a bit vague, but it may help...
> 
> Jeremy

vague I can deal with, however...

	After beating on this all day. I've discovered that the
directory that is specified in the majordomo.cf file as `homedir' has
to be world writable as the temp lock files are pointing at this
directory. . . once this is done, the error goes away, and function
seems normal. (I haevn't actually built a list as of yet.)

	Please someone tell me I've screwed up something in the
configuration, because this seems *totally* wrong to me. 

	I traced this down by using a -w on the `#! /bin/perl' line in
the majordomo script. It seemed to be looping trying to write a lock
file in shlock.pl until it finally it seg faults.
	Then turning on debug inside shlock.pl I was able to narrow
the fault down.
	I at first thought that this might be due to a user id issue
where I had the same id on the test system, and the mailserver which
had differing id numbers. that was not the case as a 3rd test id built
yet another system exibited the same behavior.
	A copy of mail sent to owner-majordomo is below prior to
chmod'ing the directory. I've also included the output of `majordomo
test' which seems fine.

Is this the way this is supposed to run? please don't say yes.

Ideas anyone? Even vague one's will do. :) (thanks, jeremy.)

fj..

==============================inclusions==============================

 id: 101 is `server'
grp: 101 is `listserv'

wrapper test, run from root:
======================================================================
==> wrapper test
euid is: 101
egid is: 101 101
ruid is: 101
rgid is: 101 101

edited returned mail to owner-majordomo:
======================================================================
Return-Path: Mailer-Daemon 
Return-Path: <Mailer-Daemon>
Received: by peregrine. (5.x/SMI-SVR4)
	id AB18000; Mon, 27 Feb 1995 10:35:05 -0700
Date: Mon, 27 Feb 1995 10:35:05 -0700
From: Mailer-Daemon (Mail Delivery Subsystem)
Subject: Returned mail: unknown mailer error 139
Message-Id: <9502271735.AB18000@peregrine.>
To: owner-majordomo
Content-Type: text
Content-Length: 36328

   ----- Transcript of session follows -----
Possible typo: "FLAGIT" at /home/server/majordomo line 205.
Possible typo: "GETFILE" at /home/server/majordomo line 992.
Possible typo: "NCONFIG" at /home/server/majordomo line 714.
Possible typo: "PASSWD" at /home/server/majordomo line 427.
Possible typo: "command_noadvert" at /home/server/majordomo line 856.
Possible typo: "command_advert" at /home/server/majordomo line 856.
Possible typo: "majordomo_version" at /home/server/majordomo line 1130.
Possible typo: "program_name" at /home/server/majordomo line 27.
Possible typo: "return_subject" at /home/server/majordomo line 118.
Possible typo: "time" at /home/server/majordomo line 592.
sort (...) interpreted as function at /home/server/config_parse.pl line 455.
Use of uninitialized variable at /home/server/majordomo.pl line 67, <STDIN> line 1.
Use of uninitialized variable at /home/server/majordomo.pl line 144, <STDIN> line 1.
trying lock "/home/server/L.Log" for pid 18002
temporary filename "/home/server/shlock.18002"
. . . [deleted ~160 lines same] . . .
trying lock "/home/server/L.Log" for pid 18002
temporary filename "/home/server/shlock.18002"
Deep recursion on subroutine "log" at /home/server/majordomo.pl line 194, <> line 1.
Deep recursion on subroutine "lopen" at /home/server/majordomo.pl line 229, <> line 1.
Deep recursion on subroutine "shlock" at /home/server/shlock.pl line 171, <> line 1.
trying lock "/home/server/L.Log" for pid 18002
Deep recursion on subroutine "xtmpfile" at /home/server/shlock.pl line 30, <> line 1.
temporary filename "/home/server/shlock.18002"
Deep recursion on subroutine "open_temp" at /home/server/shlock.pl line 130, <> line 1.
Deep recursion on subroutine "abort" at /home/server/majordomo.pl line 490, <> line 1.
trying lock "/home/server/L.Log" for pid 18002
temporary filename "/home/server/shlock.18002"
trying lock "/home/server/L.Log" for pid 18002
. . . [deleted ~520 lines same] . . .
trying lock "/home/server/L.Log" for pid 18002
temporary filename "/home/server/shlock.18002"
trying lock "/home/server/L.Log" for pid 18002
temporary filename "/home/server/shlock.18002"
Segmentation Fault
554 "|/home/server/wrapper majordomo"... unknown mailer error 139



Follow-Ups:
References:
Indexed By Date Previous: Re: Returned mail: unknown mailer error 139
From: BBoerner@btrvtech.com (Brendan B. Boerner)
Next: Re: Returned mail: unknown mailer error 139
From: Jeremy Zawodny <jzawodn@cs.bgsu.edu>
Indexed By Thread Previous: Re: Returned mail: unknown mailer error 139
From: Jeremy Zawodny <jzawodn@cs.bgsu.edu>
Next: Re: Returned mail: unknown mailer error 139
From: Jeremy Zawodny <jzawodn@cs.bgsu.edu>

Google
 
Search Internet Search www.greatcircle.com