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 running juju
[1.25.6-trusty-amd64 gc]
2016-11-08 10:24:05 DEBUG juju.api api.go:154 trying cached API connection
settings - endpoints [10.38.250.2:17070 10.38.251.49:17070]
2016-11-08 10:24:05 INFO juju.api api.go:266 connecting to API addresses: [
10.38.250.2:17070 10.38.251.49:17070]
2016-11-08 10:24:05 INFO juju.api apiclient.go:262 dialing "wss://
10.38.250.2:17070/environment/80751f52-30bf-4980-8b77-555c16684316/api"
2016-11-08 10:24:05 INFO juju.api apiclient.go:194 connection established
to "wss://
10.173.242.2:17070/environment/80751f52-30bf-4980-8b77-555c16684316/api"
2016-11-08 10:24:05 DEBUG juju.api api.go:476 API hostnames unchanged - not
resolving
2016-11-08 10:24:05 DEBUG juju.api api.go:506 cacheChangedAPIInfo:
serverUUID=""
2016-11-08 10:24:05 ERROR juju.cmd supercommand.go:429 invalid binary
version "1.25.6--amd64"
On Tue, Nov 8, 2016 at 12:15 AM, John Meinel <j...@arbash-meinel.com> wrote:
> 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 series.
>
> John
> =:->
>
> On Mon, Nov 7, 2016 at 3:10 PM, Wayne Carty <wca...@gmail.com> wrote:
>
>> 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 <j...@arbash-meinel.com>
>> wrote:
>>
>>> 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 on all IP
>>> addresses for a machine.
>>>
>>> John
>>> =:->
>>>
>>> On Sat, Nov 5, 2016 at 8:40 PM, Wayne Carty <wca...@gmail.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> 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 juju api is only listening on 10.38.250.251.0/24.
>>>> Nodes that are on 10.38.250.0/24 are now in error state because they
>>>> can't reach the api. The boot strap node has 2 interfaces. I have google
>>>> and have not found a way to fixed the issue.Any help that you guys can
>>>> provide is appreciated.
>>>>
>>>> --
>>>> Wayne Carty
>>>>
>>>> --
>>>> Juju mailing list
>>>> Juju@lists.ubuntu.com
>>>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>>>> an/listinfo/juju
>>>>
>>>>
>>>
>>
>>
>> --
>> Wayne Carty
>>
>
>
--
Wayne Carty
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
