Hey Thomas, Outside of the uwsgi config, are you following a specific guide for your install? I'd like to try and recreate the issue.
Do you happen to have any more logging information? Thanks On Mar 11, 2018 06:10, "Thomas Goirand" <z...@debian.org> wrote: > Hi, > > I've attempted to switch Keystone to using uwsgi instead of Apache in > the Debian packages for Queens. Unfortunately, I had random failure with > error 104 in both output of the client and keystone logs. 104 is in fact > "TCP connection reset by peer" (and this shows in the logs). So I've > switched back, but I'd prefer using uwsgi if possible. > > Here's the parameters I had in the .ini for uwsgi: > > http-socket = :35357 > wsgi-file = /usr/bin/keystone-wsgi-admin > buffer-size = 65535 > master = true > enable-threads = true > processes = 12 > thunder-lock = true > plugins = python3 > lazy-apps = true > paste-logger = true > logto = /var/log/keystone/keystone-admin.log > name = keystone-admin > uid = keystone > gid = keystone > chdir = /var/lib/keystone > die-on-term = true > > Has this happened to anyone else? Is there one option above which is > wrong? Why is this happening? > > Cheers, > > Thomas Goirand (zigo) > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
