Roles and privileges to run reports

Software Bahmni
22

Do you mean you have halted your vagrant and started again?

How did you do this?

Ideally yes. But it’ okay to restart.[quote=“swathivarkala, post:10, topic:11337”] Please use the below command to find the version of Bahmni installed.

yum list installed | grep bahmni [/quote]

Can you do this once again tell me how the versions look like now?

Can you run the above command and get the output.[quote=“mafrica, post:21, topic:11337”] I am afraid I am way out of my depth in analyzing this, but is it possible that the Vagrant Box does not like the port that bahmni-reports is trying to use? [/quote]

Can you check which process is running on 8051 port? You can use the below commands.

1 Like
23

Do you mean you have halted your vagrant and started again?

As it happened Vagrant was halted and so I started with Vagrant up that said: c:\Bahmni\bahmni-vagrant>vagrant up Bringing machine ‘default’ up with ‘virtualbox’ provider… ==> default: Checking if box ‘bahmni-team/bahmni’ is up to date… ==> default: A newer version of the box ‘bahmni-team/bahmni’ is available! You currently ==> default: have version ‘0.88’. The latest is version ‘0.89’. Run ==> default: vagrant box update to update.

How did you do this?

I just followed the instruction “Vagrant box update”

Please use the below command to find the version of Bahmni installed.

yum list installed | grep bahmni

vagrant@localhost ~]$ yum list installed | grep bahmni atomfeed-console.noarch 1.0-18 @bahmni bahmni-emr.noarch 0.88-241 @bahmni bahmni-erp.noarch 0.88-32 @bahmni bahmni-erp-connect.noarch 0.88-32 @bahmni bahmni-installer.noarch 0.88-101 @bintray–bahmni-rpm bahmni-lab.noarch 0.88-32 @bahmni bahmni-lab-connect.noarch 0.88-241 @bahmni bahmni-openmrs.noarch 0.88-60 @bahmni bahmni-reports.noarch 0.88-10 @bahmni bahmni-web.noarch 0.88-241 @bahmni epel-release.noarch 6-8 @bintray–bahmni-rpm python-gdata.noarch 2.0.11-1.el6 @bahmn

Strange I see lots of 0.88 where the update process said:

c:\Bahmni\bahmni-vagrant>vagrant box update ==> default: Checking for updates to ‘bahmni-team/bahmni’ default: Latest installed version: 0.88 default: Version constraints: default: Provider: virtualbox ==> default: Updating ‘bahmni-team/bahmni’ with provider ‘virtualbox’ from version ==> default: ‘0.88’ to ‘0.89’… ==> default: Loading metadata for box ‘https://atlas.hashicorp.com/bahmni-team/bahmni’ ==> default: Adding box ‘bahmni-team/bahmni’ (v0.89) for provider: virtualbox default: Downloading: https://atlas.hashicorp.com/bahmni-team/boxes/bahmni/versions/0.89/providers/virtualbox.box default: Progress: 100% (Rate: 525k/s, Estimated time remaining: --:–:--) ==> default: Successfully added box ‘bahmni-team/bahmni’ (v0.89) for ‘virtualbox’!

Can you do this once again tell me how the versions look like now?

ps -ef |grep report

bahmni 1534 1 0 Jun05 ? 00:03:46 /usr/java/jre1.8.0_101/bin/java -jar -Xms512m -Xmx1024m /opt/bahmni-reports/lib/bahmni-reports.jar vagrant 5567 10379 0 05:32 pts/1 00:00:00 grep report

$netstat -tunlp |grep 8051 pick the process Id from the output of the above which will look like " xxxx/java" and get the process using the below command. $ps -ef | grep xxxx

[vagrant@localhost ~]$ sudo netstat -tunlp |grep 8051 tcp 0 0 :::8051 :::* LISTEN 1534/java

[vagrant@localhost ~]$ ps -ef | grep 1534 bahmni 1534 1 0 Jun05 ? 00:03:46 /usr/java/jre1.8.0_101/bin/java -jar -Xms512m -Xmx1024m /opt/bahmni-reports/lib/bahmni-reports.jar vagrant 6091 10379 0 05:36 pts/1 00:00:00 grep 1534

24

You said your vagrant box updated but still everything seems to be on 0.88. Can you try re installation following https://bahmni.atlassian.net/wiki/display/BAH/Install+Bahmni

25

I must admit to being a bit confused as the vagrant up now declares everything up to date.

