acct_mgr-0.4.4: Corrupting .ini

[massimo.b@…]

I tried both versions, 0.4.4 and 0.4.2 with trac-1.0.3 and python 2.7.9-r1 on Gentoo-Linux.

After installing the plugin the procject .ini file gets corrupted to:

# -*- coding: utf-8 -*-

[account-manager]
login_attempt_max_count = 0

[components]
trac.web.auth.loginmodule = disabled

I tried with and without configuration of the [account-manager]. I'm running tracd standalone behind a forwarding Nginx:

/usr/bin/python2.7 /usr/bin/tracd -p 8000 --auth=project,/mnt/data/trac/htpasswd/users.htdigest,project_test /mnt/data/trac/project

After selecting the Trac project on the homepage the .ini file shrinks to 4 lines and the project is not usable anymore.

[Steffen Hoffmann]

More information is required to proceed.

If trac.ini gets corrupted, this is a sign, that a version other than 0.4.4 is effectively installed. The component overwrite for Trac core's LoginModule has been made soft when working for #10871 in [12609] towards 0.4.3, and nobody else has reported configuration corruption ever since.

It might happen due to wired Trac plugin interference, but to see this, you'll have to turn Trac logging on at DEBUG level and record from right before environment restart (to see all module's loading) until the time the ini has been shrunken. I bet there would something important to learn from these log lines.

[massimo.b@…]

Hm sorry, today I cannot reproduce.

I had 0.4.2 installed by distributions package manager on Gentoo Linux having this issue. Then I deinstalled and tried the zipped sources, build the egg. Same issue.

Today I tried again with svn trunk, but also with the 0.4.4 zipped sources, without an issue. Now I just have "AccountModule is disabled because the password store does not support writing", which I guess I will solve after reading the docs.

[Steffen Hoffmann]

Replying to massimo.b@…:

I had 0.4.2 installed by distributions package manager on Gentoo Linux having this issue. Then I deinstalled and tried the zipped sources, build the egg. Same issue.

I suggest this happened due to not properly re-loading the updated plugin.

No need for excuses. I take your last comment as confirmation, that 0.4.4 is ok for you now, and never think about obsolete version 0.4.2, but thank you for the additional test feedback.

Please re-open and explain more, if further investigation speak against this solution.