Great Circle Associates Majordomo-Users
(April 1996)
 

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

Subject: Re: It wasn't meant to be.
From: Mario Storti <mstorti @ galileo . unl . edu . ar>
Date: Tue, 30 Apr 1996 17:36:58 -0300
To: jim @ rollercoaster . com
Cc: majordomo-users @ GreatCircle . COM
In-reply-to: <2.2.32.19960429200622.0070a570@rollercoaster.com> (message from World of Coasters on Mon, 29 Apr 1996 13:06:22 -0700)


> OK, I installed Perl 5.002, re-installed majordomo,
> set all the permissions, and maajordomo test showed the
> correct gid and uid.
> 
> So, I create a group and then mail a request 'subscribe coasters'
> to majordomo. After another 15 minutes of heave load usage,
> I get a response, 'out of memory'. I reboot Linux and funny, majordomo
> starts up again and mails back another response:
> 
> >>>subscribe coasters
> 

(...)

> Here's what my top looked like at the peak mem usage:
> 
>  11:52pm  up 12 min,  1 user,  load average: 2.87, 2.33, 1.253
> 27 processes: 26 sleeping, 1 running, 0 zombie, 0 stopped3
> CPU states:  1.1% user,  5.2% system,  0.0% nice, 93.9% idle3
> Mem:   6984K av,  6856K used,   128K free,   568K shrd,   404K buff3
> Swap: 30740K av, 30684K used,    56K free3
> 3
>   PID USER     PRI  NI SIZE  RES SHRD STAT %CPU %MEM  TIME COMMAND3
>   151 bin       28   0 32003 4752  820 D     2.4 68.0  0:57 perl /usr/local/maj
(...)


I had the same problem when installing Majordomo. My problem was that
I forget to change the W_UID and W_GID in the Makefile file. Check
that they are set to the UID and GID values for the majordomo
user. When I send commands to majordomo 'top' shows the process with
USER 'majordomo', so that I think that you have something wrong since
your 'top' shows 'bin' as the owner of the process. Perhaps you set
the values of UID and GID for majordomo as the same for those of bin?
Check the file /etc/passwd. majordomo needs a UID and GID different
from all the others and in between 1 and 99. 

I run Majordomo in a 486 50Mhz with Linux. At the same time, the
machine is running a Boundary Element program that takes almost 99% of
the CPU and memory and Majordomo processes a lot of requests (I came
to subscribe 80 people in one command) on the fly. So that be sure
that you have something wrong in your settings.

Hope this help you,

Mario

-- 
%%%%%%<>%%%%%%<>%%%%%%<>%%%%%%<>%%%%%%<>%%%%%%<>%%%%%%<>%%%%%%<>%%%%%%<>
Dr. Mario Alberto Storti (mstorti@galileo.unl.edu.ar)
Grupo de Tecnologia Mecanica del INTEC
Instituto de Desarrollo Tecnologico para la Industria Quimica
Guemes 3450 - 3000 Santa Fe, Argentina
Fax: (54)(42) 55.09.44, Tel: (54)(42) 55.91.75
Home: Gob. Vera 3161, 3000 - Santa Fe. Tel: (54)(42) 55.00.23
%%%%%%<>%%%%%%<>%%%%%%<>%%%%%%<>%%%%%%<>%%%%%%<>%%%%%%<>%%%%%%<>%%%%%%<>


References:
Indexed By Date Previous: Re: Munge Domain fails to munge domain ;)
From: Fuzzy <fuzzy@ASARian.org>
Next: Re: Archive problem
From: bcerra@intellicorp.com
Indexed By Thread Previous: Re: It wasn't meant to be.
From: Keith Reding <kreding@info.aphis.usda.gov>
Next: Munge Domain fails to munge domain ;)
From: Fuzzy <fuzzy@ASARian.org>

Google
 
Search Internet Search www.greatcircle.com