[request-tracker-maintainers] Bug#560015: Bug#560015: request-tracker3.6: Upgrade to 3.6.1-4+etch1 results in request tracker unable to login

[Paul Gear]

On 08/12/09 21:11, Dominic Hargreaves wrote:
> On Tue, Dec 08, 2009 at 08:08:52PM +1000, Paul Gear wrote:
>> Upgrading my system to 3.6.1-4+etch1 (as announced in DSA-1944-1) causes
>> Request Tracker to report 'not logged in' every time a link is clicked
>> or a form is submitted.  This occurs no matter which user i login as.  I
>> found some additional instructions about this patch at
>> http://lists.bestpractical.com/pipermail/rt-announce/2009-November/000176.html
>> which suggests that the mason object cache needs to be cleared.  I did
>> this in /var/cache/request-tracker3.6/mason_data/obj on my system, but
>> it had no effect.  Downgrading to 3.6.1-4 again resolves the problem.
>> My database is postgresql and my MTA is postfix, but these do not seem
>> to affect the problem in any way.
>
> The Mason cache should be cleared by the package postinst, so that
> shouldn't be an issue.
>
> The patches were tested with an sqlite database; I'll see if I can
> reproduce your problem this evening. In the meantime, are any errors
> logged by RT (in /var/log/request-tracker3.8. syslog, or web server
> error log, depending on how you have things configured) at the time
> that it was broken?

This bug may be closed - version 3.6.7-5+lenny4 does not have this 
problem and is the currently supported version on lenny.  I have 
successfully upgraded my system to this version without the issue 
reoccurring.

Regards,
Paul