Aliased network interfaces cause a crash
JohnRMorris opened this issue · 4 comments
psdash can't handle aliased network interfaces:
Here's an extract from my ifconfig output:
eth1 Link encap:Ethernet HWaddr e0:69:95:88:a5:6c
inet addr:192.168.42.110 Bcast:192.168.42.255 Mask:255.255.255.0
inet6 addr: fe80::e269:95ff:fe88:a56c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:45606 errors:0 dropped:0 overruns:0 frame:0
TX packets:31806 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:54025486 (54.0 MB) TX bytes:3494120 (3.4 MB)
Interrupt:20 Memory:fe500000-fe520000
eth1:1 Link encap:Ethernet HWaddr e0:69:95:88:a5:6c
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:20 Memory:fe500000-fe520000
The "eth1:1" interface results in a traceback that terminates with:
File "/usr/local/lib/python2.7/dist-packages/psdash-0.1.1-py2.7.egg/psdash/templates/network.html", line 35, in block "content"
<td>{{ io.rx_per_sec|filesizeformat }}</td>
File "/usr/local/lib/python2.7/dist-packages/jinja2/filters.py", line 378, in do_filesizeformat
bytes = float(value)
UndefinedError: 'dict object' has no attribute 'rx_per_sec'
If I don't create eth1:1 then all is well.
+1
ah, interesting. I'll check it out.
On 03/31/2014 03:01 AM, Joakim Hamrén wrote:
—
Reply to this email directly or view it on GitHub
#6 (comment).Yes, looks good. Thanks!