You are viewing an old version of this page. View the current version.
Before installation of bahmni-installer rpm
Remove epel-release rpm before installing bahmni-installer rpm
Instructions to bahmni installation using bahmni-installer rpm is available in Install Bahmni on CentOS (Advanced Installation Options). Proceed till step 5 as mentioned in the link. After Step 5, following things have to be done manually to migrate from old sh based installation to bahmni-installer rpm based installation:
After installation of bahmni-installer rpm
Stop all services
switch off chkconfig for tomcat, openerp.
Move bahmni related webapps from tomcat's webapps directory to some other directory.
Take backup of all individual DBs **IMPORTANT**
Take backup of service logs if necessary.
Backup certain properties files
Take Backup of Nagios
Uninstall mysql if it is 5.6.12 since mysqld service is not present.
To see the list of mysql components installed, run the following command:
Uninstall the listed components. But be aware of the dependencies which might get removed by removing mysql components as well.
check whether pg_basebackup command is available. If it is not available, use alternatives to make /usr/pgsql-9.2/bin/pg_basebackup available to /usr/bin
Now the installation can be continued from Step 7 as mentioned in the link - Trigger Installation
Some common errors during deployment and steps to resolve them
When any yum operation fails with the error - 'Error: Cannot retrieve metalink for repository: epel. Please verify its path and try again', execute the following:
rpm -e jdk or yum remove jdk(If JAVA conflict occurs.)
On starting the installation, if it fails saying that ansible could not be installed or ansible-playbook command is not found, epel-release rpm has to be reinstalled.
If we get 'AnsibleLoader' object has no attribute 'dispose' on any command in Bahmni, 'PyYAML' has to be upgraded to 3.10.
Link to ansible issue: https://github.com/ansible/ansible/issues/15660
First remove python-yaml rpm
Then try to install again. Verify that 3.10 is being installed.
Check whether mysql and psql replication works.
Move patient_images, uploaded-files, uploaded_results, document_images from old tomcat user home folder to /home/bahmni folder. In the below snippet, We have assumed that 'jss' user had tomcat deployed in it. This step is not applicable if 'bahmni' was the old tomcat user.
Update global_poperties in openmrs to have /home/bahmni as directory instead of /home/jss
There can be some more as well
Update site information – parentOfUploadedFilesDirectory – check for the value once before doing it in clinlims database.
With the new way of installation, we had made 'bahmni' user as just run user. And we add a new user called 'bahmni_support' for ssh purposes.
a) Inorder to make bahmni as non-ssh user, following command needs to be executed. This command will lock the 'bahmni' user account for login.
b) Inorder to make bahmni as non-sudoer, do the following – Be very careful with this step
1. type 'visudo' in shell
2. Remove the line bahmni ALL=(ALL) NOPASSWD:ALL
3. save it
On this page
- No labels