a great help to
me when the original problem came up, and this has worked great in an
environment where servers can be rebooted without notice.
On 04/07/2015 01:22 PM, Mark Sapiro wrote:
On 04/07/2015 08:09 AM, Jeff Taylor wrote:
I've been running the modified slice code (three slice serve
I've been running the modified slice code (three slice servers plus one
backup server) for the past couple years, and generally speaking it has
run perfectly. However every now and then I find that mailman is
suddenly not running on any of the servers, with no helpful information
showing in th
text
messages).
On 05/25/2014 12:07 PM, Richard Damon wrote:
On 5/24/14, 9:53 PM, Jeff Taylor wrote:
Its odd, I could have sworn the slicing used to be done per recipient,
not per message. I've had to check logs for a client to confirm her
messages went out, and generally had check all three m
add more redundancy to ensure the out queue
would get processed, even if it took a couple minutes for a backup
machine to get to them.
On 05/25/2014 10:52 AM, Mark Sapiro wrote:
On 05/24/2014 06:53 PM, Jeff Taylor wrote:
Its odd, I could have sworn the slicing used to be done per recipient,
not
On 05/24/2014 03:05 PM, Jeff Taylor wrote:
After stopping mailman, machine #1 shows:
May 24 15:23:34 2014 (11512) Master qrunner detected subprocess exit
(pid: 11516, sig: None, sts: 15, class: IncomingRunner, slice: 1/3)
Machine #2:
May 24 15:21:56 2014 (12767) Master qrunner detected subpr
After stopping mailman, machine #1 shows:
May 24 15:23:34 2014 (11512) Master qrunner detected subprocess exit
(pid: 11516, sig: None, sts: 15, class: IncomingRunner, slice: 1/3)
Machine #2:
May 24 15:21:56 2014 (12767) Master qrunner detected subprocess exit
(pid: 12769, sig: None, sts: 15, clas
The entire QRUNNERS section on the machines looks like this:
QRUNNERS = [
('ArchRunner', 3,0,3), # messages for the archiver
('BounceRunner', 3,0,3), # for processing the qfile/bounces directory
('CommandRunner', 3,0,3), # commands and bounces from the outside
world
('Inc
After doing some upgrades, I noticed yesterday that my multi-machine
setup is no longer properly slicing the queue between machines. I
probably missed something, but after going through all my notes on the
setup I cannot figure out what the problem in. Hopefully someone else
can spot the issu
couple
years. Thanks!
On 04/09/2014 04:32 PM, Jeff Taylor wrote:
I just upgraded an old ubuntu machine from oneiric to precise, and now
I cannot get mailman to run. Something starts up long enough to set a
pid file, but then it simply dies. There is nothing being added to
either syslog or any
I just upgraded an old ubuntu machine from oneiric to precise, and now I
cannot get mailman to run. Something starts up long enough to set a pid
file, but then it simply dies. There is nothing being added to either
syslog or any of the mailman log files. I tried reinstalling mailman,
and mad
No problems, I'm at least aware of the indented nature of python. I'll
get this code added in later in the week and give it a trial run, see
what happens. Thanks!
On 12/23/2012 02:55 PM, Mark Sapiro wrote:
> Stephen J. Turnbull wrote:
>
>> Mark Sapiro writes:
>>
>> Python is indentation-sensiti
I have been running mailman 2.1 from three servers with NFS sharing for
the past couple years, but due to a recent issue I did some digging and
found the suggestions for clustering at
http://mail.python.org/pipermail/mailman-users/2008-March/060753.html
(the post by Mark Sapiro detailing how to set
12 matches
Mail list logo
