Forum Problems Installing LAMS: Re: Re: Re: Re: Re: Re: Problems logging into LAMS with "sysadmin"

By: Jun-Dir Liew

[ Reply | Forward ]

Sorry, looks like the installer is supposed to replace @confdir@ with the correct value - which should be /path/to/jboss-4.0.2/server/default/conf/ (replace with your correct path).

Posted by Jun-Dir Liew

By: Martyn Yap

[ Reply | Forward ]

Thanks alot ... got the login issue solved. Seems to have another problems arising.

Will update in awhile.

Cheers and many thanks. = ]

Posted by Martyn Yap

By: Jun-Dir Liew

[ Reply | Forward ]

Actually, you might also be missing the lamsauthentication.xml and lamsauthentication.dtd files - these are located in lams-unix-installer-2.0.4/conf/unix/authentication, and they go in jboss/server/default/conf/ as well.

Can you do the following - it'll run the section of the installer that copies the conf files for jboss (there are others I haven't mentioned):

cd lams-unix-installer-2.0.4
ant/bin/ant -buildfile ant-scripts/configure-deploy.xml copy-conf

Posted by Jun-Dir Liew

By: Martyn Yap

[ Reply | Forward ]

Yup, done that and I managed to login but it displays the HTTP500 error page instead.

Should I proceed to do a reinstall? Can't figure out what could be the problem here.

Cheers! = ]

--START SCREENDUMP AFTER LOGIN--
HTTP Status 500 -

--------------------------------------------------------------------------------

type Exception report

message

description The server encountered an internal error () that prevented it from fulfilling this request.

exception

org.apache.jasper.JasperException
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:370)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
org.lamsfoundation.lams.web.filter.LocaleFilter.doFilterInternal(LocaleFilter.java:151)
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:77)
org.springframework.orm.hibernate3.support.OpenSessionInViewFilter.doFilterInternal(OpenSessionInViewFilter.java:174)
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:77)
org.lamsfoundation.lams.web.session.SystemSessionFilter.doFilter(SystemSessionFilter.java:71)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)


root cause

java.lang.NullPointerException
org.apache.jasper.compiler.Localizer.getMessage(Localizer.java:56)
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:565)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:293)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
org.lamsfoundation.lams.web.filter.LocaleFilter.doFilterInternal(LocaleFilter.java:151)
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:77)
org.springframework.orm.hibernate3.support.OpenSessionInViewFilter.doFilterInternal(OpenSessionInViewFilter.java:174)
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:77)
org.lamsfoundation.lams.web.session.SystemSessionFilter.doFilter(SystemSessionFilter.java:71)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)


note The full stack trace of the root cause is available in the Apache Tomcat/5.5.9 logs.
--END SCREENDUMP AFTER LOGIN--

