Problem resolved... but not understood.
It was probably operating system based.
I shut down the ethernet interfaces
sudo ip link set enp1s0 down
sudo ip link set eno1 down
launched the brooklyn web console successfully, then put the interfaces
back up and launched brooklyn again without issue.
Prior to this I had rebooted a number of times and removed the docker0
bridge interface without success.
Thanks.
Jade
On 13 April 2015 at 04:37, jade mackay <[email protected]> wrote:
> Hi Alex,
>
> Thanks for your reply. I tried specifying bindAddress as the ip address of
> another interface without success. See ip addr, brooklyn launch outputs
> below.
> $ ip addr
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
> default
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> valid_lft forever preferred_lft forever
> inet6 ::1/128 scope host
> valid_lft forever preferred_lft forever
> 2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
> UP group default qlen 1000
> link/ether 2c:41:38:4f:16:ff brd ff:ff:ff:ff:ff:ff
> inet 10.100.21.87/26 brd 10.100.21.127 scope global eno1
> valid_lft forever preferred_lft forever
> inet6 fe80::2e41:38ff:fe4f:16ff/64 scope link
> valid_lft forever preferred_lft forever
> inet6 fe80::f26:6a58:82ee:1b6c/64 scope link
> valid_lft forever preferred_lft forever
> 3: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
> state DOWN group default qlen 1000
> link/ether 2c:41:38:4f:16:fe brd ff:ff:ff:ff:ff:ff
> inet6 fe80::5367:eebb:34ac:44c3/64 scope link tentative
> valid_lft forever preferred_lft forever
> 4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
> state DOWN group default
> link/ether 56:84:7a:fe:97:99 brd ff:ff:ff:ff:ff:ff
> inet 172.17.42.1/16 scope global docker0
> valid_lft forever preferred_lft forever
> inet6 fe80::bd01:3011:3b12:b866/64 scope link tentative
> valid_lft forever preferred_lft forever
> 5: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc
> pfifo_fast state UNKNOWN group default qlen 100
> link/none
> inet 10.8.0.18 peer 10.8.0.17/32 scope global tun0
> valid_lft forever preferred_lft forever
>
> $ ./usage/dist/target/brooklyn-dist/bin/brooklyn launch --bindAddress
> 10.100.21.87
> ...
> 2015-04-13 04:34:07,103 ERROR Startup error: Failed to start Brooklyn
> web-console: Unable to provision port for web console (wanted 8081-65535)
>
>
> /jade
>
> On 13 April 2015 at 04:23, Alex Heneveld <[email protected]>
> wrote:
>
>>
>> Hi Jade,
>>
>> I think I've figured this out. Try specifying a non-loopback
>> `--bindAddress`.
>>
>> See http://stackoverflow.com/questions/29597279/apache-
>> brooklyn-unable-to-provision-port-for-web-console/29597786#29597786 for
>> more details.
>>
>> Also could share the list of network interfaces that your OS has?
>>
>> Best
>> Alex
>>
>>
>>
>> On 12/04/2015 23:11, jade mackay wrote:
>>
>>> I have recently performed an update on my computer which seems to have
>>> broken apache brooklyn for me:
>>>
>>> brooklyn launch
>>> ...
>>> WARN Failed to start Brooklyn web-console (rethrowing): Unable to
>>> provision port for web console (wanted 8081-65535)
>>>
>>>
>>> I am using the pre-compiled binaries: 0.7.0-M2-incubating I have stopped
>>> and disabled ufw and iptables.
>>>
>>> Any ideas appreciated!
>>>
>>> Thanks,
>>> Jade
>>>
>>>
>>
>
>
> --
> Jade Mackay
> e: [email protected]
> m: +64-(0)22-319-0847
>
>
--
Jade Mackay
e: [email protected]
m: +64-(0)22-319-0847