Anyway I am presently following these update instructions and will report what happens:#

https://bahmni.atlassian.net/wiki/display/BAH/Upgrade+to+Latest+Bahmni+Release

26

So having followed that approach rather than the instructions given at Vagrant up time it seems I am now at 0.89, but the basic problem still persists

[vagrant@localhost ~]$ yum list installed | grep bahmni atomfeed-console.noarch 1.0-18 @bahmni bahmni-emr.noarch 0.89-316 @bahmni bahmni-erp.noarch 0.89-43 @bahmni bahmni-erp-connect.noarch 0.89-43 @bahmni bahmni-implementer-interface.noarch 0.89-93 @bahmni bahmni-installer.noarch 0.89-167 @/bahmni-installer-0.89-167.noarch bahmni-lab.noarch 0.89-64 @bahmni bahmni-lab-connect.noarch 0.89-316 @bahmni bahmni-openmrs.noarch 0.89-83 @bahmni bahmni-reports.noarch 0.89-59 @bahmni bahmni-web.noarch 0.89-316 @bahmni epel-release.noarch 6-8 @bintray–bahmni-rpm python-gdata.noarch 2.0.11-1.el6 @bahmni [vagrant@localhost ~]$

[vagrant@localhost ~]$ sudo netstat -tunlp |grep 8051 tcp 0 0 :::8051 :::* LISTEN 1556/java [vagrant@localhost ~]$ ps -ef | grep 1556 bahmni 1556 1 7 08:19 ? 00:00:58 /usr/java/jre1.8.0_101/bin/java -jar -Xms512m -Xmx1024m /opt/bahmni-reports/lib/bahmni-reports.jar vagrant 4895 3517 0 08:33 pts/0 00:00:00 grep 1556 [vagrant@localhost ~]$

Here is the latest bahmni-reports.log reportslog89.txt (8.6 KB)

27

Still you are not able to run reports? Which Database Dump are you using?

28

Still the same error as at message 1 in this thread.

I use mysqldump - do you want a copy of the db? It presently only has test data so no confidentiality issues.

29

Where did you get the dump from?

30

The original db came with the vagrant distro and then I requested through this forum a procedure to remove all the test data and was instructed as below:

binduakHimabindu AkkinepalliApr 41 mafrica Hi @mafrica, You can download the openmrs clean db dump from here2. Please run the below commands to restore the database once you download.

gzip -d openmrs_backup.sql.gz mysql -uroot -ppassword -e “drop database openmrs” mysql -uroot -ppassword -e “create database openmrs” mysql -uroot -ppassword openmrs < openmrs_backup.sql

This is clean database and it doesn’t any concepts, locations , address heirarchy and many more so that you can start from scratch. As @gsluthra mentioned I will share the OpenELIS and OpenERP clean databases in couple of days. Meanwhile you can start configuring openmrs database.

31

hi @mafrica, @binduak is looking into replicating the issue with the steps followed by you and will get back with the findings.

32

For completeness later in the thread Flush test data from Bahmni/opeMRS @binduak advised "You can directly download the file using wget in guest machine ( Bahmni server ) and run the above mentioned restore commands.

wget https://github.com/Bahmni/bahmni-scripts/raw/master/FreshDb/v0.86/openmrs_backup.sql.gz" this was done and the data deletion apparently worked fine.

33

Can you share your inventory file? You can find it in /etc/bahmni-installer/ folder.

34

Is this what you need…thanks again for being so actively involved

local.txt (1.1 KB)

35

I would really be grateful for any ideas on how to narrow the source of this problem. I am sure the source must be trivial although beyond my ability to identify and fix. However, the consequences of being unable to produce a single report puts our entire implementation at risk.

36

Hi @mafrica, Bahmni 0.89 version is available… would you mind upgrading and trying? Why are you using vagrant??

37

I will try 0.89. On Vagrant, we are a very low IT resource environment and require Windows Server for some apps and so I had hoped to use Bahmni inside vagrant as a sort of appliance. Response time seems fine for the volumes that we have so far.

38

This has already been a very long thread, but looking back I see that upgrade to 0.89 was suggested and done previously with no improvement.

The error that I have is surely within a quite localised piece of code. Is it not possible to trap the source by an appropriate patch?

39

Hi,

@mafrica @swathivarkala did the problem of communication link failure get resolved? I am facing what it seems like similar issue and could not figure out the solution. posted the issue here