Forum Problems Installing LAMS: Can't login as administrator after install


 
You may request notification for Can't login as administrator after install.
Search: 

1: Can't login as administrator after install
04/06/09 05:18 AM
[ Reply | Forward ]
Hi

I've managed to get LAMS up and running behind Apache using mod_jk on CentOS 5.2 linux :)

However when I go to the LAMS login screen for the very first time and enter the login details for the administrator as provided in the lams.properties file I get the message:

Sorry, that username or password is not known. Please try again.

In the lams.log file I get the following messages:

2009-04-06 12:02:51,735 [TP-Processor6:] INFO org.lamsfoundation.lams.security.UniversalLoginModule - initialize
2009-04-06 12:02:51,735 [TP-Processor6:] INFO org.lamsfoundation.lams.security.UniversalLoginModule - login
2009-04-06 12:02:51,770 [TP-Processor6:] INFO org.lamsfoundation.lams.security.UniversalLoginModule - abort

Any suggestions what I am doing wrong?

Thanks very much in advance

Clive

Posted by Clive Gould

2: Re: Can't login as administrator after install
In response to 1 04/06/09 12:12 PM
[ Reply | Forward ]
Some additional information...

DEBUG logs are shown below for a failed login session:
(all logs cleared immediately before login attempt i.e. cat /dev/null > logfilename)

ls -la
total 9852
drwxr-xr-x 2 root root 4096 Apr 6 18:54 .
drwxr-xr-x 9 root root 4096 Apr 4 21:08 ..
-rw-r--r-- 1 root root 0 Apr 6 18:55 audit.log
-rw-r--r-- 1 root root 0 Apr 6 18:55 boot.log
-rw-r--r-- 1 root root 0 Apr 6 18:57 hibernatelams.log
-rw-r--r-- 1 root root 0 Apr 6 18:56 hibernatelams.log.1
-rw-r--r-- 1 root root 0 Apr 6 18:56 hibernatelams.log.2
-rw-r--r-- 1 root root 1727 Apr 6 18:57 lams.log
-rw-r--r-- 1 root root 377 Apr 6 18:57 localhost_access_log.2009-04-06.log
-rw-r--r-- 1 root root 27226601 Apr 6 19:02 server.log


less lams.log
2009-04-06 18:57:20,450 [TP-Processor8:] DEBUG org.lamsfoundation.lams.web.session.SessionManager - ==>Couldn't find the sso cookie
2009-04-06 18:57:20,451 [TP-Processor8:] DEBUG org.lamsfoundation.lams.web.session.SessionManager - ==>Created one - 8ae48091207c90b301207c93c5c3006f
2009-04-06 18:57:20,480 [TP-Processor8:] INFO org.lamsfoundation.lams.security.UniversalLoginModule - initialize
2009-04-06 18:57:20,481 [TP-Processor8:] INFO org.lamsfoundation.lams.security.UniversalLoginModule - login
2009-04-06 18:57:20,482 [TP-Processor8:] DEBUG org.lamsfoundation.lams.security.UniversalLoginModule - ===> authenticating user: admin
2009-04-06 18:57:20,619 [TP-Processor8:] DEBUG org.lamsfoundation.lams.security.UniversalLoginModule - ===> authentication type: LAMS
2009-04-06 18:57:28,657 [TP-Processor8:] INFO org.lamsfoundation.lams.security.UniversalLoginModule - abort
2009-04-06 18:57:28,686 [TP-Processor8:] DEBUG org.lamsfoundation.lams.security.JspRedirectStrategy - ===>LOGIN PAGE: there is no auth obj in session or accessing login page before login succeed, auth obj created. session id: 3F02167933FF06F1E5AA1DDDD7308387
2009-04-06 18:57:28,687 [TP-Processor8:] DEBUG org.lamsfoundation.lams.security.JspRedirectStrategy - Set locale information for login page:en_GB
2009-04-06 18:57:28,773 [TP-Processor7:] DEBUG org.lamsfoundation.lams.web.session.SessionManager - ==>Couldn't find the sso cookie
2009-04-06 18:57:28,773 [TP-Processor7:] DEBUG org.lamsfoundation.lams.web.session.SessionManager - ==>Created one - 8ae48091207c90b301207c93e6450070
2009-04-06 18:57:28,773 [TP-Processor7:] DEBUG org.lamsfoundation.lams.web.session.SessionManager - SessionManager: cookie is null, generating a new session

