Mark Sapiro wrote:
First check Mailman's logs, particularly 'error' and 'qrunner'. You
need to figure out why it died and fix that problem.
I got this when doing a stop/start:
Sep 25 13:51:15 2008 qrunner(29214): Traceback (most recent call last):
Sep 25 13:51:15 2008 qrunner(29214): File
Mark Sapiro wrote:
There is a master and 8 qrunners. Mail in the archives says
IncomingRunner and ArchRunner are running. It doesn't say
OutgoingRunner is running.
Here's the results of a ps aux | grep qrunner:
mailman 28584 0.0 0.3 13304 6912 ?S12:44 0:00
/usr/bin/python
Mustafa Akgul wrote:
did you ran mailman daemon ?
Either
/etc/init.d/mailman start
or
/var/lib/mailman/bin/mailmanctl
will do. You need to start it maunally, at the very beginning.
I had the same problem recently.
Yeah, I did that. I set it up to autostart too. I just doublechecked
and it'
For those following the saga... :)
My switch to our new server is proceeding well, but I've hit a snag that
I'm not sure what to do about.
Basically, Mailman is accepting messages just fine. They appear in the
Archives. The web interface works. I can watch the maillog and see the
message
Mark Sapiro wrote:
You didn't move the lists to the right place. RedHat puts things all
over the place to be FHS compliant. There should have already been a
/var/lib/mailman/lists/ directory which is where you should put your
lists/* subdirectories. Likewise, /var/lib/mailman/archives/private/.
Howdy!!
We've been running Mailman for years (about ten)... upgraded through the
years, finally ending up with 2.1.3 on an OLD copy of Red Hat Linux
(pre-Fedora). But that server died recently.
Now we have a shiny new server with a fresh copy of Fedora 9, and
Mailman 2.1.9. I did mana