--START LAMS.LOG--
12:22:16,337 [http-0.0.0.0-8080-1:] 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: C4675EF35D22A4BA8C63332E5977141D
12:22:16,343 [http-0.0.0.0-8080-1:] ERROR org.lamsfoundation.lams.web.session.SessionManager - Failed on finding current system session with null sessionId
12:22:16,344 [http-0.0.0.0-8080-1:] DEBUG org.lamsfoundation.lams.web.filter.LocaleFilter - Locale set from server is en,AU
12:22:16,357 [http-0.0.0.0-8080-1:] DEBUG org.lamsfoundation.lams.security.JspRedirectStrategy - Set locale information for login page:en_US
12:22:16,392 [http-0.0.0.0-8080-1:] ERROR org.lamsfoundation.lams.web.session.SessionManager - Failed on finding current system session with null sessionId
12:22:16,484 [http-0.0.0.0-8080-2:] DEBUG org.lamsfoundation.lams.web.session.SessionManager - ==>Couldn't find the sso cookie
12:22:16,493 [http-0.0.0.0-8080-2:] DEBUG org.lamsfoundation.lams.web.session.SessionManager - ==>Created one - ff808081193bb64c01193bb82ea60049
12:22:16,493 [http-0.0.0.0-8080-2:] DEBUG org.lamsfoundation.lams.web.session.SessionManager - SessionManager: cookie is null, generating a new session
12:22:16,503 [http-0.0.0.0-8080-2:] DEBUG org.lamsfoundation.lams.web.session.SessionManager - SessionManager: creating new session ff808081193bb64c01193bb82ead004a
12:22:17,601 [http-0.0.0.0-8080-1:] 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: C4675EF35D22A4BA8C63332E5977141D
12:22:19,024 [http-0.0.0.0-8080-1:] ERROR org.lamsfoundation.lams.web.session.SessionManager - Failed on finding current system session with null sessionId
12:22:19,024 [http-0.0.0.0-8080-1:] DEBUG org.lamsfoundation.lams.web.filter.LocaleFilter - Locale set from server is en,AU
12:22:19,024 [http-0.0.0.0-8080-1:] DEBUG org.lamsfoundation.lams.security.JspRedirectStrategy - Set locale information for login page:en_US
12:22:19,025 [http-0.0.0.0-8080-1:] ERROR org.lamsfoundation.lams.web.session.SessionManager - Failed on finding current system session with null sessionId
12:22:19,026 [http-0.0.0.0-8080-2:] DEBUG org.lamsfoundation.lams.web.session.SessionManager - ==>Couldn't find the sso cookie
12:22:19,026 [http-0.0.0.0-8080-2:] DEBUG org.lamsfoundation.lams.web.session.SessionManager - ==>Created one - ff808081193bb64c01193bb83892004b
12:22:19,026 [http-0.0.0.0-8080-2:] DEBUG org.lamsfoundation.lams.web.session.SessionManager - SessionManager: cookie is null, generating a new session
12:22:19,026 [http-0.0.0.0-8080-2:] DEBUG org.lamsfoundation.lams.web.session.SessionManager - SessionManager: creating new session ff808081193bb64c01193bb83892004c
12:22:24,232 [http-0.0.0.0-8080-3:] INFO org.lamsfoundation.lams.security.UniversalLoginModule - initialize
12:22:24,234 [http-0.0.0.0-8080-3:] INFO org.lamsfoundation.lams.security.UniversalLoginModule - login
12:22:24,235 [http-0.0.0.0-8080-3:] DEBUG org.lamsfoundation.lams.security.UniversalLoginModule - ===> validatePassword() called: a159b7ae81ba3552af61e9731b20870515944538 :
12:22:25,246 [http-0.0.0.0-8080-3:] DEBUG org.lamsfoundation.lams.security.UniversalLoginModule - ===> authenticating user: sysadmin
12:22:25,251 [http-0.0.0.0-8080-3:] DEBUG org.lamsfoundation.lams.security.UniversalLoginModule - ===>dsJndiName = java:/jdbc/lams-ds
12:22:25,251 [http-0.0.0.0-8080-3:] DEBUG org.lamsfoundation.lams.security.UniversalLoginModule - ===>principalsQuery = select password from lams_user where login=?
12:22:25,251 [http-0.0.0.0-8080-3:] DEBUG org.lamsfoundation.lams.security.UniversalLoginModule - ===>rolesQuery =
SELECT DISTINCT r.name,'Roles' FROM
lams_user u LEFT OUTER JOIN lams_user_organisation uo USING(user_id)
LEFT OUTER JOIN lams_user_organisation_role urr USING(user_organisation_id)
LEFT OUTER JOIN lams_role r USING (role_id)
WHERE u.login=?

12:22:25,251 [http-0.0.0.0-8080-3:] DEBUG org.lamsfoundation.lams.security.UniversalLoginModule - ===> authentication type :LAMS
12:22:25,255 [http-0.0.0.0-8080-3:] DEBUG org.lamsfoundation.lams.security.UniversalLoginModule - ===> LAMS:: user:sysadmin:a159b7ae81ba3552af61e9731b20870515944538 authenticated!
12:22:25,256 [http-0.0.0.0-8080-3:] ERROR org.lamsfoundation.lams.web.session.SessionManager - Failed on finding current system session with null sessionId
12:22:25,276 [http-0.0.0.0-8080-3:] DEBUG org.lamsfoundation.lams.security.UniversalLoginModule - ===> exception: java.lang.NullPointerException
java.lang.NullPointerException
at org.lamsfoundation.lams.security.UniversalLoginModule.validatePassword(UniversalLoginModule.java:185)
at org.lamsfoundation.lams.security.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:151)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
at org.jboss.security.plugins.JaasSecurityManager.defaultLogin(JaasSecurityManager.java:483)
at org.jboss.security.plugins.JaasSecurityManager.authenticate(JaasSecurityManager.java:425)
at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:251)
at org.jboss.web.tomcat.security.JBossSecurityMgrRealm.authenticate(JBossSecurityMgrRealm.java:230)
at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:256)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:391)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:619)
--END LAMS.LOG--

Posted by Martyn Yap

By: Jun-Dir Liew

[ Reply | Forward ]

Do you get the same if you restart lams?

Posted by Jun-Dir Liew

By: Martyn Yap

[ Reply | Forward ]

Yup, do get the same error when i restart LAMS and JBOSS.

After restarting, I managed to get to the login page and enter the uname and pwd but it than directs me to this HTTP500 page.

12:22:25,251 [http-0.0.0.0-8080-3:] DEBUG org.lamsfoundation.lams.security.UniversalLoginModule - ===> authentication type :LAMS
12:22:25,255 [http-0.0.0.0-8080-3:] DEBUG org.lamsfoundation.lams.security.UniversalLoginModule - ===> LAMS:: user:sysadmin:a159b7ae81ba3552af61e9731b20870515944538 authenticated!
12:22:25,256 [http-0.0.0.0-8080-3:] ERROR org.lamsfoundation.lams.web.session.SessionManager - Failed on finding current system session with null sessionId
12:22:25,276 [http-0.0.0.0-8080-3:] DEBUG org.lamsfoundation.lams.security.UniversalLoginModule - ===> exception: java.lang.NullPointerException

Seems to be having a null session id and not matching to the current session id, but I'm unsure where to make changes.

Posted by Martyn Yap

