[rt-users] Login Issues with Session data

[Scott Thomson]

Just in case anyone is googling with the same error's I was having,
somewhere in there my sessions database got the wrong type of data in it.
as described in the wiki, though my issue wasn't continuous login so much as
login click on something, click again and get error about non writable
/opt/rt3/var/session_data/.

Anyway,

I changed the table's data type back to longblob and I can now login, and
click more than twice before having to restart the browser.  This was in the
wiki here with slightly different symptoms that what I was experiencing:

http://wiki.bestpractical.com/view/TroubleShooting

Still having some other issues but we should be able to workaround/sort
those out.

Thanks!

Scott

On Mon, Dec 8, 2008 at 2:26 PM, Scott Thomson <scott.e.thomson at gmail.com>wrote:

> Hey Folks,
>
> So I'm stumped, I was having issues with rt 3.4.5 so I upgraded and the
> issues have followed me.
>
> We can log in, we can get to whatever we were logging in to see (ie our
> homepage, or a specific ticket if we specify the URL).  If we try to click
> on anything else, we get the following error message.
>
> RT couldn't store your session. This may mean that that the directory
> '/opt/rt3/var/session_data' isn't writable or a database table is missing or
> corrupt.
>
> I turned logging up to debug, and that didn't seem to turn anything up.
> I've been combing through the httpd and mysqld logs and haven't seen
> anything there either.
>
> This all started when I updated mysql from 4.1.20 to 4.1.22 and
> perl-5.8.5-36.el4_5.2 to perl-5.8.5-36.el4_6.3.
>
> Any ideas?  If we delete the info in the session data table, we can then
> log back in.  Otherwise it continues to give the error message unless we
> close and reopen the browser.
>
> We know that it sets a cookie with the session id in the browser as well.
> It just seems to be unable to process that session ID once it's established?
> Thanks!
>
> Scott
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20081210/ad7d6b7e/attachment.htm>