I want to share a problem I recently have with bahmni
i think it would be difficult to replicate the problem, since it was different evertime but i’ll try to explain the best i can.
I’m using Bahmni ver 0.93 via VirtualMachine in CentOS
everything started when i was writing consultation notes, and follow ups, then i notice everytime I save the system hangs and deploys “Open MRS is not currently not available”
i do the vagrant halt and the vagrant up and the problem persists
but if i reboot the server completely it works again
sometimes when i restart in the login page i have no options from the drop down menu so i have to restart again, the thing with restarting is that is the entire server, i does not work if i just restart the virtual machine
i do have other services running like oviyam, but the only one affected is Bahmni…
this last reboot send the next message
Sorry if is too long, i do not know what to do, and even don’t know how to backup my patient database
i havent touch files in at least 4months the only file i changed was dashboard.json and deleted some sections everything else is stock provided, i attach my current dashboard.json if its needed
currentdashboard.txt (18.2 KB)
I don’t know if this helps but I’m running Bahmni Vagrant on:
thanks in advance…
Bahmni Error.txt (444.6 KB)
instead of rebooting vagrant, try investigating the service logs.
journalctl -u openmrs
Also when you reboot the vagrant, check the memory using commands like free or top.
Its quite possible that you are running out resources.
If you have installed all components, try stopping some of the services and see
Hello, thanks for your answer
I change all the files i change for the original ones but as i said before rebooting only the VM doesn’t work
i have to reboot the entire server, i did what you requested and this is what i got
-- Logs begin at mar 2022-11-01 12:54:49 CST, end at mar 2022-11-01 12:56:52 CST. --
nov 01 18:54:55 localhost.localdomain systemd: [/usr/lib/systemd/system/openmrs.service:11] Unknown lvalue 'LogsDirecnov 01 18:54:57 localhost.localdomain systemd: Starting OpenMRS Server...
nov 01 18:54:57 localhost.localdomain openmrs: Starting openmrs
nov 01 18:54:57 localhost.localdomain systemd: Started OpenMRS Server.
nov 01 12:56:05 localhost.localdomain systemd: openmrs.service: main process exited, code=killed, status=6/ABRT
nov 01 12:56:05 localhost.localdomain systemd: Unit openmrs.service entered failed state.
nov 01 12:56:05 localhost.localdomain systemd: openmrs.service failed.
and the problems is getting worst now everytime i do the login the system sends the following error
i’ll try to do
bahmni -i local install
but i do not know if that deletes all my patient data
If you are evaluating Bahmni for local use, then maybe you can try the docker-compose version instead of the VM version. Will need lesser resources, runs on newer version of OpenMRS, more stable and better. This is the current “development version” of Bahmni, which will get launched in a month or so as Bahmni Lite v1.0.
After making lots of changes, debugging and stuff
it’s my obligation to tell you that the problem, was the server
i don’t know why, but i did a thoughtfulll inspection and the result was that the computer that was running th service somehow got a corrupted apt
for someone interested in this the specs of the server are:
Nvidia 1660Ti with 8gb ram
32GB Ram doble channel
linux Distro : mxlinux
i have to format the entire computer and everything is working fine
i dont know how “apt” may disturb vagrant or virtualbox, that’s beyond my level of knowledge
many thanks to all who posted