By: Jun-Dir Liew

[ Reply | Forward ]

Yeah, not sure what's happening there - do you have the logs for the installer? They should be located under lams-unix-installer-2.0.4/log/.

Posted by Jun-Dir Liew

By: Martyn Yap

[ Reply | Forward ]

Here they are ... = ]

Posted by Martyn Yap

By: Jun-Dir Liew

[ Reply | Forward ]

Forgot attachments...?

Posted by Jun-Dir Liew

By: Martyn Yap

[ Reply | Forward ]

Aplogises .. it seems like its working now ... managed to login successfully, but seem like there another problem accessing the sysadmin function. Thanks for assisting all this while.

Here's the error from the log. = ]
14:34:32,902 INFO [UniversalLoginModule] User 'sysadmin' authenticated, loginOk=true
14:34:32,902 INFO [UniversalLoginModule] commit, loginOk=true
14:34:32,905 INFO [UniversalLoginModule] Assign user to role SYSADMIN
14:34:32,905 INFO [UniversalLoginModule] Found SYSADMIN
14:34:32,905 INFO [UniversalLoginModule] Assign user to role AUTHOR
14:34:33,449 INFO [TilesRequestProcessor] Tiles definition factory found for request processor ''.
14:39:19,482 WARN [RequestUtils] No FormBeanConfig found under 'AuthoringAction'
14:40:06,987 ERROR [SessionManager] Failed on finding current system session with null sessionI
14:40:06,987 ERROR [SessionManager] Failed on finding current system session with null sessionI
14:40:14,004 WARN [UserTag] UserTag unable to access user details as userDTO is missing. SessionImpl@41e72a

Posted by Martyn Yap

By: Jun-Dir Liew

[ Reply | Forward ]

The user object containing some info about the logged-in user is missing... are you logged into a Wildfire admin interface by any chance? That can interfere with LAMS' cookies. Try closing the browser and all it's windows and logging in again, starting a fresh new session. If you still get the 'userDTO is missing' message, something deeper must still be wrong.

Posted by Jun-Dir Liew

By: Martyn Yap

[ Reply | Forward ]

I did not install Wildfire as I have decided not to have a chat function. Did close all the browser windows and clear its cache.

Now it shows me the HTTP404 error, previous it just open a new window with the same information.

Any chance where I should look at?

15:06:01,114 INFO [UniversalLoginModule] User 'sysadmin' authenticated, loginOk =true
15:06:01,114 INFO [UniversalLoginModule] commit, loginOk=true
15:06:01,116 INFO [UniversalLoginModule] Assign user to role SYSADMIN
15:06:01,116 INFO [UniversalLoginModule] Found SYSADMIN
15:06:01,116 INFO [UniversalLoginModule] Assign user to role AUTHOR
15:06:01,314 INFO [TilesRequestProcessor] Tiles definition factory found for re quest processor ''.
15:06:01,594 WARN [UserTag] UserTag unable to access user details as userDTO is missing. Session is org.lamsfoundation.lams.web.session.SessionManager$SessionI mpl@3d4f04

Posted by Martyn Yap

By: Jun-Dir Liew

[ Reply | Forward ]

Just had a closer look at the conf files in 2.0.4, and there's one more thing I think you might not have done - in /path/to/jboss-4.0.2/server/default/conf/lamsauthentication.xml, at the top is another @confdir@ which needs to contain the proper path to lamsauthentication.dtd (should be in the same directory).

Posted by Jun-Dir Liew

By: Martyn Yap

[ Reply | Forward ]

Should the top part look like this?

How many slashes should it have?

Posted by Martyn Yap

By: Jun-Dir Liew

[ Reply | Forward ]

The first two lines should look like this:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Authentication PUBLIC "-//LAMS//DTD LAMS//EN" "http://lamsfoundation.org/dtd/lamsauthentication.dtd">

This version points to the lamsfoundation.org website, which should also work.

Posted by Jun-Dir Liew

By: Martyn Yap

[ Reply | Forward ]

Tried both the ways and the same problem still occurs?

Now it seems that I do not get a HTTP 404 error but the page keeps on refreshing itself.

Thanks! =]

10:31:22,840 WARN [UserTag] UserTag unable to access user details as userDTO is missing. Session is org.lamsfoundation.lams.web.session.SessionManager$SessionImpl@176578

Posted by Martyn Yap

By: Jun-Dir Liew

[ Reply | Forward ]

Can you reinstall the installer from scratch? Originally your install had an error where it didn't copy the files across, and we never got to see the logs as to why that happened. Before installing though, remove the current jboss-4.0.2 directory, unzip a new jboss-4.0.2 instance, drop the current lams database, and then run the installer again - if you run into problems, post the installer logs (located under lams-unix-installer-2.0.4/logs).

Posted by Jun-Dir Liew

By: Martyn Yap

[ Reply | Forward ]

Hihi,

It works after removing the JBOSS directory and dropping the database. Not sure where it went wrong but sincere thanks for the assistance given.

Now ... I'm going to try to integrate LAMS with Blackboard.

Cheers!

Posted by Martyn Yap