Re: [openstack-dev] [keystone] Keystone failing with error 104 (connection reset by peer) if using uwsgi

2018-03-13 Thread Thomas Goirand
On 03/11/2018 08:12 PM, Lance Bragstad wrote: > 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 Hi Lance, Thanks for your proposal to

Re: [openstack-dev] [keystone] Keystone failing with error 104 (connection reset by peer) if using uwsgi

2018-03-12 Thread Lance Bragstad
On 03/11/2018 06:09 PM, Thomas Goirand wrote: > On 03/11/2018 08:12 PM, Lance Bragstad wrote: >> Hey Thomas,  >> >> Outside of the uwsgi config, are you following a specific guide for your >> install? > Under the packages that I maintain in Debian, there's nothing more to do > than "apt-get

Re: [openstack-dev] [keystone] Keystone failing with error 104 (connection reset by peer) if using uwsgi

2018-03-11 Thread Thomas Goirand
On 03/11/2018 08:12 PM, Lance Bragstad wrote: > Hey Thomas,  > > Outside of the uwsgi config, are you following a specific guide for your > install? Under the packages that I maintain in Debian, there's nothing more to do than "apt-get install keystone", reply to a few Debconf questions, and you

Re: [openstack-dev] [keystone] Keystone failing with error 104 (connection reset by peer) if using uwsgi

2018-03-11 Thread Lance Bragstad
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" wrote: > Hi, > > I've attempted to switch

[openstack-dev] [keystone] Keystone failing with error 104 (connection reset by peer) if using uwsgi

2018-03-11 Thread Thomas Goirand
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