unable to install module reporting

21

Are you running the same modules and versions as here? https://demo.openmrs.org/openmrs/admin/modules/module.list

22

Hi Daniel,

Yes, except for reporting - for that one we’re running the snapshot that herbert24 suggested earlier in this thread.

Some modules are not installed yet, but the ones that are installed are the same as the demo system. I was in the process of installing the modules when the system crashed (specifically, it crashed when I installed restreporting). I was installing them via the legacy UI, although some modules had already been installed by Davy, and I didn’t remove those. I’ve pasted the current contents of the modules directory here: adminui-1.4.0.omod htmlformentryui-1.11.2.omod referenceapplication- - Pastebin.com .

Thanks!

23

Remove the module which led to the crush and first get back to the original working state.

24

Hi Daniel,

I have already tried removing the file reportingrest-1.11.0.omod from the modules folder, but unfortunately that did not restore the system to a working state.

EDIT: I tried it again to be sure, and the error message does not change. It seems that trying to install the module caused something in the system to stop working. If I go into /.OpenMRS/.openmrs-lib-cache/ I see that there is a reportingrest directory that I assume was added when I added the module. I could try deleting this, but I don’t know what other changes might be needed to un-do the attempt at installing the module.

  • Ace
25

Which OpenMRS platform version are you running?

26

Version 2.4 (Davy and I are working together: this thread is all about the same system.)

EDIT: The admins gave us permission to restart Tomcat… I had to restart it twice but the system is now alive again.

Thanks; I will now go back to breaking it. :slight_smile:

27

I have encountered this error (core-2.4.0, reporting-1.21.0). I have looked at the liquibase logs and noticed something: reporting_report_design_1 changeSet is executed successfully (including the addForeignKeyConstraint commands)

reporting_report_design_2 and reporting_report_design_3 are not executed (as per the logs) - add column report_definition_uuid to reporting_report_design table

reporting_report_design_4 is executed (as per the logs)

reporting_report_design_5 fails because it acts on a column that wasn’t created in reporting_report_design_2

Could the reason reporting_report_design_2 is not executed is because the dbms is specified as mysql and I am using mariadb?? Is mariadb not mysql?

@ace - are you also using mariadb, just in case this is the reason?

@mseaton @dkayiwa

28

Hi @alaboso - good catch! I think this is likely and inadvertent due to work done at some point by those who were trying to support postgres:

@ibacher and @dkayiwa FYI

29

Yes, our problem also occurred on a system using MariaDB. Good eye! MariaDB is a fork of MySQL, created shortly after Oracle bought MySQL. They have a lot of similarities but they are not exactly the same.

30

Yeah, looks like those changeSet entries need to have dbms="mysql,mariadb", since Liquibase treats MySQL and MariaDB as separate databases.

31

Update related to this topic as of April 2022: There is a team (ICAP-Ethiopia, with support from @alaboso) who is using mardiadb and is unable to deploy the reporting module (1.24.0) because of this mariadb need. Hoping we can discuss a plan for how to handle mariadb in such situations on today’s platform call.