Solved odoo pkg (odoo v16) requires "latest" pkg repo

[dalescott]

Posting my recent experience in case it may help others....

I recently installed the Odoo 16 pkg (py39-odoo-16 aka finance/odoo). There were no errors reported in the installation process, and the provided rc.d script started the odoo service. However browsing to Odoo from another system returned "500 Internal Server Error":

Internal Server Error
The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.

I contacted the pkg maintainer, who quickly noted from my pkg info listing that I was using a quarterly pkg repo and needed to switch to the "latest" repo, where my issue had already been resolved.

pkg in quarterly repo: py39-odoo-16.0
pkg in latest repo: py39-odoo-16.0.20230804

I followed the procedure in the Handbook to change my pkg repo to "latest", updated the odoo pkg, deleted and re-created the database, and re-started the server (with the initdb command since it was the first time with a new database). Afterwards Odoo was happily served into my browser.

Extra thanks to the pkg maintainer!

Dale

P.S. There is no logging to /var/log/odoo.log as I had expected, but I'm thinking perhaps logging has to be enabled from within Odoo...

 

[zirias@]

I have no idea about the software in question here ...

but this is a general symptom of somewhat poor maintenance of the "quarterly" branches. There is no team responsible for them (for obvious lack of manpower), so it's every single port committer's responsibility to apply "relevant" changes also to the latest "quarterly". And "relevant" can mean two things:

• Fixing a security issue. I'm pretty sure that this is not a problem (at least as long as you're aware you're fixing one), because it's a simple thing: security-relevant, then cherry-pick it to the latest quarterly, no questions asked.
• Fixing a "severe" bug. A bug is severe when it makes it impossible for most users to actually use the software. This is something that's easily forgotten (because you're basically fixing stuff all the time ...)

BTW, there can be yet another issue: With large dependency graphs, fixing such a "severe" bug in quarterly could mean you have to pull in tons of other commits. Then, sometimes, it makes more sense to leave one package "broken", instead of forcing updates to hundreds of packages onto every user of "quarterly". Not saying this happens often, but it's certainly a possible scenario.

So, unfortunately, using "quarterly" packages is kind of a trade-off. You trade a mostly stable (for a quarter) set of software, needing only few updates, for the risk to run into some unfixed bugs ....

 

[gkisuze]

Hi Dale,
On installation of odoo 16, I'm currently encountering errors similar to what you experienced. Both quarterly and latest repos produce internal server error. Odoo service status shows its running.
I get internal server error on the front end and below is what i get in the stdout;

2023-12-29 11:07:04,755 80808 ERROR odoodb odoo.http: Exception during request handling. 
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/odoo/http.py", line 1584, in _serve_db
    return service_model.retrying(self._serve_ir_http, self.env)
  File "/usr/local/lib/python3.9/site-packages/odoo/service/model.py", line 133, in retrying
    result = func()
  File "/usr/local/lib/python3.9/site-packages/odoo/http.py", line 1596, in _serve_ir_http
    ir_http = self.registry['ir.http']
  File "/usr/local/lib/python3.9/site-packages/odoo/modules/registry.py", line 190, in __getitem__
    return self.models[model_name]
KeyError: 'ir.http'

Any ideas on how to fix this?

 

[dalescott]

Hi gkisuze sorry but nothing jumps out as obvious to me but I'm far more user than python dev. After testing the current Odoo community release, I have continued with Tryton (tryton.org) as it is more aligned with my needs.

My only suggestions are to re-read the pkg notes looking for possible misunderstandings or incorrect assumptions, and if that doesn't help, then contact the port maintainer directly for help.

 

[gkisuze]

Hi gkisuze sorry but nothing jumps out as obvious to me but I'm far more user than python dev. After testing the current Odoo community release, I have continued with Tryton (tryton.org) as it is more aligned with my needs. My only suggestions are to re-read the pkg notes looking for possible misunderstandings or incorrect assumptions, and if that doesn't help, then contact the port maintainer directly for help.

Hi dalescott , I kept troubleshooting until i failed to get any productive progress. I had been running odoo 13 smoothly on Freebsd 13 in a bastillebsd jail. For odoo 16, I've had to run back to Linux until odoo 16 on freebsd gets sorted by someone more experienced/knowledgeable. It would be nice if someone could document his experience eg install steps. Quite a number of issues on my side!! wkhtmltopdf gets upgraded to version 0.12.6 and this fails to print out a number of pdf documents.