[Mailman-Users] qrunner

Richard Barrett r.barrett at openinfo.co.uk
Thu May 6 23:36:27 CEST 2004


On 6 May 2004, at 22:00, tikkliknl wrote:

> Well it was a new install, but there was an old not used version 
> pressent.
> i installed python 2.3.3

Did you install it in the same location as and replacing any previous 
version of python on the system?

> looking at ps -aux i see this:
>
> mailman  28884  0.1  0.9  5964 4792 ?        S    22:55   0:00
> python2.3 /home/mailman/bin/mailmanctl -s start
> mailman  28885  2.8  0.8  5736 4600 ?        S    22:55
> 0:00 /usr/local/bin/python2.3 /home/mailman/bin/qrunner --
> runner=ArchRunner:0:1 -s
> mailman  28886  3.0  0.8  5748 4612 ?        S    22:55
> 0:00 /usr/local/bin/python2.3 /home/mailman/bin/qrunner --
> runner=BounceRunner:0:1 -s
> mailman  28887  2.8  0.8  5740 4596 ?        S    22:55
> 0:00 /usr/local/bin/python2.3 /home/mailman/bin/qrunner --
> runner=CommandRunner:0:1 -s
> mailman  28888  2.8  0.8  5744 4600 ?        S    22:55
> 0:00 /usr/local/bin/python2.3 /home/mailman/bin/qrunner --
> runner=IncomingRunner:0:1 -s
> mailman  28889  3.1  0.8  5752 4636 ?        S    22:55
> 0:00 /usr/local/bin/python2.3 /home/mailman/bin/qrunner --
> runner=NewsRunner:0:1 -s
> mailman  28890  2.9  0.9  5764 4668 ?        S    22:55
> 0:00 /usr/local/bin/python2.3 /home/mailman/bin/qrunner --
> runner=OutgoingRunner:0:1 -s
> mailman  28891  2.9  0.8  5744 4600 ?        S    22:55
> 0:00 /usr/local/bin/python2.3 /home/mailman/bin/qrunner --
> runner=VirginRunner:0:1 -s
> mailman  28892  3.3  0.8  5736 4600 ?        S    22:55
> 0:00 /usr/local/bin/python2.3 /home/mailman/bin/qrunner --
> runner=RetryRunner:0:1 -s
>
> only thing i changed was when starting mailmanctl it looked for 
> qrunner but
> he didnt find it

which indicates something went wrong with your installation if your 
install $prefix was /home/mailman and the 'make install' did not put a 
copy of the MM 2.1.4 qrunner into /home/mailman/bin

> so i put t there

put what from where to where?

> fronm the install files.

If the 'make install' had executed correctly you should not have had to 
copy over/install any files by hand.

MM 2.1.4 does not normally execute a file called $prefix/cron/qrunner 
and not from its normal crontab. If cron is trying to execute a qrunner 
scr8pt it is probably the old Mailman installation's crontab that is so 
doing. Did you check that this had been removed before you installed 
the new MM 2.1.4 crontab? Did you install the MM 2.1.4 crontab?

The syntax error you reported originally could come about if:

1. your old MM crontab was not removed

2. you copied a copy of the MM 2.1.4 qrunner into $prefix/cron/

3. your old MM crontab referenced an older python installation still on 
your system and not the Python 2.3.3 you have installed

4. as a result, an entry in the old MM crontab tried to execute the 
(daemon) qrunner used by MM 2.1.4 with an old version of python which 
saw a feature used in the new code as being a syntax error

> thanxs
> steffan.
>
>> Hello did a new install of mailman 2.1.4 now cron gives this error
>>
>> File "/home/mailman/cron/qrunner", line 96
>>     print >> fd, _(__doc__)
>>            ^
>> SyntaxError: invalid syntax
>
>> any idees
>>
>
> what version of python are you running? the README says
>
>
> MM 2.1.x normally operates its qrunners as daemons, unlike MM 2.0.x 
> which
> used a cron executed qrunner.
>
> You appear to have a cron based qrunner yet say you are running a newly
> installed MM 2.1.4.
>
> Did you install this over an earlier MM 2.0.x install and if so did you
> remove the old crontab before installing the one for the newer release?
>





More information about the Mailman-Users mailing list