Thorsten Scherler wrote:
On Thu, 2008-01-31 at 18:03 +1100, David Crossley wrote:
As you can see from recent forrestbot error messages to
this dev list, the dispatcher enabled test site is failing
with out-of-memory errors.
Hmm, weird. Why now and not before?
You probably already realise,
On Fri, 2008-02-01 at 11:05 +, Ross Gardler wrote:
Thorsten Scherler wrote:
On Thu, 2008-01-31 at 18:03 +1100, David Crossley wrote:
As you can see from recent forrestbot error messages to
this dev list, the dispatcher enabled test site is failing
with out-of-memory errors.
Hmm,
I re-enabled the forrest-sample-2 cronjob on our zone,
so the memory workaround will enable our forrest testing
services to continue.
I am not overjoyed at this. Remember that the zones server
is shared infrastructure.
-David
On Thu, 2008-01-31 at 18:03 +1100, David Crossley wrote:
As you can see from recent forrestbot error messages to
this dev list, the dispatcher enabled test site is failing
with out-of-memory errors.
Hmm, weird. Why now and not before?
We have not been getting all of the messages. I presume
As you can see from recent forrestbot error messages to
this dev list, the dispatcher enabled test site is failing
with out-of-memory errors.
We have not been getting all of the messages. I presume
that that is because jobs are hanging on the zone server.
I logged in and found 12 hung forrestbot