I am having a great deal of difficulty getting Odoo to run, and integrating ERP. Perhaps I don’t understand the process well enough, but I have tried multiple Bahmni installations from scratch and it just is not working. Access to localhost:8069 shows Internal Server Error (or other errors on various attempts) “The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.” Also ERP does not give any response. “We can’t connect to the server at erp-localhost”. I have tried successfully to compile the ERP module, but I have not been successful in containerizing it. Suggestions?
I now have Odoo working but some problems persist:
- http://erp-localhost : site not found. From the main Bahmni page this is the error I receive when trying to open “Stock Inventory & Billing” In checking the start-up, I see that erp has failed. See log below
- No access to Analytics from the main page, Atom Feed Console & Lab Entry when logged into Clinical Services
When opening localhost:8069 I do not get the console I see described in the documentation. I have set a main database password, but I get a login for e-mail and password. The page comes up with the Bahmni logo, but no tool bar. The only items are “Quotations” “Sales Orders” & “Invoices and Billing”. There is nothing that refers to any of the Bahmni modules, and it appears not to be linked in any way to the lab, medical records, clinic/hospital billing, or other aspects of Bahmini.
Please help!
Charles W. Powell, MD
odoo-connect-1 | 2025-09-06 06:52:06,284 DEBUG [openerp-atomfeed-service][org.springframework.beans.factory.support.DefaultListableBeanFactory] Creating shared instance of singleton bean ‘customerFeedfailedJobTrigger’ odoo-connect-1 | org.springframework.scheduling.quartz.JobMethodInvocationFailedException: Invocation of method ‘execute’ on target class [class org.bahmni.feed.openerp.job.OpenERPEventsPublisherJob] failed odoo-connect-1 | Caused by: org.springframework.scheduling.quartz.JobMethodInvocationFailedException: Invocation of method ‘execute’ on target class [class org.bahmni.feed.openerp.job.OpenERPEventsPublisherJob] failed odoo-connect-1 | 2025-09-06 06:53:30,004 INFO [openerp-atomfeed-service][org.bahmni.feed.openerp.job.SimpleFeedJob] Processing failed events for Feed [customer.feed.generator.uri] odoo-connect-1 | 2025-09-06 06:53:30,026 INFO [openerp-atomfeed-service][org.bahmni.feed.openerp.job.SimpleFeedJob] Processing failed events for Feed [drug.feed.generator.uri] odoo-connect-1 | 2025-09-06 06:53:30,026 INFO [openerp-atomfeed-service][org.bahmni.feed.openerp.job.SimpleFeedJob] Processing failed events for Feed [lab.feed.generator.uri] odoo-connect-1 | 2025-09-06 06:53:30,027 INFO [openerp-atomfeed-service][org.bahmni.feed.openerp.job.SimpleFeedJob] Processing failed events for Feed [lab.feed.generator.uri] odoo-connect-1 | 2025-09-06 06:53:30,028 INFO [openerp-atomfeed-service][org.bahmni.feed.openerp.job.SimpleFeedJob] Processing failed events for Feed [lab.feed.generator.uri] odoo-connect-1 | 2025-09-06 06:53:50,498 INFO [openerp-atomfeed-service][org.bahmni.feed.openerp.job.SimpleFeedJob] Processing failed events for Feed [saleorder.feed.generator.uri] odoo-connect-1 | 2025-09-06 06:53:50,514 INFO [openerp-atomfeed-service][org.bahmni.feed.openerp.job.SimpleFeedJob] Processing failed events for Feed [saleable.feed.generator.uri] odoo-connect-1 | 2025-09-06 06:54:00,001 INFO [openerp-atomfeed-service][org.bahmni.feed.openerp.job.SimpleFeedJob] Processing failed events for Feed [drug.feed.generator.uri] odoo-connect-1 | 2025-09-06 06:54:00,003 INFO [openerp-atomfeed-service][org.bahmni.feed.openerp.job.SimpleFeedJob] Processing failed events for Feed [lab.feed.generator.uri] odoo-connect-1 | 2025-09-06 06:54:00,027 INFO [openerp-atomfeed-service][org.bahmni.feed.openerp.job.SimpleFeedJob] Processing failed events for Feed [customer.feed.generator.uri] odoo-connect-1 | 2025-09-06 06:54:10,530 INFO [openerp-atomfeed-service][org.bahmni.feed.openerp.job.SimpleFeedJob] Processing failed events for Feed [lab.feed.generator.uri] odoo-connect-1 | 2025-09-06 06:54:10,548 INFO [openerp-atomfeed-service][org.bahmni.feed.openerp.job.SimpleFeedJob] Processing failed events for Feed [lab.feed.generator.uri] odoo-connect-1 | 2025-09-06 06:54:20,030 INFO [openerp-atomfeed-service][org.bahmni.feed.openerp.job.SimpleFeedJob] Processing failed events for Feed [saleable.feed.generator.uri]
I am down to two items that are not working properly. In “Clinical” dashboard, the “AtomFeed Console” returns an error as does “Lab Entry”. I suspect they are related but I am not quite sure where to go with solving the problem.
Second, when I open localhost:8069, I can now log into odoo, but all that is displayed is an e-mail client. The Bahmni modules are shown under Apps but I do not see how to make use of them. Clicking on ‘Stock and Billing’ from the main page returns and error, but I now understand why. It is the lack of an FQDN. The way around this is to point to the server and use port 8069. Nonetheless, how does one get the Bahmni apps to run under odoo?
Once I get these working, I can start on customization with our facility name and logo.
Charles W. Powell, MD Chihoni Medical Center Chihoni, Nala Ward Tanzania
hey , how are you able to start the atomfeed module .i’m really stuck at that part the ui says that i can’t update through ui and when i added the line “module.allow_web_admin=true “ and restarted it still shows the same how do i start the atomfeed module because everything depends on it and i.m stuck here once this gets done i’ll be able to see the orders in openmrs and dcm4chee.pls help me out.
@rahu1ramesh @mohant please help
I have not been successful in starting the atomfeed module. This is one of the issues I have had. I have encountered the same issues as you.
Charles
@cwpowell The logs attached are from odoo-connect, which is a downstream service that acts as a bridge between the EMR and Odoo. For troubleshooting, you’ll need to review the logs from the Odoo container itself, as those are the ones that will provide the necessary diagnostic details.
Atomfeed console and lab lite are under specific profiles. You need to explicity add it to COMPOSE_PROFILES variable in the .env file.
If you are using Bahmni Standard Lab Lite service would not start automatically. If you need lab-lite, the service definition must be copied over from bahmni-lite and added into bahmni-standard docker compose file
Had this on Bahmni (Docker) with Odoo 16. It wasn’t a module issue, it was filestore permissions. (PermissionError: [Errno 13] Permission denied: ‘/var/lib/odoo/filestore/odoo/checklist/fd/fdffc45cba0e31dd34423b54f06fd48e9824192c’). The filestore volume mounted at /var/lib/odoo/filestore/odoo/... was owned by root, yet Odoo container runs as user odoo.
Fix was to change ownership/perms of the filestore to odoo:odoo, then restart:
docker compose exec -u 0 odoo bash -lc ’ chown -R odoo:odoo /var/lib/odoo/filestore && find /var/lib/odoo/filestore -type d -exec chmod 775 {} ; && find /var/lib/odoo/filestore -type f -exec chmod 664 {} ;’ docker compose restart odoo
1 Like