Skip to Content
Menu
Musisz się zarejestrować, aby móc wchodzić w interakcje z tą społecznością.
To pytanie dostało ostrzeżenie
1 Odpowiedz
3651 Widoki

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. 

Awatar
Odrzuć
Najlepsza odpowiedź

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

Awatar
Odrzuć
Powiązane posty Odpowiedzi Widoki Czynność
2
paź 21
8916
1
maj 24
15103
3
sty 18
10957
0
lut 24
1441
5
lis 23
58939