Reference Application - 2.1.3 Build 33f4e7

Ask OpenMRS
1

Reference Application 2.1.3 Build 33f4e7

Question: We have an OpenMRS install that we’ve been using in our educational program. For the most part it’s a standard install with a few modules; we have one custom-built module running (https://github.com/RSSchermer/openmrs-module-ardenreminders ). The system worked fine for several months; in the last couple months we’ve been getting a run-time error (see https://pastebin.com/as250WJ6 ). Steps to reproduce the problem: On our install:

  1. Log in
  2. Click on Find Patient Record
  3. Click on any patient’s name

Any other means of trying to view a patient file will result in the same error, including creating a new patient. (The demographic data can be entered, but the runtime error occurs after clicking “create”.) Viewing the patient record through the old UI does not generate an error (e.g. System Administration -> Advanced Administration -> Manage Patients -> search for patient and click on name -> click on View Patient Dashboard).

The problem can be temporarily corrected by restarting all modules, but it will occur again after a while (a few hours to a few days).

In the administration view, there are a number of system alerts visible (see below).

We have already tried restarting Tomcat and reinstalling OpenMRS from the WAR file; neither of these seemed to fix the problem.

Thanks in advance for your time!

  • Ace

Errors: There was an error starting the module: Atlas Module There was an error starting the module: UI Library Module There was an error starting the module: Provider Management Module There was an error starting the module: Order Entry UI Module There was an error starting the module: Reference Metadata Module There was an error starting the module: Reference Demo Data Module There was an error starting the module: Admin UI Module There was an error starting the module: Form Entry App Module There was an error starting the module: Allergy UI Module There was an error starting the module: Core Apps Module There was an error starting the module: Registration App Module There was an error starting the module: Reporting UI Module There was an error starting the module: Chart Search Module There was an error starting the module: Appointment Scheduling UI Module There was an error starting the module: Reference Application Module

2

Can you share the real server side log?

3

Thanks for your reply! The log is 80K lines; about half of it is from last year. Do you want the whole thing or just part of it?

4

@ace yes , he basically means you can drop it at https://hastebin.com/ and give the link here.

5

You can keep a backup of the logs. Then delete them. Reproduce the error and send the new logs via pastebin.com

6

Thanks for your help.

Interestingly, OpenMRS found my backup and wrote to it instead of writing to the nice new log file I made for it, but here’s the output from /var/lib/OpenMRS/openmrs.log: https://hastebin.com/dukiqefiso.sql

This should contain two instances of the error (one at 16:23 and one at 16:25).

If you want more of the log file, or if there’s a different log I should be looking at, please let me know.

Thanks again!

7

openmrs.log does not have the full detailed log. Can you look at the tomcat log file?

8

Thanks again for your help, and sorry for the delay in reply.

The contents of catalina.out from the same day as the openmrs.log above are here: https://hastebin.com/jodamorote.sql

The errors occurred at the timestamps 2019-11-04 16:23:23 and 2019-11-04 16:25:39. I included everything that was logged from that day, though.

If you need anything else, please let me know.

9

Are you able to reproduce the error even after removing all your custom modules?

10

We have only one custom module, but I have not yet tried disabling it.

I have a couple VMs I can work with, so I can turn off the module in one VM. The problem often takes a few days to reoccur, so it will be a while before I will have any indication if this makes a difference. I will also try a clean reinstall on a fresh VM and see if the problem occurs on that machine.

Thanks!