Hi Anthony, Am 17.02.11 17:31, schrieb Anthony Veale: > I followed the instructions for "Installing on Linux from source" on: > > http://www.agile42.com/cms/pages/download-install/ > > I ran "python setup.py bdist_egg", then I copied the egg file into the > testbed trac instance.
Hrm, damn, thats of course not a good starting point - I'll update that immediately. > I had initially put in the shared plugin area, but then I thought > better of that and moved it from the shared area to the local plugin > area for the testbed instance and restarted the apache server. Probably installing it (with easy_install) into the shared plugin path would be better, as the egg would not need to be unzipped by each process that accesses it in some way which IMO (as Felix said) is the reason you are seing this behaviour from the auto updater. >> How do you serve your tracs? mod_python or mod_wsgi, how do you separate >> the processes that serve the different tracs? > > They are handled through mod_python in apache2 with separate > <Location> tags for each instance. I imagine that does not do much > for truly isolating the trac instances. > > Still, this is the first sign I have seen of any cross-talk between > the trac instances that wasn't an obvious mistake I made. (Not saying > this isn't a mistake I made, just that it isn't obvious.) Yep. Sadly and as Felix noted mod_python is known for these types of interactions that can be really hard to debug. >> From your description my first guess would be that you installed the >> binary egg (in zip form) to a shared location and that the way you run >> the different trac environments leads to a shared instance of a not >> threadsafe setuptools being used by all of them. > > Well, I have the recommended minimum version of setuptools, > python-setuptools-0.6c9, installed, but I didn't do anything specific > with setuptools, except whatever the included setup.py with agilo > might have done. > > The egg is installed under the plugin directory specific to the > testbed trac instance, though it was at one time installed in the > shared plugin directory. Apache has been fully stopped and restarted > several times since removing agilo from the shared plugin directory. > > All of these plugin directories are specific to the trac directories. > They are not in the python paths, so that only trac instances (and > currently only the testbed trac instance) should be able to find them. I guess the reason really is that mod_python and setuptools interact in a weird way in this multi-threaded environment. As Felix mentioned, swithing over to mod_wsgi is probably a good option, and you can also try installing the egg with easy_install into a shared location and then referencing it from there. In the long run, I would recommend going with mod_wsgi - but that change will probably require even more testing. > Yes, the joy of running software in production environments. There is > a openSuse build service upgrade to 0.12.2 available, but I will have > to install the upgrade in test and measure the functionality of > roughly a dozen plugins before I will be allowed to deploy. Weeks > away, at least, on my current priority list. :-) Oh I can so sympathize. :-) If you want to have an easier upgrade path, going to 0.11.7 is probably _a lot_ simpler as Trac is quite good about keeping interfaces compatible in minor version updates. -- Regards / Mit freundlichen Grüßen Martin Häcker Software Engineer Agilo Software GmbH Gruenberger Str. 54 10245 Berlin, Germany [email protected] http://www.agiloforscrum.com Amtsgericht Charlottenburg: HRB 127146 CEO Marion Eickmann, Andrea Tomasini -- Follow Agilo on Twitter: http://twitter.com/agiloforscrum Please support us by reviewing and voting on: http://userstories.com/products/8-agilo-for-scrum http://ohloh.net/p/agilo-scrum http://freshmeat.net/projects/agiloforscrum You have received this message because you are subscribed to the "Agilo for Scrum" Google Group. This group is focused on supporting Agilo for Scrum users and is moderated by Agilo Software GmbH <http://www.agiloforscrum.com>. To post to this group, send email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/agilo