less localhost_access_log.2009-04-06.log
195.69.92.72 - - [06/Apr/2009:18:57:19 +0000] "GET /lams/images/css/btn_over.gif HTTP/1.1" 304 -
10.100.0.17 - - [06/Apr/2009:18:57:28 +0000] "GET /lams//www/news.html HTTP/1.1" 200 3502
195.69.92.72 - - [06/Apr/2009:18:57:28 +0000] "POST /lams/j_security_check HTTP/1.1" 200 8919
195.69.92.72 - - [06/Apr/2009:18:57:28 +0000] "GET /lams/images/css/warning.gif HTTP/1.1" 304 -

server.log appears to be a binary file and as such is unreadable using the less pager

Posted by Clive Gould

3: Re: Can't login as administrator after install
In response to 2 04/07/09 12:53 AM
[ Reply | Forward ]
In desperation I have now compiled and installed the deparecated mod_jk2 instead of mod_jk and configured it using the instructions on the page http://www.lamsinternational.com/faq/advanced_p.php?g=modjk2

However once again when I try to login as administrator I am refused and the following lines appear in the lams.log file:

2009-04-07 07:47:05,216 [TP-Processor11:] INFO org.lamsfoundation.lams.security.UniversalLoginModule - initialize
2009-04-07 07:47:05,216 [TP-Processor11:] INFO org.lamsfoundation.lams.security.UniversalLoginModule - login
2009-04-07 07:47:05,218 [TP-Processor11:] DEBUG org.lamsfoundation.lams.security.UniversalLoginModule - ===> authenticating user: admin
2009-04-07 07:47:05,667 [TP-Processor11:] DEBUG org.lamsfoundation.lams.security.UniversalLoginModule - ===> authentication type: LAMS
2009-04-07 07:47:13,675 [TP-Processor11:] INFO org.lamsfoundation.lams.security.UniversalLoginModule - abort
2009-04-07 07:47:13,677 [TP-Processor11:] DEBUG org.lamsfoundation.lams.security.JspRedirectStrategy - ===>LOGIN PAGE: there is no auth obj in session or accessing login page before login succeed, auth obj created. session id: 3CBDDB916CDEC9A4CE2AC8AA03C394EF
2009-04-07 07:47:13,678 [TP-Processor11:] DEBUG org.lamsfoundation.lams.security.JspRedirectStrategy - Set locale information for login page:en_GB
2009-04-07 07:47:13,685 [TP-Processor12:] DEBUG org.lamsfoundation.lams.web.session.SessionManager - ==>Couldn't find the sso cookie
2009-04-07 07:47:13,686 [TP-Processor12:] DEBUG org.lamsfoundation.lams.web.session.SessionManager - ==>Created one - 8ae48091207f530601207f54a0160080
2009-04-07 07:47:13,686 [TP-Processor12:] DEBUG org.lamsfoundation.lams.web.session.SessionManager - SessionManager: cookie is null, generating a new session

Please what is wrong???

Thanks

Clive

Posted by Clive Gould

4: Re: Can't login as administrator after install
In response to 1 04/07/09 01:51 AM
[ Reply | Forward ]
I found the problem thanks to Jun-Dir.

I had set the language in lams.properties to en_GB, which did not exist in LAMS.

This meant that the locale field in the admin users entry in the lams database was NULL, preventing me from logging in as an administrator.

On changing this to entry to 1 (en_AU) all was well and I was able to log in as an administrator :)

Posted by Clive Gould

Reply to first post on this page
Back to Problems Installing LAMS
.LRN Home