Christopher Adams wrote:
>I noticed that messages weren't being delivered. So, I checked the
>mailman error logs and noticed something about a master qrunner lock. I
>found something in the /locks directory names master qrunner and deleted
>it. Then I restarted mailman and got this:
>
>./mailma
I noticed that messages weren't being delivered. So, I checked the
mailman error logs and noticed something about a master qrunner lock. I
found something in the /locks directory names master qrunner and deleted
it. Then I restarted mailman and got this:
./mailmanctl restart
Restarting Mailman'
Another quick update: I had old queue files in qfiles/out. So I
cleared out everything in the folder and restarted all the qrunners.
Now I can get the OutgoingRunner to send one post or one message.
After it's restarted, it sends one message correctly. The next post
or confirmation message after t
I have just tested a post to a new list created with the 2.1.2
mailman. Pretty much the same behavior, the .pck and .db files are
created in qfiles/out. They look normal when I peek in with dumpdb.
But nothing leaves the machine. No apparent errors anywhere.
Can I run the "qrunner --runner=Outgoin
I've just upgraded my Mailman installation from a 2.0.x to a 2.1.2
on a Solaris 8 server using Python 2.2.2. And I think I have a
problem with the OutgoingRunner but I can't put my finger on it.
Here a the symtoms:
1. After I start mailman, the mailmanctl never exits. I can still
see it in the
