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
348 Widoki

I succesfuly created the sh script, that backups my prod database and restore them on my local dev sever, but I am hitting a problem:

Style error

The style compilation failed. This is an administrator or developer error that must be fixed for the entire database before continuing working. See browser console or server logs for details.


UncaughtPromiseError > OwlError

Uncaught Promise > An error occured in the owl lifecycle (see this Error's "cause" property)

OwlError: An error occured in the owl lifecycle (see this Error's "cause" property)
    Error: An error occured in the owl lifecycle (see this Error's "cause" property)
        at handleError (http://172.21.21.219/web/assets/9c4fa1b/web.assets_web.min.js:916:101)
        at App.handleError (http://172.21.21.219/web/assets/9c4fa1b/web.assets_web.min.js:1548:29)
        at ComponentNode.initiateRender (http://172.21.21.219/web/assets/9c4fa1b/web.assets_web.min.js:1006:19)

Caused by: TypeError: Cannot read properties of undefined (reading 'type')
    at http://172.21.21.219/web/assets/9c4fa1b/web.assets_web.min.js:8965:126
    at visit (http://172.21.21.219/web/assets/9c4fa1b/web.assets_web.min.js:4246:51)
    at visitChildren (http://172.21.21.219/web/assets/9c4fa1b/web.assets_web.min.js:4245:171)
    at visit (http://172.21.21.219/web/assets/9c4fa1b/web.assets_web.min.js:4246:129)
    at visitXML (http://172.21.21.219/web/assets/9c4fa1b/web.assets_web.min.js:4246:202)
    at KanbanArchParser.parse (http://172.21.21.219/web/assets/9c4fa1b/web.assets_web.min.js:8962:2326)
    at Object.props (http://172.21.21.219/web/assets/9c4fa1b/web.assets_web.min.js:9236:1128)
    at View.loadView (http://172.21.21.219/web/assets/9c4fa1b/web.assets_web.min.js:9877:179)
    at async Promise.all (index 0)
    at async ComponentNode.initiateRender (http://172.21.21.219/web/assets/9c4fa1b/web.assets_web.min.js:1005:36)

 I am using the same server OS and the same env settings etc. f.ex. systemd service file. 

Finally I found that if I stop the service and run as odoo user following commands

./odoo-bin -u all --stop-after-init

./odoo-bin -c /etc/odoo.conf --dev=all

Then it works without error.

Could any body help with a tip what is missing in my odoo.service file (or what other commands should be used to start the odoo service on my dev server):

[Unit]
Description=Odoo ERP System
Documentation=http://www.odoo.com
Requires=postgresql.service
After=network.target postgresql.service

[Service]
Type=simple
SyslogIdentifier=odoo
PermissionsStartOnly=true
User=odoo
Group=odoo
Environment="HOME=/opt/odoo"

# Optional but recommended: pre-start asset cleanup/rebuild
ExecStartPre=/opt/odoo/odoo-venv/bin/python3.11 /opt/odoo/odoo/odoo-bin \
    --config=/etc/odoo.conf \
    -u all \
    --stop-after-init

ExecStart=/opt/odoo/odoo-venv/bin/python3.11 /opt/odoo/odoo/odoo-bin \
    --config=/etc/odoo.conf \
    --addons-path=/opt/odoo/odoo/addons/ \
    --logfile=/var/log/odoo/odoo-server.log

StandardOutput=journal+console
KillMode=mixed
Restart=on-failure
RestartSec=10s

# Optional hardening
PrivateTmp=true
ProtectSystem=full
ProtectHome=true
NoNewPrivileges=true

[Install]
WantedBy=multi-user.target

Awatar
Odrzuć
Autor Najlepsza odpowiedź

Finally solved by the help from outside this forum:

These errors could also simply mean that there are couple of folder contents missing i.e. in my case - custom-addons and enterprise-addons.

As I did not full install of our odoo server, but just starting step, then I didn't noted those as rather begginer with odoo.

There are also the "Update Apps List" procedure/menu should be done under Apps in dev mode. 

Awatar
Odrzuć