Comments on: How to Install Odoo 17 on Ubuntu 22.04

By: admin

admin — Sun, 12 May 2024 08:03:35 +0000

In reply to djangosu. You can try installing lxml manually with the command: pip3 install lxml and please make sure you are running the commands in a Python virtual environment.

By: djangosu

djangosu — Sat, 11 May 2024 20:47:17 +0000

In step 7, After pip3 install -r odoo17/requirements.txt I get the following error:

src/lxml/etree.c: In function ‘__Pyx_PyInt_As_long’:
src/lxml/etree.c:269960:53: error: ‘PyLongObject’ {aka ‘struct _longobject’} has no member named ‘ob_digit’
269960 | const digit* digits = ((PyLongObject*)x)->ob_digit;
| ^~
src/lxml/etree.c:270015:53: error: ‘PyLongObject’ {aka ‘struct _longobject’} has no member named ‘ob_digit’
270015 | const digit* digits = ((PyLongObject*)x)->ob_digit;
| ^~
src/lxml/etree.c: In function ‘__Pyx_PyIndex_AsSsize_t’:
src/lxml/etree.c:270403:45: error: ‘PyLongObject’ {aka ‘struct _longobject’} has no member named ‘ob_digit’
270403 | const digit* digits = ((PyLongObject*)b)->ob_digit;
| ^~
Compile failed: command ‘/usr/bin/x86_64-linux-gnu-gcc’ failed with exit code 1
creating tmp
cc -I/usr/include/libxml2 -I/usr/include/libxml2 -c /tmp/xmlXPathInit4_94cqzo.c -o tmp/xmlXPathInit4_94cqzo.o
cc tmp/xmlXPathInit4_94cqzo.o -lxml2 -o a.out
error: command ‘/usr/bin/x86_64-linux-gnu-gcc’ failed with exit code 1
[end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for lxml
Running setup.py clean for lxml
Failed to build greenlet lxml
ERROR: Could not build wheels for greenlet, lxml, which is required to install pyproject.toml-based projects

By: admin

admin — Mon, 15 Apr 2024 06:59:10 +0000

In reply to cristian.

If you need to add the odoo17 user to the sudo group, you can do it with the following command:
usermod -aG sudo odoo17

You can check our full tutorial on how to create a sudo user at:
https://www.rosehosting.com/blog/how-to-create-a-sudo-user-on-ubuntu-22-04/

By: cristian

cristian — Sat, 13 Apr 2024 19:21:12 +0000

have you tried following this tutorial? some command require elevated privileges and odoo17 user is not in the sudoers group: useradd -m -U -r -d /opt/odoo17 -s /bin/bash odoo17

By: admin

admin — Sat, 06 Apr 2024 12:02:41 +0000

In reply to Aladdin. Make sure that your Odoo is using the virtual environment in which you installed the requirements.

By: Aladdin

Aladdin — Sat, 06 Apr 2024 09:02:40 +0000

Apr 06 08:43:14 vps-56aca941 odoo17[8318]: File “/opt/odoo17/odoo17/odoo/modules/graph.py”, line >
Apr 06 08:43:14 vps-56aca941 odoo17[8318]: import odoo.tools as tools
Apr 06 08:43:14 vps-56aca941 odoo17[8318]: File “/opt/odoo17/odoo17/odoo/tools/__init__.py”, line>
Apr 06 08:43:14 vps-56aca941 odoo17[8318]: from . import _monkeypatches
Apr 06 08:43:14 vps-56aca941 odoo17[8318]: File “/opt/odoo17/odoo17/odoo/tools/_monkeypatches.py”>
Apr 06 08:43:14 vps-56aca941 odoo17[8318]: from werkzeug.datastructures import FileStorage
Apr 06 08:43:14 vps-56aca941 odoo17[8318]: ModuleNotFoundError: No module named ‘werkzeug’
Apr 06 08:43:14 vps-56aca941 systemd[1]: odoo17.service: Main process exited, code=exited, status=1>
Apr 06 08:43:14 vps-56aca941 systemd[1]: odoo17.service: Failed with result ‘exit-code’.
Apr 06 08:43:14 vps-56aca941 systemd[1]: odoo17.service: Consumed 1.479s CPU time.

keep stopping after somtime

knowing that werkzeug installed correctly from requirements

By: Aville

Aville — Fri, 29 Mar 2024 21:04:12 +0000

Not right like this:

Step 4. Install Wkhtmltopdf
sudo wget https://github.com/wkhtmltopdf/packaging/releases/download/0.12.6-1/wkhtmltox_0.12.6-1.bionic_amd64.deb
sudo dpkg -i wkhtmltox_0.12.6-1.bionic_amd64.deb
sudo apt install -f

Right like this:
cd /tmp
wget https://github.com/wkhtmltopdf/packaging/releases/download/0.12.6.1-3wkhtmltox_0.12.6.1-3.jammy_amd64.deb
sudo gdebi -n wkhtmltox_0.12.6.1-3.jammy_amd64.deb
rm wkhtmltox_0.12.6.1-3.jammy_amd64.deb
sudo ln -s /usr/local/bin/wkhtmltopdf /usr/bin/
sudo ln -s /usr/local/bin/wkhtmltoimage /usr/bin/