|
From: Chris W. <ch...@cw...> - 2002-04-12 12:13:31
|
On Fri, 2002-04-12 at 05:55, Jure Simsic wrote:
> I have the same problem still. As I'm trying to dig out the problem I've
> checked sessions in postgres and it seems that a session is written out
> the first time i log in:
> ...
> And with DEBUGging turned to 2 I get this errors in my modperl log:
>
> Found item: Apache::DBI::db
> (eval) (252) >> Trying to use cookie class: OpenInteract::Cookies::Apache
> OpenInteract::Cookies::Apache::parse (21) >> Getting cookie session to
> 532730127
> 96ad85a6a327ab7213feffd
> (eval) (254) >> Cookies in: $VAR1 = {
> 'session' => '53273012796ad85a6a327ab7213feffd'
> };
>
> (eval) (255) >> Trying to use session class: OpenInteract::Session::DBI
> OpenInteract::Session::DBI::_create_session (26) >> Trying to fetch
> session 53273012796ad85a6a327ab7213feffd
> OpenInteract::Session::parse (32) >> Retrieved session properly: $VAR1 = {
> '_session_id' => '53273012796ad85a6a327ab7213feffd'
> };
Ah, here's the issue. There should be a 'user_id' entry in here, as the
log says...
> OpenInteract::Auth::user (63) >> No uid found in session. Finding login
> info.
> OpenInteract::Auth::user (72) >> Creating the not-logged-in user.
> OpenInteract::Auth::group (256) >> No logged-in user found, not
> retrieving groups.
>
> What does this mean? Also, is it ok not to have last_accessed field in
> sessions empty? Are there be any other tables where session info gets
> written (or not) to check?
No, this is the only session table. Can you delete this cookie (or
delete the session from the database) and login again, with DEBUG still
set to 2. You should get a message before the session is created/saved
telling you what's in the session.
Chris
--
Chris Winters (ch...@cw...)
Building enterprise-capable snack solutions since 1988.
|