Please Help: Session expired when launching testlink 1.8beta

1.8 related questions and discussions.
Please upgrade to LATEST 1.9.x.
No more fixes for 1.8.

Moderators: Amaradana, TurboPT, TL Developers

Locked
testlc
TestLink user
Posts: 5
Joined: Tue Jul 29, 2008 8:46 am

Please Help: Session expired when launching testlink 1.8beta

Post by testlc »

I have upgraded my testlink from 1.7 to 1.8 beta2, the upgrade finishes successfully.

but when I browse to "http://[ip address]:[port]/testlink/login.php, whatever i input as user name/password, I always get the "Your session has expired....". I can never log on the testlink 1.8....Please could you help!

I also searched topics posted by other people, and followed their instructions, like set up php session path, time out value etc. But none sovled my problem.

Please note on the same environment, my testlink 1.7.4 works fine.

My environment is Windows 2003 Server +PHP5+Apache2

A million thanks in advance!
havlatm
Member of TestLink Community
Posts: 940
Joined: Mon Oct 31, 2005 1:24 am
Location: Czech

Post by havlatm »

Check that DB configuration file targets to the correct database. Check table 'users' in this DB.
testlc
TestLink user
Posts: 5
Joined: Tue Jul 29, 2008 8:46 am

Post by testlc »

havlatm wrote:Check that DB configuration file targets to the correct database. Check table 'users' in this DB.
Glad to see your reply thanks! I checked my db-cofig file it is targeting to the correct db.

I made a fresh new installation of 1.8beta, but still get the sessiion expired message when logging in, so I guess this is not to do with the db settings?

My testlink1.7 can work on the same php and apache environment, can i say this is not to do with the environment settings as well?

I guess for some reason testlink1.8beta remembers the original session id, thus when do session_start(), it fails to start a new session, is this possible? I am wondering where the old session information is stored? can you help?

Thanks a million!
fman
Member of TestLink Community
Posts: 3123
Joined: Tue Nov 15, 2005 7:19 am

Post by fman »

session info is save if I'm not wrong on cookies and on tmp dir (you can see config on php.ini).

Anyway do not do following action:

USE 1.7 with one browser and then with same browser login into 1.8, think this can create problems.
I suggest to have at least two differnt type of browsers (kmeleon, firefxo, ie, safari) and try with different browser to point different TL version
testlc
TestLink user
Posts: 5
Joined: Tue Jul 29, 2008 8:46 am

Post by testlc »

Thanks fman! Yes I found the session file under \windows\temp now. Here below is what i have examined:

1) Use different browser (IE, mathon, Firefox), get same result - session expired for 1.8beta2, ok for 1.7.

2) when using 1.7, type the url like http://[ip adress:port]/testlink1.7, the browser will add automatically the note expired to the above url, that is, it displays as "http://[ip adress:port]/testlink1.7/login.php?note=expired", however I can log on and use the system properly.

3) when using 1.8beta, always get the url like "http://[ip adress:port]/testlink1.8/login.php?note=expired", and unable to log on.
testlc
TestLink user
Posts: 5
Joined: Tue Jul 29, 2008 8:46 am

Post by testlc »

Anyway do not do following action:

USE 1.7 with one browser and then with same browser login into 1.8, think this can create problems.


Since I definitely have done the above action, that probably caused my current problem? any way to get out of it?
fman
Member of TestLink Community
Posts: 3123
Joined: Tue Nov 15, 2005 7:19 am

Post by fman »

what about clearing all session files, all cookies and browser cache ?

let me know
Christophe
TestLink user
Posts: 12
Joined: Wed Sep 16, 2009 4:52 pm

Post by Christophe »

Did you manage to solve this problem? What was the solution?

I have exactly the same problem with version 1.8.5 (only with IE, it works with Firefox...)

Thank you very much
Christophe
TestLink user
Posts: 12
Joined: Wed Sep 16, 2009 4:52 pm

Post by Christophe »

In Internet explorer, sessions do not work if the name of the server contains an underscore. For example...if your server is called web_server, if you call a page which uses sessions like http://web_server/example.php your sessions won't work but sessions will work if you call the script like this [IP NUMBER]/example.php
Locked