Skip to Content
Menu
This question has been flagged
1 Reply
4352 Views

We are facing a weird behavior with Odoo 12.0 Enterprise Edition.


When we enable multithread in odoo config file, large attachments won't complete to download, it is interrupted at 11 megabytes aprox, we have nginx as reverse proxy.


I'm sure it's matter of configuration, has some one faced this odoo's behavior?


this is our odoo.conf

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

[options]
addons_path = /opt/odoo/enterprise,/opt/odoo/12.0/addons
data_dir = /mnt/ssd/datadir
proxy_mode = True
PATH=/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
geoip_database = /usr/share/GeoIP/GeoLiteCity.dat
workers = 39
limit_time_cpu = 172800
limit_time_real = 345600
limit_memory_hard = 7068709120
limit_memory_soft = 6094967296
limit_request = 8192
max_cron_threads = 2
logrotate = True
logfile = /var/log/odoo/odoo-server.log
log_db = False
log_db_level = warning
log_handler = :INFO
db_host = False
db_maxconn = 600
db_name = False
db_password = False
db_port = False
db_template = template1
db_user = False
dbfilter = .*
longpolling_port = 8072
xmlrpc = True
xmlrpc_interface = 127.0.0.1
xmlrpc_port = 8069

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

And this is our nginx site config

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

#odoo server
upstream odoo {
 server 127.0.0.1:8069 weight=1 fail_timeout=0;
}
upstream odoochat {
 server 127.0.0.1:8072 weight=1 fail_timeout=0;
}

# http -> https
server {
   listen 80;
   server_name mrp.geportal.com;
   rewrite ^(.*) https://$host$1 permanent;
}

server {
 listen 443;
 server_name mrp.geportal.com;

 client_max_body_size 200m;

 proxy_buffers 32 1024k;
 proxy_buffer_size 2048k;

 proxy_connect_timeout 172800s;
 proxy_send_timeout 172800s;
 proxy_read_timeout 172800s;
 proxy_next_upstream error timeout invalid_header http_500 http_502 http_503;

 proxy_set_header X-Forwarded-Host $host;
 proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
 proxy_set_header X-Forwarded-Proto $scheme;
 proxy_set_header X-Real-IP $remote_addr;

 # SSL parameters
 ssl on;
 ssl_certificate /etc/letsencrypt/live/mrp.geportal.com/fullchain.pem;
 ssl_certificate_key /etc/letsencrypt/live/mrp.geportal.com/privkey.pem;
 ssl_session_timeout 30m;
 ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
 ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA';
 ssl_prefer_server_ciphers on;

 # log
 access_log /var/log/nginx/odoo.access.log;
 error_log /var/log/nginx/odoo.error.log;

proxy_redirect off;
proxy_buffering off;

 # Redirect longpoll requests to odoo longpolling port
 location /longpolling {
   proxy_pass http://odoochat;
 }

 # Redirect requests to odoo backend server
 location / {
   proxy_pass http://odoo;
 }

 # cache some static data in memory for 60mins.
 # under heavy load this should relieve stress on the OpenERP web interface a bit.
 location /web/static/ {
   proxy_cache_valid 200 60m;
   proxy_buffering on;
   expires 864000;
   proxy_pass http://odoo;
 }

 # common gzip
 gzip_types text/css text/scss text/plain text/xml application/xml application/json application/javascript;
 gzip on;
}

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

When we open the nginx log we can see an error like this:

2020/09/01 16:17:47 [error] 1350#1350: *1544 upstream prematurely closed connection while sending to client, client: 177.333.177.222, server: mrp.geportal.com, request: "GET /web/content/1131335?download=true HTTP/1.1", upstream: "http://127.0.0.1:8069/web/content/1131335?download=true", host: "mrp.geportal.com", referrer: "https://mrp.geportal.com/web?debug=assets"


We have the same problem even with 3 or 4 workers.


Thank you in advance for your help.



Avatar
Discard

Hello, I also encountered this problem, have you found a solution?

Best Answer

I had the same issue as you. After playing around with various parameters, I found that removing `proxy_buffering off;` from the Nginx config solves the issue.

Avatar
Discard
Author

Thank you Andre! it works fine for me.

Related Posts Replies Views Activity
2
Feb 19
8766
1
May 24
3549
2
Sep 24
433
1
May 24
2097
2
May 24
12883