www.mantisbt.org/bugs seems to be responding slowly - do we have plans to try and fix this?

It does't look good to end users when it takes >20 seconds to render our own bug tracker.


On Thu, Oct 17, 2013 at 9:05 AM, Paul Richards <paul@mantisforge.org> wrote:
at work atm but: http://lists.xen.org/archives/html/xen-devel/2011-09/msg01461.html

On Thu, Oct 17, 2013 at 8:26 AM, Damien Regad <dregad@mantisbt.org> wrote:
On 2013-10-17 07:56, Victor Boctor wrote:
> Paul has suggested that we upgrade server to a new version of the OS /
> kernel due to a kernel bug that is causing the hangs (is this proven?).

Not proven, just a suspicion.

> Are others aware of any other work that we need to get done on the server?

The only thing which I think would be nice to have atm, is a more recent
version of Publican (docbook building tool). The one we have in 10.04
(1.0~20090927-2) is really outdated and sometimes causes issues (build
warnings or errors) when documentation build scripts run. Precise comes
with 2.8-2 which I use on my dev box and works fine.

> The other thing to discuss is the timing.  I would rather if we stay
> focused for the time being on getting 1.3.0a1 out of the door.  I don't
> want us distracted with environmental issues that are not critical
> causing us downtime, creating work, etc..


> *** DAMIEN REGAD ***
> Silence :) but he agreed based on follow up discussion.

Let me come out of my silence then ;-)

In light of the recent arguments put forward by Paul wrt some xen bug in
the kernel being a potential reason for the frequent crashes we're
suffering (it is not proven that it's indeed the root cause btw), I
think it would be worth a shot to try an upgrade now. I think
12.04LTS/precise has been out long enough that major issues would have
been sorted by now.

That said, except for the publican issue I mentioned above, there are no
major immediate benefits that I can see, other than running generally
more recent software - which can also be a shortcoming as we could be
introducing new issues ;-).

With regards to the upgrade process, I do not recommend upgrading
in-place, due to the long potential downtime and risk of failure
requiring restore.

As I was saying in some other e-mail, I think we should instead work on
a copy of mantisbt.org as a test platform. That means running 2 servers
concurrently (assuming Linode allows us to do that), the live site and a
test upgrade one. If the upgrade proves successful, then we can bring
mantisbt.org offline, copy the databases over to the upgraded box then
switch the images.


October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
mantisbt-dev mailing list