RT requiring login for every click

RT Users
21

there are some DB maintenance scripts you need to run. read the
install README file. this happened to me, too :slight_smile:

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.

22

Chris Searle chris+lists@chrissearle.org writes:

there are some DB maintenance scripts you need to run. read the
install README file. this happened to me, too :slight_smile:

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.

Output of

show create table sessions;

?

Espen Wiborg espen.wiborg@telio.no
Compared to system administration, being cursed forever is a step up.
- Paul Tomko in the Monastery

23

there are some DB maintenance scripts you need to run. read the
install README file. this happened to me, too :slight_smile:

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.

24

this my describe table output:

id | varchar(32) | | PRI | | |
| a_session | longtext | YES | | NULL | |
| LastUpdated | timestamp | YES | | CURRENT_TIMESTAMP |

and show create table:

| sessions | CREATE TABLE sessions (
id varchar(32) NOT NULL default ā€˜ā€™,
a_session longtext,
LastUpdated timestamp NOT NULL default CURRENT_TIMESTAMP on update
CURRENT_TIMESTAMP,
PRIMARY KEY (id)
) ENGINE=MyISAM DEFAULT CHARSET=latin1 |

There is wrong vlaues?

M.

Marco Avvisano
Regione Toscana - Giunta Regionale
Direzione Generale Organizzazione - Servizio I.I.T.R.
Via di Novoli, 26 - 50127 Firenze (Italy)
Tel. +39.055.438.3809 - Fax +39.055.438.5101
e-mail: m.avvisano@regione.toscana.it----- Original Message -----
From: ā€œChris Searleā€ chris+lists@chrissearle.org
To: rt-users@lists.bestpractical.com
Sent: Monday, September 01, 2008 10:43 PM
Subject: Re: [rt-users] RT requiring login for every click

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 :slight_smile:

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.

The rt-users Archives

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RTā€™s hidden secrets with RT Essentials from Oā€™Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

25

Iā€™d certainly be interested in what changes (if any) were made in
session handling 3.8.0 ā†’ 3.8.1On 2. sepā€¦ 2008, at 18.13, Trenton Taylor wrote:

I went back to 3.8.0 and everything is working fine ā€¦ Do you think
there is any problem with running 3.8.0 against a 3.8.1 database
upgrade? I didnā€™t restore back to my 3.8.0 database because Iā€™ll
lose a
couple hundred tickets ā€¦

Not sure what to do but I think you guys are in the same place I am.

Thanks,
Trent

-----Original Message-----
From: rt-users-bounces@lists.bestpractical.com
[mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Marco
Avvisano
Sent: Tuesday, September 02, 2008 3:52 AM
To: Chris Searle; rt-users@lists.bestpractical.com
Subject: Re: [rt-users] RT requiring login for every click

this my describe table output:

id | varchar(32) | | PRI | | |
| a_session | longtext | YES | | NULL | |
| LastUpdated | timestamp | YES | | CURRENT_TIMESTAMP |

and show create table:

| sessions | CREATE TABLE sessions (
id varchar(32) NOT NULL default ā€˜ā€™,
a_session longtext,
LastUpdated timestamp NOT NULL default CURRENT_TIMESTAMP on update
CURRENT_TIMESTAMP,
PRIMARY KEY (id)
) ENGINE=MyISAM DEFAULT CHARSET=latin1 |

There is wrong vlaues?

M.

Marco Avvisano
Regione Toscana - Giunta Regionale
Direzione Generale Organizzazione - Servizio I.I.T.R.
Via di Novoli, 26 - 50127 Firenze (Italy)
Tel. +39.055.438.3809 - Fax +39.055.438.5101
e-mail: m.avvisano@regione.toscana.it

----- Original Message -----
From: ā€œChris Searleā€ chris+lists@chrissearle.org
To: rt-users@lists.bestpractical.com
Sent: Monday, September 01, 2008 10:43 PM
Subject: Re: [rt-users] RT requiring login for every click

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 :slight_smile:

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.

The rt-users Archives

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RTā€™s hidden secrets with RT Essentials from Oā€™Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

The rt-users Archives

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RTā€™s hidden secrets with RT Essentials from Oā€™Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.169 / Virus Database: 270.6.14/1646 - Release Date:
2008-09-01 6:03 PM

Important: The information contained in this e-mail message is
confidential and is intended only for the named addressee(s). If the
reader of this e-mail message is not an intended recipient (or the
individual responsible for the delivery of this e-mail message to an
intended recipient), please be advised that any re-use,
dissemination, distribution or copying of this e-mail message is
prohibited. If you have received this e-mail message in error,
please reply to the sender that you have received the message in
error and then delete it. Thank you.