-
I am unable to login to Libreclinica 1.3 even though I can get to the login screen. system is ubuntu 20.04, tomcat 9, postgres 14. Every time I try and login I get the error page (Oops ...). Below is the error I see in the logs. 21-Oct-2024 14:39:00.316 SEVERE [http-nio-8080-exec-1] org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() for servlet [default] in context with path [/LibreClinica] threw exception [java.lang.NullPointerException] with root cause Any ideas? Thanks. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 6 replies
-
This is error from data access layer which looks like the initialisation of the data access objects was not successful. Can you check if the initial table structure was created in the database and that there is the |
Beta Was this translation helpful? Give feedback.
-
the log shows that database connection string was not initialized properly (failing with null pointer). Looks like it is failing while setting the database connection url but that is supposed to be created automatically when postgres is detected as dbType in datainfo properties file. I would suspect other the properties file not copied out of WEB-INF/classes into libreclinica.config location or tomcat cannot read the properties file (permissions not set correctly). |
Beta Was this translation helpful? Give feedback.
-
now I noticed on your screenshot from 1.3 opps! page that the changeset corresponds to the current state of lc-develop branch which is unreleased development state (supposed to be released as 1.4 eventually). This means that you was compiling it on your own from the sources. Could you try to use the actually released 1.3 war from the release page and let me know if you are still getting the same error in the log? |
Beta Was this translation helpful? Give feedback.
-
This is really strange, not sure if I will manage to reproduce it. There is lots of errors in logs that would indicate not just database layer is not initialized but also other things from spring application context failed to start. Almost like if it would have in classpath some incompatible or conflicting libraries but this is hard to imagine because also between 1.2.1 and 1.3 there have not been that many changes. You can try to describe in more detail your deployment environment, maybe somebody else will have an idea (I exhausted my initial list of typical troublemakers). |
Beta Was this translation helpful? Give feedback.
Hello, just to let you know that I recently reinstalled lc 1.3.0 on my system and it worked. Both the released one and the latest lc_develop one worked. The only change from earlier was to update the OS when I had to install a new package (swaks) on the system so seems more like an environment issue. Thanks.