Skip to Content
Menu
This question has been flagged
1 Reply
3633 Views

May 02 18:53:47 uboosvr systemd[1]: Started Odoo.
░░ Subject: A start job for unit odoo.service has finished successfully
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit odoo.service has finished successfully.
░░
░░ The job identifier is 1101901.
May 02 18:53:47 uboosvr systemd[1]: odoo.service: Main process exited, code=exited, status=203/EXEC
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit odoo.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 203.
May 02 18:53:47 uboosvr systemd[1]: odoo.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit odoo.service has entered the 'failed' state with result 'exit-code'.
May 02 18:53:52 uboosvr systemd[1]: odoo.service: Scheduled restart job, restart counter is at 62.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Automatic restarting of the unit odoo.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
May 02 18:53:52 uboosvr systemd[1]: Stopped Odoo.
░░ Subject: A stop job for unit odoo.service has finished
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A stop job for unit odoo.service has finished.
░░
░░ The job identifier is 1102009 and the job result is done.
May 02 18:53:52 uboosvr systemd[1]: Started Odoo.
░░ Subject: A start job for unit odoo.service has finished successfully
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit odoo.service has finished successfully.
░░
░░ The job identifier is 1102009.
May 02 18:53:52 uboosvr systemd[1]: odoo.service: Main process exited, code=exited, status=203/EXEC
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit odoo.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 203.
May 02 18:53:52 uboosvr systemd[1]: odoo.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: t
░░
░░ The unit odoo.service has entered the 'failed' state with result 'exit-code'.

sudo find / -name "odoo-bin" found nothing. Full remove and reinstall several times and odoo-bin still fails when the odoo.service starts. 
Apologies for the prior post, the hyperlink "karma" barrier kept catching. Realized after the test post was successful. 


updated info below:
ian@uboosvr:~$ /opt/odoo/odoo/odoo-bin -c /etc/odoo/odoo.conf
-bash: /opt/odoo/odoo/odoo-bin: No such file or directory

grep -i odoo-bin /var/log/apt/term.log | less showed no entries. 

Avatar
Discard
Best Answer

Hi,

If there is any missing packages the odoo service wont get started, in this case, you can try running the odoo instance via command line using the odoo-bin to identify the issue.

In order to locate where the odoo-bin is locating, you can use the locate package, command --> locate file_name , will give the full path to the corresponding file, so you can use locate odoo-bin .


Once odoo-bin is found, you can run odoo as explained here: How To Run Odoo From Terminal

Thanks

Avatar
Discard
Related Posts Replies Views Activity
2
Oct 21
8907
1
May 24
15079
3
Jan 18
10939
0
Feb 24
1436
5
Nov 23
58924