On 31. aug.. 2008, at 11.39, Chris Searle wrote: >> there are some DB maintenance scripts you need to run. read the >> install README file. this happened to me, too :) > > Do you recall which ones? > > After running make upgrade from 3.8.0 to 3.8.1 I ran > > /opt/rt3/sbin/rt-setup-database --dba root --prompt-for-dba-password > --action upgrade > > And when asked - entered 3.8.0 as the version being upgraded from. > > However - I'm still getting asked to login for most clicks. > > I'm a little confused as to what maintenance script didn't get run > here.
Been digging here - still not getting anywhere. Checked the sessions table structure - CREATE TABLE sessions ( id char(32) NOT NULL, a_session longtext, LastUpdated timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP, PRIMARY KEY (id) ) ENGINE=InnoDB DEFAULT CHARSET=latin1; which looks very similar to etc/schema.mysql CREATE TABLE sessions ( id char(32) NOT NULL, a_session LONGTEXT, LastUpdated TIMESTAMP, PRIMARY KEY (id) ); The table was originally MyISAM (was the only one that was) - changed it to InnoDB on the offchance - made no difference in behaviour. Its odd - here's an example. Login - you're logged in Click 'Tickets' - you get the tickets query form Choose an owner and hit 'add these terms' - you get to the login screen Login again - you get to the tickets form _with_ the query updated. I've tried clearing the old session table (well - dumping it to disk then truncating it) - no change. The 3.8.0 backup - that works fine with no issues. _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com