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 <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
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
juju API not listening on all interfaces
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/mailman/listinfo/juju
Re: Charm stuck dying
Hi John, There are other services running on the box that I don't want destroyed. Is there anyway to clean this up without killing the server. Thanks, Wayne On Tue, Aug 16, 2016 at 1:33 AM, John Meinel <j...@arbash-meinel.com> wrote: > I'm quite surprised to see an 'agent-state: stopped' and life: dead with > an 'agent-status: ... executing'. > If the agent really is dead, then there is nothing for the hooks to run > on. Is this particular unit (nrpe/20) running on a machine that has other > services running on it, or was it the last thing on the machine. I believe > 'juju destroy-machine --force' is able to clean up all of the units/etc > that had been placed onto a machine (its used for the case where you > actually stopped the machine via some other means, and there is nothing > left that can run any cleanup steps.) > > John > =:-> > > > On Mon, Aug 15, 2016 at 6:36 PM, Wayne Carty <wca...@gmail.com> wrote: > >> >> Hi >> >> I have a charm that is stuck dying. It seem like the entry didn't get >> updated in juju. >> Is there a way to manually update the status or trigger the hooks >> >> nrpe/20: >> workload-status: >> current: terminated >> since: 12 Aug 2016 10:57:55Z >> agent-status: >> current: executing >> message: running stop hook >> since: 12 Aug 2016 10:57:54Z >> version: 1.25.3 >> agent-state: stopped >> agent-version: 1.25.3 >> life: dead >> >> >> Thanks >> >> -- >> Wayne Carty >> >> -- >> Juju mailing list >> Juju@lists.ubuntu.com >> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm >> an/listinfo/juju >> >> > -- Wayne Carty -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Juju broken install. Charm in a dying state
Hi, I'm looking for some help with a charm stuck in a dying state. nrpe/20: workload-status: current: terminated since: 12 Aug 2016 10:57:55Z agent-status: current: executing message: running stop hook since: 12 Aug 2016 10:57:54Z version: 1.25.3 agent-state: stopped agent-version: 1.25.3 life: dead -- Wayne Carty -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
nagios charm stuck dying
I have a charm stuck dying. Nothing I do seems to solve the issue. How can I delete or remove the stuck charm nagios: charm: cs:trusty/nagios-10 exposed: true life: dying service-status: current: unknown message: Waiting for agent initialization to finish since: 23 May 2016 22:44:07Z relations: monitors: - nrpe -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Charm stuck dying
Hi I have a charm that is stuck dying. It seem like the entry didn't get updated in juju. Is there a way to manually update the status or trigger the hooks nrpe/20: workload-status: current: terminated since: 12 Aug 2016 10:57:55Z agent-status: current: executing message: running stop hook since: 12 Aug 2016 10:57:54Z version: 1.25.3 agent-state: stopped agent-version: 1.25.3 life: dead Thanks -- Wayne Carty -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
