Error while installing Bahmni 0.92 - Start Odoo and enable at boot error

Tags: #<Tag:0x00007fa3fa5372a8> #<Tag:0x00007fa3fa5370c8> #<Tag:0x00007fa3fa536fb0> #<Tag:0x00007fa3fa536e98>

Please help. I got this error while installing the latest stable version of Bahmni. I followed the instructions for 0.92 installation. Unfortunately, I can’t proceed because of this error. It says fatal: [localhost]: FAILED! => {“changed”: false, “msg”: “Unable to start service odoo: Job for odoo.service failed because a configured resource limit was exceeded. See “systemctl status odoo.service” and “journalctl -xe” for details.\n”}

I got 8gb of ram, by the way.

Facing Same issue. “unable to start service odoo: Job for odoo.service failed because a configured resource limit was exceeded.” My versions are:- ansible :- 2.4.2.0 systemd:- 219-67.el7_7.1

Also there is “rpm” (rpm -Uvh https://download.postgresql.org/pub/repos/yum/9.6/redhat/rhel-7-x86_64/pgdg-centos96-9.6-3.noarch.rpm) not found for PostgreSQL. PostgreSQL may be removed that rpm from the list of rpm.

You can find my solution in PostgresSQL error here.

@darius can you please help us in this error? we are stuck.

@aldrin19

Please follow Bahmni 0.92 Install on CentOS 7.6 Minimal Fails Steps for odoo boot issue. I solved my error using that steps. Just Downgrade systemd and use yum version lock.

1 Like

Okay. will confirm it if it is okay

I did a fresh install using CentOS 7.7 (1908 minimal) and after update postgres repo, I had the same issue as reported by @aldrin19 on starting odoo service.

After journalctl -xe command I get:

Unit odoo.service has begun starting up. Apr 27 14:37:36 localhost.localdomain odoo[18318]: mkdir: cannot create directory ‘odoo’: File exists Apr 27 14:37:36 localhost.localdomain runuser[18327]: pam_unix(runuser:session): session opened for user odoo by (uid=0) Apr 27 14:37:36 localhost.localdomain runuser[18327]: pam_unix(runuser:session): session closed for user odoo Apr 27 14:37:36 localhost.localdomain odoo[18318]: Starting Odoo Server Daemon (odoo-server): [ OK ] Apr 27 14:37:36 localhost.localdomain systemd[1]: Can’t open PID file /var/run/odoo/odoo-server.pid (yet?) after start: No such file or directory Apr 27 14:37:36 localhost.localdomain odoo[18318]: Traceback (most recent call last): Apr 27 14:37:36 localhost.localdomain odoo[18318]: File “/usr/bin/odoo”, line 4, in Apr 27 14:37:36 localhost.localdomain odoo[18318]: import(‘pkg_resources’).run_script(‘odoo==10.0.post20190619’, ‘odoo’) Apr 27 14:37:36 localhost.localdomain odoo[18318]: File “/usr/lib/python2.7/site-packages/pkg_resources/init.py”, line 3098, in Apr 27 14:37:36 localhost.localdomain odoo[18318]: @_call_aside Apr 27 14:37:36 localhost.localdomain odoo[18318]: File “/usr/lib/python2.7/site-packages/pkg_resources/init.py”, line 3082, in _call_aside Apr 27 14:37:36 localhost.localdomain odoo[18318]: f(*args, **kwargs) Apr 27 14:37:36 localhost.localdomain odoo[18318]: File “/usr/lib/python2.7/site-packages/pkg_resources/init.py”, line 3111, in _initialize_master_working_set Apr 27 14:37:36 localhost.localdomain odoo[18318]: working_set = WorkingSet._build_master() Apr 27 14:37:36 localhost.localdomain odoo[18318]: File “/usr/lib/python2.7/site-packages/pkg_resources/init.py”, line 575, in _build_master Apr 27 14:37:36 localhost.localdomain odoo[18318]: return cls._build_from_requirements(requires) Apr 27 14:37:36 localhost.localdomain odoo[18318]: File “/usr/lib/python2.7/site-packages/pkg_resources/init.py”, line 588, in _build_from_requirements Apr 27 14:37:36 localhost.localdomain odoo[18318]: dists = ws.resolve(reqs, Environment()) Apr 27 14:37:36 localhost.localdomain odoo[18318]: File “/usr/lib/python2.7/site-packages/pkg_resources/init.py”, line 782, in resolve Apr 27 14:37:36 localhost.localdomain odoo[18318]: raise VersionConflict(dist, req).with_context(dependent_req) Apr 27 14:37:36 localhost.localdomain odoo[18318]: pkg_resources.ContextualVersionConflict: (soupsieve 2.0 (/usr/lib/python2.7/site-packages/soupsieve-2.0-py2.7.egg), Requirement.parse(’ Apr 27 14:37:36 localhost.localdomain systemd[1]: odoo.service never wrote its PID file. Failing. Apr 27 14:37:36 localhost.localdomain systemd[1]: Failed to start LSB: Launches the Odoo server… – Subject: Unit odoo.service has failed – Defined-By: systemd – Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel – – Unit odoo.service has failed. – – The result is failed. Apr 27 14:37:36 localhost.localdomain systemd[1]: Unit odoo.service entered failed state. Apr 27 14:37:36 localhost.localdomain systemd[1]: odoo.service failed. Apr 27 14:37:36 localhost.localdomain polkitd[1075]: Unregistered Authentication Agent for unix-process:18312:6977134 (system bus name :1.365, object path /org/freedesktop/PolicyKit1/Aut lines 1486-1526/1526 (END)

I have tried another fresh installation with the steps reported by @bhiravabhatla on this post Bahmni 0.92 Install on CentOS 7.6 Minimal Fails and the installation could end without any error, but still I was not able to start odoo service with “service odoo restart” or “systemctl odoo restart”. All other services work well.

When the last release was announced by @angshuonline in this post Announcing release of Bahmni 0.92 I gave it a try with a fresh install and all worked well (including odoo) in the first attempt. This release fix the systemd issues reported in previous release which had this Bahmni 0.92 Install on CentOS 7.6 Minimal Fails as work around. Something happen meanwhile.

It would be nice to hear if someone has a resolution for this problem.

I had the same error but according to this particular error message, i have downgraded this library and installed below version.

pip install soupsieve==1.9.5

and i reinstalled only bahmni-erp

bahmni -i local --only bahmni-erp install

2 Likes

Thank you so much @mupagasi, that was indeed the issue! All modules work fine now.

1 Like

@mupagasi hi. I have the same issue of Odoo services not starting. I have seen the fix you have provided and I hear it has worked. I’m new to Linux, therefore unable to perform the downgrade of the library you suggested and install the new one. Kindly guide me here on how I’m going to do it. Regards

You can avoid the problem just fire the following two commands . Hope the problem will be solved.

  1. pip uninstall beautifulsoup4

  2. pip install beautifulsoup4

Then fire the bahmni install command .

2 Likes

Thank you very much @rakib for your fix, it has worked very well. I have really struggled. How are we going to make team update the process so that it is clear and straight forward? Thank you again!

1 Like

This worked for me too on ( CentOS Linux release 7.8.2003 Core ). I had previously encountered problems downgrading the “systemd.”