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: systemd-devel Info Page – – 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 - #10 by bhiravabhatla 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 - #10 by bhiravabhatla as work around. Something happen meanwhile.
It would be nice to hear if someone has a resolution for this problem.