Re: regression: restore-backup broken by recent commit

2017-02-24 Thread John Meinel
Is it possible for us to close more gracefully most of the time? John =:-> On Feb 24, 2017 08:27, "Tim Penhey" wrote: > OK, I think I got it now... > > This is all crazy, and it was a change due to the gorilla/websocket > change. > > So... what happens when there is a successful restore on the

Re: regression: restore-backup broken by recent commit

2017-02-23 Thread Tim Penhey
OK, I think I got it now... This is all crazy, and it was a change due to the gorilla/websocket change. So... what happens when there is a successful restore on the server side is that it calls os.Exit(...) which then has the pid 1 restart the agent. However from the API client, this is an ab

Re: regression: restore-backup broken by recent commit

2017-02-23 Thread Tim Penhey
On 24/02/17 16:17, Tim Penhey wrote: Also, a CI run of a develop revision just before the gorilla/websocket reversion hit this: http://reports.vapour.ws/releases/4922/job/functional-ha-backup-restore/attempt/5045#highlight cannot create collection "txns": unauthorized mongo access: not

Re: regression: restore-backup broken by recent commit

2017-02-23 Thread Tim Penhey
Hi Curtis (also expanding to juju-dev), I have been looking into this issue. And the good news is that it doesn't appear to be a real problem with gorilla/websocket at all, but instead a change in timing showed an existing issue that hadn't surfaced before. I'll be looking into that issue -