[haiku-web] Re: Trac trouble (WAS Re: [haiku-development] Re: Trac down, bug report here: efi_gpt.cpp has functions with wrong number of parameters)

Urias McCullough wrote:

On Fri, Jul 24, 2009 at 1:35 AM, Brecht Machiels<brecht@xxxxxxxxxxx> wrote:

Trac is being hosted using mod_python, right? Perhaps switching to fastCGI
might solve these problems...


Yes, it does use mod_python.

I know very little about python and the different ways of running it.
What does mod_python generally offer over fastcgi that would cause one
to use it instead?
Looking at http://trac.edgewall.org/wiki/TracModPython, it seems that mod_python is the recommended way to host Trac. I thought it might be worth trying to run Trac using FastCGI in order to see whether the problems disappear.
HaikuPorts runs Trac using FastCGI because of the lack of mod_python on Dreamhost servers. Fortunately, there is quite a lot of documentation on installing Trac on DH. Nevertheless, it took a lot of sweat and tears to get it running. But it seems to be running fine now. Of course, that is no guarantee that dev.haiku-os.org will run fine with FastCGI.
We could start from the HP setup to convert dev.haiku-os.org to FastCGI and see whether that improves things. Hopefully, with what I remember about that installation, that might be 'easy' (yeah right :). 


Is this a common problem with Trac? A quick search for "trac huge log"
doesn't bring up much. Might it have something to do with the Haiku-specific
changes (AFAIK, this is unlikely)?


In the past, things would reach a point where the log was filling with
errors every time someone hit the page(s). I found a few issues and
resolved them, such as the wrong versions of various added modules
(during the attempts to install Bitten). Unfortunately my lack of


What are the various added modules? Are these Trac plugins?


understanding of Python left me unable to really understand what could
be done to repair the situation, so I removed as much of the Bitten
stuff that I could find (since it wasn't working anyway). That brought
the stability back somewhat, but we still get occasional errors in the
log, sometimes errors about mismatched DB versions, but these go away
once you restart apache, which is strange.
Yes, very strange. And the problem only occurs after Trac has been running for quite a while, yes?
dev.haiku-os.org is using PostgreSQL instead of SQLite, right? SQLite is the default. I'm not sure whether the use of PostgreSQL as backend is wide-spread. This is another thing to look at besides mod_python. I would place PostgreSQL above mod_python on the suspect list.
I'm not sure how much work would be involved in switching to SQLite (and back again?). In any case, it feels dangerous. 


Frankly, I have little time to debug the existing solution on the
production server - I would rather build a fresh install somewhere
else (perhaps on my own local server) and see what the working pieces
look like so that I can educate myself on what is needed to
install/run Trac in the first place. Without this, I feel like I'm
poking in the dark.
Yes, it would probably be a good idea to start afresh, since the Trac installation has been 'tainted' a lot, from what I hear.
Niels already mentioned this kind of problem. He described it as a memory leak, which sounds logical, as it seems to take a while to blow up. 


If someone else has the knowledge and time, I think we could certainly
use some help.
As I said, I have some experience setting up Trac for HaikuPorts. Time, however... :) I'd be glad to have a look at it though.
Have the Trac developers been consulted about this problem? They might have a better feel of where to look. 

Regards,
Brecht
-----------------------------------------------------------------------
haiku-web@xxxxxxxxxxxxx - Haiku Web & Developer Support Discussion List

Other related posts: