[Mailman-Users]HandlerAPE error: WAS :Listserv wide announcements?

[Bruce Mitzit]

Hey, Richard--

>
>I know it is a bit obvious but you have used the crontab command to 
>double check that the old Mailman crontab is still not extant and 
>being executed on behalf of some user or another.

Yeh, it is and I did that...blixxed whatever mailman might have had 
with "# crontab -r mailman", edited out of root's cron the mailman 
stuff.

>
>If it were me trying to do what you suggest, I would;
>
>1. rename the current /usr/local/mailman and take a backup of it
>
>2. mkdir /usr/local/mailman
>
>3. use mv to put /usr/local/mailman.old/lists and 
>/usr/local/mailman.old/archives to /usr/local/mailman
>
>4. ./configure and make install MM 2.1.2 into /usr/local/mailman
>
>5. crank up the new MM install per the INSTALL file

I did that too, more or less. Started it up with total confidence but 
continued getting the error messages. I couldn't figure out where 
this cron job is...nowhere I put it. Checked the account of a former 
assistant capable of knowing what a cron is. Nothing there. Did a 
"find / -user mailman -name cron*" Interesting hit was an old Mailman 
2.0.13 install directory in /usr/src (assistant's work. I'd have put 
in /tmp). No reason to have it, rm -R'd it. Error messages stopped. 
Not yet using this new better-behaved iteration with entire 
confidence. We'll see. Thanks for prodding me in the right direction.

Bruce



>On Tuesday, August 12, 2003, at 10:35  pm, Bruce Mitzit wrote:
>
>>Richard---
>>
>>You're right, thanks. I have a number of files from the old install:
>>
>>	 Apr 16  2002 /usr/local/mailman/Mailman/Handlers/HandlerAPI.py
>>	Dec 20  2002 /usr/local/mailman/ bin/digest_arch
>>	Dec 20  2002 /usr/local/mailman/ bin/move_list
>>a bunch of cgi's,
>>	Apr 16 2002  ../cron/qrunner
>>
>>I removed HandlerAPI.py, renamed cron/qrunnerBU (with current date) 
>>to qrunner. Gave it 755 perms.
>>
>>This has not seemed to have calmed things down.
>>If I wanted to do a clean install --start from scratch-- what 
>>directories in /usr/local/mailman/ should I keep?
>>
>>
>>
>>
>>
>>
>>>On Tuesday, August 12, 2003, at 07:23  pm, Bruce Mitzit wrote:
>>>
>>>>At 3:33 PM +0100 8/12/03, Richard Barrett wrote:
>>>>>On Tuesday, August 12, 2003, at 03:10  pm, Bruce Mitzit wrote:
>>>>>
>>>>>>
>>>>>>Hello, MM users---
>>>>>>
>>>>>>After upgrading from mailman 2.0.9 to mailman-2.1.2, and 
>>>>>>tweaking all the things I could find to tweak, I still get this 
>>>>>>error emailed to me at the rate of about three a minute:
>>>>>>
>>>>>>Your "cron" job on urserver.uchicago.edu
>>>>>>/usr/local/bin/python -S /usr/local/mailman/cron/qrunner
>>>>>>produced the following output:
>>>>>>
>>>>>>Traceback (most recent call last):
>>>>>>   File "/usr/local/mailman/cron/qrunner", line 89, in ?
>>>>>>     from Mailman.Handlers import HandlerAPI
>>>>>>   File "/usr/local/mailman/Mailman/Handlers/HandlerAPI.py", line 26, in ?
>>>>>>     from Mailman.pythonlib.StringIO import StringIO
>>>>>>ImportError: No module named pythonlib.StringIO
>>>>>>
>>>
>>>Well some of your old MM installation is executing to generate 
>>>these warnings. The traceback is from MM 2.0.x code as the 
>>>Mailman/Handlers/HandlerAPI.py file is not in the MM 2.1.2 
>>>distribution; well its in MM 2.0.13 but not in MM 2.1.2 on my test 
>>>system.
>>>
>>>>>
>>>>>With Mailman 2.1.2 the qrunner is no longer run as a cron job.
>>>>>
>>>>>The 2.1.2 qrunners are run as daemons started by the 
>>>>>$prefix/bin/mailmanctl script.
>>>>>
>>>>>Looks like, maybe, you did not remove the mailman user's crontab 
>>>>>before doing the update and the old 2.0.9 crontab is still 
>>>>>trying to do stuff.
>>>>>
>>>>>Did you take a look at the section 'UPGRADING FROM 2.0.x to 2.1' 
>>>>>in the UPGRADING file in your MM 2.1.2 build director as part of 
>>>>>your tweakingy?
>>>>
>>>>Richard et. al.--
>>>>
>>>>Well, yeah, I did read that thing. I did not remove (in Solaris 
>>>>7) /var/spool/cron/cronjobs/mailman prior to the install.
>>>>
>>>>So, I've rm'd that cronjob. We'd been running that cron from root 
>>>>anyway, so I commented all out from there as well.  I did a 
>>>>configure, make install all over again. I still am getting the 
>>>>same error message by email. Any suggestions? The original 
>>>>install of MM made me feel pretty smart. This one makes me feel 
>>>>dumb.
>>>>
>>>
>>>If messages reporting the same error are still turning up then 
>>>either the mail system has a backlog it is drip feeding you or 
>>>there is still another crontab which executes the old MM qrunner 
>>>script in place and enough old MM code extant to generate the 
>>>error.
>>>
>>>>Bruce
>>>>
>-----------------------------------------------------------------------
>Richard Barrett                               http://www.openinfo.co.uk


--