more_set_headers "Content-Security-Policy: default-src 'none'; script-src 'self' 'unsafe-inline'; object-src 'none'; style-src 'self' 'unsafe-inline'; img-src 'self' blob:; media-src 'self'; frame-src 'none'; font-src 'self'; connect-src 'self'; frame-ancestors 'none'; base-uri 'none'; form-action 'self'; manifest-src 'none'; worker-src 'none'; upgrade-insecure-requests" always;
location / {
try_files $uri @tryton;
}
location @tryton {
uwsgi_pass tryton;
include uwsgi_params;
uwsgi_request_buffering off;
}
location = /favicon.ico {
alias /var/www/tryton-sao/images/tryton-icon.png;
}
location = /robots.txt {
return 200 "User-agent: *\nDisallow: /\n";
}
}
```
---
### Author:  [@SamBull](https://discuss.tryton.org/u/SamBull)
#### Post date: [April 10, 2019, 3:37pm UTC](https://discuss.tryton.org/t/connection-closed-every-couple-of-minutes/1309/11 "2019-04-10T15:37:18Z")
I tried logging in and out 3 times, but it also doesn’t seem to make a difference to me. If I open and close a few different tabs in the admin, I will encounter that error within a minute or 2.
It also sounds a bit weird that Nginx could be responsible for causing a connection between Tryton and the DB to get closed. Surely, that would be outside the control of Nginx.
---
### Author:  [@SamBull](https://discuss.tryton.org/u/SamBull)
#### Post date: [April 10, 2019, 4:08pm UTC](https://discuss.tryton.org/t/connection-closed-every-couple-of-minutes/1309/12 "2019-04-10T16:08:11Z")
Just to mention I’ve tried switching the DB connection to a localhost TCP connection, but get the same results either way.
---
### Author:  [@edbo](https://discuss.tryton.org/u/edbo)
#### Post date: [April 10, 2019, 5:45pm UTC](https://discuss.tryton.org/t/connection-closed-every-couple-of-minutes/1309/13 "2019-04-10T17:45:00Z")
Are you using the webclient? We are using the GTK desktop client. I’ve asked my client to pull the nginx.conf from the server. That one works for them.
And from my memory there was a specific location with the databasename.
> ```
> location /production_database/ {
> uwsgi stuff
> }
>
> ```
Can you can try something like that?
---
### Author:  [@ced](https://discuss.tryton.org/u/ced)
#### Post date: [April 10, 2019, 6:08pm UTC](https://discuss.tryton.org/t/connection-closed-every-couple-of-minutes/1309/14 "2019-04-10T18:08:40Z")
Another possibility is that the connection pool is started before the fork of µwsgi. In this case the connections could be shared between multiple process and closed by one while the other still use it.
You could try to µwsgi option `lazy-apps=true` which prevent µwsgi to load the application before forking.
---
### Author:  [@SamBull](https://discuss.tryton.org/u/SamBull)
#### Post date: [April 15, 2019, 3:39pm UTC](https://discuss.tryton.org/t/connection-closed-every-couple-of-minutes/1309/15 "2019-04-15T15:39:34Z")
lazy-apps seems to have solved the issue, and I can even activate new modules in the admin now. Thanks.
---
### Author:  [@ced](https://discuss.tryton.org/u/ced)
#### Post date: [April 15, 2019, 3:43pm UTC](https://discuss.tryton.org/t/connection-closed-every-couple-of-minutes/1309/16 "2019-04-15T15:43:23Z")
How do you launch the µwsgi process? It will be good to understand why the connection pool is created before the fork (and see if we can fix that).
---
### Author:  [@SamBull](https://discuss.tryton.org/u/SamBull)
#### Post date: [April 15, 2019, 4:11pm UTC](https://discuss.tryton.org/t/connection-closed-every-couple-of-minutes/1309/17 "2019-04-15T16:11:35Z")
I run `service tryton-wsgi start`. Obviously, I had to configure all that myself as this is not something provided by the Debian package.
`/etc/systemd/system/tryton-wsgi.service`:
```
[Unit]
Description=Start uwsgi for Tryton ERP
After=network.target
[Service]
Type=simple
User=tryton
Group=www-data
PermissionsStartOnly=true
ExecStart=/usr/bin/uwsgi --post-buffering 65536 --ini /etc/tryton/uwsgi.ini
[Install]
WantedBy=multi-user.target
```
`/etc/tryton/uwsgi.ini`:
```
[uwsgi]
uid = tryton
gid = tryton
socket = /run/trytond/trytond.sock
chmod-socket = 660
plugins = python3
module = trytond.application:app
env = TRYTOND_CONFIG=/etc/tryton/trytond.conf
env = TRYTOND_LOGGING_CONFIG=/etc/tryton/trytond_log.conf
env = TRYTOND_DATABASE_NAMES=tryton
logto = /var/log/uwsgi/tryton.log
log-5xx = true
disable-logging = true
lazy-apps=true
master
workers = 1
max-requests = 200
harakiri = 30
die-on-term
```
---
### Author:  [@ced](https://discuss.tryton.org/u/ced)
#### Post date: [April 15, 2019, 6:14pm UTC](https://discuss.tryton.org/t/connection-closed-every-couple-of-minutes/1309/18 "2019-04-15T18:14:01Z")
> [@SamBull](#):
>
> env = TRYTOND\_DATABASE\_NAMES=tryton
This is the line that force the creation of the connection pool.
I created [Do not copy connection pool after fork (#8281) · Issues · Tryton / Tryton · GitLab](https://bugs.tryton.org/issue8281) to be able to use the advantage of loading the database before the fork.
---
### Author:  [@system](https://discuss.tryton.org/u/system)
#### Post date: [May 15, 2019, 6:14pm UTC](https://discuss.tryton.org/t/connection-closed-every-couple-of-minutes/1309/19 "2019-05-15T18:14:07Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.