maas-devel team mailing list archive
-
maas-devel team
-
Mailing list archive
-
Message #01849
Re: 1.6.0 beta 5 out
On 18 July 2014 16:25, Andreas Hasenack <andreas@xxxxxxxxxxxxx> wrote:
>
>
>
> On Fri, Jul 18, 2014 at 12:22 PM, Andreas Hasenack <andreas@xxxxxxxxxxxxx>
> wrote:
>>
>> Can you paste your ifconfig output please? I think I know what's
>> happening.
>>
>>
>> These are the "real" interfaces:
>> br0 Link encap:Ethernet HWaddr 00:23:55:2c:53:78
>> inet addr:10.1.0.1 Bcast:10.1.255.255 Mask:255.255.0.0
>> inet6 addr: fe80::223:55ff:fe2c:5378/64 Scope:Link
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:88357707 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:172662349 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:0
>> RX bytes:6541281459 (6.5 GB) TX bytes:306129483057 (306.1 GB)
>>
>> eth0 Link encap:Ethernet HWaddr 78:2b:cb:8e:56:6b
>> inet addr:10.0.7.8 Bcast:10.0.7.255 Mask:255.255.255.0
>> inet6 addr: fe80::7a2b:cbff:fe8e:566b/64 Scope:Link
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:83209393 errors:0 dropped:1869 overruns:0 frame:0
>> TX packets:44154022 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:1000
>> RX bytes:120405683094 (120.4 GB) TX bytes:4738076825 (4.7 GB)
>> Interrupt:19
>>
>> eth1 Link encap:Ethernet HWaddr 00:23:55:2c:53:78
>> inet6 addr: fe80::223:55ff:fe2c:5378/64 Scope:Link
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:82937896 errors:3139 dropped:0 overruns:0 frame:3139
>> TX packets:188420263 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:1000
>> RX bytes:6529695865 (6.5 GB) TX bytes:276815240088 (276.8 GB)
>>
>> Other than that I have lxcbr0, virbr0 and some veth. Unrelated I suspect,
>> but I can include them if you want.
>
>
> eth1 and br0 have the same inet6 addr, since they "share" the mac
>
> # brctl show br0
> bridge name bridge id STP enabled interfaces
> br0 8000.0023552c5378 no eth1
Yeah, that's what I was going to say.
http://paste.ubuntu.com/7814891/ will help you, if you want to apply it.
To stop the "Unable to get RPC connection" errors from appearing, shut
the region web app down and truncate the eventloops table in
PostgreSQL. Alternatively, truncate it and wait 60 seconds. Stale
entries get pruned after 5 minutes so these errors should not persist
in a longer-running system; it's a bug if they do. Stale entries in
that table should only appear when Apache crashes (or the machine
does); that they're appearing routinely might indicate that Apache is
not shutting down its Python interpreters "nicely".
Follow ups
References