Re: juju API not listening on all interfaces

Hi John, I went through the upgrade guide and ran into some issues. I'm not sure what I should do to resolved this. The error listed below root@maas01:~# apt-get install juju-core root@maas01:~# juju upgrade-juju --version 1.25.6 --debug 2016-11-08 10:24:05 INFO juju.cmd supercommand.go:37 runn

Re: juju API not listening on all interfaces

A couple of points 1) I dug up the code and 1.22.8 has the same code for listening on ":17070", so I can't see why it wouldn't be listening on both addresses. 2) Is there any reason you're still on 1.22.* ? Its been out of support for a while, and we do strongly encourage you to upgrade to the 1.25

Re: juju API not listening on all interfaces

Hi John, I'm using version 1.22.8. I did check the order of the interfaces and they all start before juju runs. Even after restarting the API service with the interfaces up it's still doesn't listen on 10.38.250.0/24. Thanks, Wayne On Mon, Nov 7, 2016 at 6:34 AM, John Meinel wrote: > What ve

Re: juju API not listening on all interfaces

What version of Juju are you running? Is it possible the devices didn't come up before Juju was up and running? Right now we are doing: endpoint := net.JoinHostPort("", strconv.Itoa(info.APIPort)) listener, err := net.Listen("tcp", endpoint) Which means we listen to ":17070". That should listen

Re: juju API not listening on all interfaces

On 05/11/16 18:40, Wayne Carty wrote: > I had our bootstrap node crash a few days ago and now the juju api is > not listening on all interfaces. > Out boot strap nodes server two networks. > > 10.38.250.0/24 and 10.38.251.0/24 > . > > As of right now