On Feb 17, 1:34 am, Martin Häcker <[email protected]>
wrote:
>
> This is defnitely strange and a bug. Agilo should not write this setting
> to disk every time it is invoked - especially if it is not active in
> that environment.
To clarify a bit, it is only writing the trac.ini file for the testbed
instance where agilo is installed. But within that trac.ini it
references the paths to other trac instances. So in the two other
projects, pm and libre, the trac.ini is not affected.
(I actually simplified list of trac instances: we have eleven
instances plus the testbed instance. The paths used in the testbed's
trac.ini span all eleven other instances at random. But none of the
other eleven trac.ini files gets modified.)
> To understand your problem better, how exactly did you build and install
> the egg? Is it still a binary egg, or is it decompressed? Global or
> local? ...
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.
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.
> 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.)
> 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.
> On another note, the trac version you are using is quite ancient
> (0.11.3) and contains known security holes in addition to being quite
> slow, so I would definitely recommend to go to the current 0.11 version
> 0.11.7.
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.
Anthony Veale
--
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
