コンテンツへスキップ
メニュー
この質問にフラグが付けられました
5 返信
37347 ビュー

Someone can make a concise point out of this error page on my odoo installation?

"nginx 502 :: Bad Gateway"

It happens every now and then irregularely and apparently without further interaction...

Here are the different log-excerpts: (github displays it nicer)

https://gist.github.com/blaggacao/9577fd6b496c9af88735

restarting the odoo service solves the problem until it occurs again.

Update:

It could probably be two problems as error logs are not time exactly related (I don't know much about time dynamics of error logs, but I would supose they should coincide completely or differ only milliseconds, if related)

So the startupscript contains the following lines:

DAEMON=/home/odoo/odoo/openerp-server
NAME=openerp-server
DESC=openerp-server

thus not starting in gevent mode.. (If I'm right...)

On the other hand, ps -efH shows:

https://gist.github.com/blaggacao/e55581a3a2d5503b8273

I configured Workers = 5 (2xcores +1)

You can see, odoo spun up 7+1 where 5 as defined, 1 is for cron jobs AFAIK, 1 I don't know and the last one (the "+1") seems to be something geventish...

My nginx-config btw looks something like this: https://gist.github.com/anonymous/4b3cf30dcc81058ffe1b

Can anyone share his insights/knowledge, please?

I read this one, to no avail: http://www.nginxtips.com/502-bad-gateway-using-nginx/

----------------------------------------------------------------------------------------------------------------------------

UPDATE

I get an intersting new error  in the logfiles, which also has been reported in github.

Something is killing all python instances/threads and leaves odoo down related to an issue with the pickles module.

Reference: https://github.com/odoo/odoo/issues/3878

アバター
破棄
著作者

Please see the UPDATE...

最善の回答

Start odoo with --proxy-mode or set proxy-mode = True in your odoo config file.

アバター
破棄
著作者

It was indeed set to false. I'll accept if this was the solution. Thanks.

著作者

The error still occurs, this might not have been the problem, or there are two problems.

著作者

I updated the initial question with a new log-error...

最善の回答

Hi, you can follow this: https://youtu.be/-3wV7A_4s-w

Hope it helps

アバター
破棄
最善の回答

I've been facing this problem for 2 whole days.

Solution was that my odoo source code was in a directory out of space left.
In that way python code is unexecutable.

アバター
破棄

I'm facing same issue with my odoo 16 community hosted in Digital Ocean, How I can solve this issue? Can I solve by incresing my SSD Droplet Size from 25 GB to 50 GB? Please Help ..

Thats it. Firstly, comment that to your Digital Ocean admin.

最善の回答

Hello,

I have same issue. 

I have added workers=2 in /etc/odoo-server.conf and problem solved!

 

アバター
破棄
最善の回答

On odoo 10 Enterprise, we are regularly facing this problem, UNFORTUNATELY once a week.

odoo's support staff plays the same music everytime "please update to latest version", which we already are on. Alternatively there is a request for a copy of the database. This is naive, because we cannot send production copies of erp-database without violating privacy laws.

The failures are silent as far as we can tell from /var/log/odoo/xyz-prod10-server.log.

Is there any other log to look for useful failure-information?

アバター
破棄