On Mon, Jun 06, 2011 at 10:44:46AM -0400, Joshua Knarr wrote:
> I just tracked this down to the password changing in the database...
>
> If I try to log in after upgrading - it works for awhile then stops
> working. The question is
> why?
>
> The workaround:
> UPDATE Users SET Password=md5('password') WHERE Name='knarrj';
>
> This isn't good. I would vastly prefer to not have to run the upgrade
> again and I would really
> like to use the old passwords. Is there a workaround? What changed?What changed was http://lists.bestpractical.com/pipermail/rt-announce/2011-January/000185.html It is also documented in docs/UPGRADING-3.8 It sounds like you have an extension somewhere that clobbers the new password checking routine. It also sounds like you missed some parts of the upgrade. -kevin > On Mon, 2011-06-06 at 09:29 -0400, Joshua Knarr wrote: > > I am upgrading from RT 3.4.5 to RT 4. > > I read the docs and stopped at 3.8, did the schema stuff, and then > continued to 4 per the > instructions for upgrading mysql also. > > On the new system it runs for a few hours just fine, but then suddenly > everyones account > gets locked. > > I restarted the services, I checked my configs, I'm coming up empty. > What went wrong or > where should I be looking?
pgp7pWlhCEW8Y.pgp
Description: PGP signature
