samuel34
(Samuel Male)
September 2, 2018, 2:38pm
1
Hi,
I’m trying to work on TRUNK-5342 . This requires me to setup a distro depending on platform 2.2. (distro.properties file)
However, I have a batch of a few modules failing to start.
Lets start with Reference Metadata - 2.8.0. => error log
However, on restarting the server, I got the error below on accessing http://localhost:8080/openmrs/login.htm
https://pastebin.com/YCvVG4e1
cc: @dkayiwa , @wyclif
samuel34
(Samuel Male)
September 2, 2018, 7:18pm
2
Any idea of how to successfully setup a server that depends on platform 2.2
cc : @dkayiwa
dkayiwa
(Daniel Kayiwa)
September 2, 2018, 7:58pm
3
samuel34
(Samuel Male)
September 3, 2018, 1:30pm
4
I successfully setup a server that depends on platform 2.2 using the sdk.
openmrs-distro.properties
#Tue Aug 07 02:47:25 MDT 2018
db.h2.supported=false
db.sql=classpath\://openmrs-distro.sql
name=Reference Application
omod.addresshierarchy=2.11.0
omod.adminui=1.2.3
omod.allergyui=1.8.1
omod.appframework=2.11.0
omod.appointmentscheduling=1.9.0
omod.appointmentschedulingui=1.7.0
omod.appui=1.8.0
omod.atlas=2.2
omod.atlas.type=omod
omod.calculation=1.2
omod.chartsearch=2.1.0
omod.coreapps=1.20.0-SNAPSHOT
omod.dataexchange=1.3.2
omod.emrapi=1.25.0-SNAPSHOT
omod.event=2.6.0
omod.event.groupId=org.openmrs
omod.fhir=1.13.0
omod.formentryapp=1.4.2
omod.htmlformentry=3.7.0
omod.htmlformentryui=1.7.0
omod.htmlwidgets=1.9.0
omod.idgen=4.5.0
omod.legacyui=1.4.0
omod.metadatadeploy=1.10.0
omod.metadatamapping=1.3.4
omod.metadatasharing=1.5.0
omod.owa=1.9.0
omod.providermanagement=2.10.0
omod.referenceapplication=2.8.0
omod.referencedemodata=1.4.5-SNAPSHOT
omod.referencemetadata=2.9.0-SNAPSHOT
omod.registrationapp=1.12.0
omod.registrationcore=1.8.0
omod.reporting=1.16.0
omod.reportingcompatibility=2.0.5
omod.reportingrest=1.10.0
omod.reportingui=1.6.0
omod.serialization.xstream=0.2.14
omod.serialization.xstream.type=omod
omod.uicommons=2.6.0
omod.uiframework=3.13.0
omod.uilibrary=2.0.6
omod.webservices.rest=2.22.0
owa.openmrs-owa-sysadmin=1.1
version=2.9.0-SNAPSHOT
war.openmrs=2.2.0-SNAPSHOT
But the server failed to start with this error log
Please, could you help here! @dkayiwa , @mozzy
dkayiwa
(Daniel Kayiwa)
September 3, 2018, 3:08pm
5
Looks like you may not have compiled the referencemetadata module well. Can you attach the compiled omod that you are using?
dkayiwa
(Daniel Kayiwa)
September 3, 2018, 5:59pm
7
I have made a commit to the module. Can you pull, compile, install and test again?
1 Like
samuel34
(Samuel Male)
September 3, 2018, 6:38pm
8
dkayiwa
(Daniel Kayiwa)
September 3, 2018, 6:51pm
9
Are you sure this is not the old log? Can you attach your new compiled omod?
dkayiwa
(Daniel Kayiwa)
September 3, 2018, 7:27pm
11
Can you delete the logs and then run again?
samuel34
(Samuel Male)
September 3, 2018, 7:29pm
12
Sorry to ask such a newbie question, which logs should I delete
samuel34
(Samuel Male)
September 3, 2018, 8:03pm
14
I tried a different approach
Built core
Put .war file in /webapps dir of tomcat
Put the modules in appdata dir
On installing the latest Snapshot version of referencemetadata, I got this error @dkayiwa
dkayiwa
(Daniel Kayiwa)
September 3, 2018, 9:51pm
15
Strange. What happens when you run openmrs from command line using? mvn jetty:run
samuel34
(Samuel Male)
September 3, 2018, 10:24pm
16
The issue persists with https://pastebin.com/A50UfVZr
But whats that missing file?
dkayiwa
(Daniel Kayiwa)
September 4, 2018, 12:20pm
18
samuel34
(Samuel Male)
September 4, 2018, 12:21pm
19
Gonna show you in 40 mins, I’m still in a lecture
samuel34
(Samuel Male)
September 4, 2018, 4:57pm
20
I have used the modules in the addson package for 2.8. However I still get this error when I install the latest SNAPSHOT version of referencemetadata module.
NB: The EMRAPI-1.24.4 module liquibase change set fails at startup untill I explicitly dropped the ‘openmrs.conditions’ table.
cc: @dkayiwa