Metadata sharing nolonger on the mdsbuilder

Basing on the release management guidelines for CIEL Dictionary when i try to follow like below;

2.Update Metadata Sharing packages to the latest versions of CIEL concepts Login to mdsbuilder OpenMRS instance. Go to Administration -> Metadata Sharing -> Export Metadata and choose a package (repeat b. and c. for the following packages: Reference Application Concepts, Reference Application Diagnoses, Reference Application Order Entry and Allergies Concepts) Click New Version. Follow the creating package wizard leaving all defaults. Click Download Latest to get the zip file for that package.

This is what i see;

so where do i find the Reference application concepts and other concepts like mentioned in the guidelines above?

@taremwatadeo i wanted to install it from the web but it crashed. So i tried to restart tomcat which i failed because i do not have root privileges. May be @burke can help.

I have restarted the mdsbuilder server. Let me know if I should reinstall the mds package.


1 Like

Thanks @ball :slight_smile: It has a startup error which would require looking at the logs.

@dkayiwa - You have permissions now.

catalina.out shows only this error:

ERROR - Listener.contextInitialized(188) |2016-10-24 00:21:27,232| Got exception while starting up: org.openmrs.module.ModuleException: Unable to start OpenMRS. Error thrown was: org.openmrs.api.APIException: Service not found: interface org.openmrs.scheduler.SchedulerService at org.openmrs.web.WebDaemon.startOpenmrs( at org.openmrs.web.Listener.contextInitialized( at org.apache.catalina.core.StandardContext.listenerStart( at org.apache.catalina.core.StandardContext.startInternal( at org.apache.catalina.util.LifecycleBase.start( at org.apache.catalina.core.ContainerBase.addChildInternal( at org.apache.catalina.core.ContainerBase.addChild( at org.apache.catalina.core.StandardHost.addChild( at org.apache.catalina.startup.HostConfig.deployWAR( at org.apache.catalina.startup.HostConfig$ at java.util.concurrent.Executors$ at java.util.concurrent.FutureTask$Sync.innerRun( at at java.util.concurrent.ThreadPoolExecutor.runWorker( at java.util.concurrent.ThreadPoolExecutor$ at Caused by: javax.servlet.ServletException: org.openmrs.api.APIException: Service not found: interface org.openmrs.scheduler.SchedulerService at org.openmrs.web.Listener.startOpenmrs( at org.openmrs.web.WebDaemon$ Caused by: org.openmrs.api.APIException: Service not found: interface org.openmrs.scheduler.SchedulerService at org.openmrs.api.context.ServiceContext.getService( at org.openmrs.api.context.ServiceContext.getSchedulerService( at org.openmrs.api.context.Context.getSchedulerService( at org.openmrs.module.web.WebModuleUtil.stopTasks( at org.openmrs.module.web.WebModuleUtil.stopModule( at org.openmrs.module.web.WebModuleUtil.shutdownModules( at org.openmrs.web.Listener.performWebStartOfModules( at org.openmrs.web.Listener.performWebStartOfModules( at org.openmrs.web.Listener.startOpenmrs( … 1 more

@ball This is what is happenning when i try to access the mdsbuilder

Thanks again @ball for giving me the required permissions! :slight_smile:

@taremwatadeo the server is now up and running.

Does anyone know where the reference application MDS packages, that used to be on this server, are?

I usually try to keep this server running and with the latest CIEL dictionary. At some point (many months ago), new OpenMRS software appears to be automatically deployed on this server which doesn’t always work with the mds and metadata sharing packages. I have fiddled around the in the past. Not sure who should be maintaining and keeping his running.

I do use this server to create mds packages from CIEL for the PIH “golden” concept server and github code source for our implementations.

I used to have a user account on that server, but it’s gone now. The earliest date_created for any account there (besides admin and daemon) is @ball on 2016-06-21 09:56:22 (and then @ssmusoke and @jmpango two days later).

Did this database get nuked in June? Ellen, do you remember anything about that?

(I can’t find anything relevant on talk, or in my skype or email history.)

1 Like

@dkayiwa Does this mean we should continue with the release process since it all looks like @ball keeps the server updated

@taremwatadeo we would need to update the metadatasharing module with MDS packages downloaded from the updated mdsbuilder server. So @ball’s keeping the server updated, cater for only step 1 of the reference application release process. We need to take care of step 2 and the rest. Does this make things clearer? :slight_smile:

yes its clearer @dkayiwa but then this leaves me stuck , since i cannot see any of the concepts (packages) to be updated

@taremwatadeo yes you are correct, we need to look into this.

Am trying to avoid having to recreate these packages. @raff, @ball, or any one else, do you have tips? :slight_smile:

Thanks for fixing, @dkayiwa. You are wonderful.

I tested with creating/exporting one mds package with one concept. I supposed the rules for OpenMRS 2.0 or MDS does not allow for concepts without a description in the preferred locale? There are many CIEL (and PIH) concepts which will hit this problem.

Sounds like there are some other glitches with this process. What are the other problems?

@ball would temporarily setting the value of the global property named “validation.disable” help you with the problem of concepts without descriptions?

As for other glitches, am not aware of any, for now. :slight_smile:

Do you know of any trick which will save us from having to recreate, from scratch, the metadata sharing packages that used to be on this server?

Do we know when the packages disappeared? Where are the mds packages stored on an OpenMRS server? At a certain point, the .OpenMRS directory moved from the usual place (~tomcat7/.OpenMRS) to /var/lib/OpenMRS. I haven’t followed the timing of this with the OpenMRS version or settings.

I took a sqldump backup of the database on October 10 (before sourcing the new CIEL dictionary). Would that help?

Someone wiped this OpenMRS installation at some point before June 21. I don’t have any insight into why or who. (Maybe it was tied to this, or tied to getting to Platform 2.0?) In any case this is bad, because this was supposed to be our server of record for metadata that we include in the reference application. :frowning:

Poking around, the only relevant database dump I see is in Rafal’s home directory openmrs_db_20160412.sql which we might consider restoring. (Ellen has a dump from October, but I’m guessing these packages were deleted before that.)

@raff, what do you think is the best way to reconstruct the MDS packages we had on this machine? It seems like we are using 7 packages, as defined here, and I think they’re probably small, since we’re not including concepts.

One option (tedious, but doable) is (1) import all MDS packages that are in the referencemetadata module, to get the metadata onto this server; (2) look at the header.xml in each of the zip files, and manually create new packages having the relevant items, (3) manually edit the records created in the metadatasharing_exported_packages table so they have the right UUIDs and versions.

Another idea is to stop using metadata sharing for all these things, and instead use the metadatadeploy module. I wouldn’t have prioritized making this change, but if we already have to do tedious work to recover, this would be a better use of time.

(@raff, @dkayiwa, @wyclif, @ball, someone experienced like you is going to have to lead this, it’s not something we can expect @taremwatadeo to do in his first time as release manager! Who can commit to doing this?)

Aside: I have changed the admin user’s password to something none of us will remember, to force people to use their own accounts to do things on this server. We want the metadata that people created on this server to be traceable…

My account on that server is also gone

@wyclif I just created an account for you.

I can’t log in either so please someone with privileges create an OpenMRS account for me on mdsbuilder.

I think I took the “openmrs_db_20160412.sql” backup before doing upgrades to openmrs-core 1.11.5 and mds 1.2 (I will double check that), which both went fine and we were able to do the RA 2.4 release… Maybe something with the Platform 2.0 upgrade went wrong? I can’t recall working on that though so I have no insights.

Did we add any metadata for RA 2.5, which wasn’t in RA 2.4? I think no, but I want to confirm with you. Using that backup and upgrading to the latest CIEL will be enough in such a case.

In particular @ball did you add any metadata to mdsbuilder other than upgrading CIEL after April 12th 2016, which you would like to backup? Could you please send me your backup from October so I can diff it with mine from April?