Skip to main content

Mininet/Containernet Problem: Exception: Error creating interface pair (s2-eth5,s3-eth1): RTNETLINK answers: File exists

If you did not shut down the previous running mininet/containernet network (e.g. if you lose your connection to remote server), you will got the following error when you try to rerun your mininet network

Traceback (most recent call last):
  File "./mynet.py", line 31, in <module>
    net.addLink(d2, s1)
  File "build/bdist.linux-x86_64/egg/mininet/net.py", line 403, in addLink
  File "build/bdist.linux-x86_64/egg/mininet/link.py", line 430, in __init__
  File "build/bdist.linux-x86_64/egg/mininet/link.py", line 474, in makeIntfPair
  File "build/bdist.linux-x86_64/egg/mininet/util.py", line 202, in makeIntfPair
Exception: Error creating interface pair (d2-eth0,s1-eth2): RTNETLINK answers: File exists

In order to solve the problem, you need to clean up the previous running topology by using the following command

sudo mn -c

It will clean up all your cache. It will be something like this

$ sudo mn -c
*** Removing excess controllers/ofprotocols/ofdatapaths/pings/noxes
killall controller ofprotocol ofdatapath ping nox_core lt-nox_core ovs-openflowd ovs-controller udpbwtest mnexec ivs 2> /dev/null
killall -9 controller ofprotocol ofdatapath ping nox_core lt-nox_core ovs-openflowd ovs-controller udpbwtest mnexec ivs 2> /dev/null
pkill -9 -f "sudo mnexec"
*** Removing junk from /tmp
rm -f /tmp/vconn* /tmp/vlogs* /tmp/*.out /tmp/*.log
*** Removing old X11 tunnels
*** Removing excess kernel datapaths
ps ax | egrep -o 'dp[0-9]+' | sed 's/dp/nl:/'
***  Removing OVS datapaths
ovs-vsctl --timeout=1 list-br
ovs-vsctl --if-exists del-br s1 -- --if-exists del-br s2 -- --if-exists del-br s3
ovs-vsctl --timeout=1 list-br
*** Removing all links of the pattern foo-ethX
ip link show | egrep -o '([-_.[:alnum:]]+-eth[[:digit:]]+)'
( ip link del s2-eth1;ip link del s1-eth3;ip link del s1-eth3;ip link del s2-eth1;ip link del s3-eth1;ip link del s2-eth2;ip link del s2-eth2;ip link del s3-eth1;ip link del s1-eth1 ) 2> /dev/null
ip link show
*** Killing stale mininet node processes
pkill -9 -f mininet:
*** Shutting down stale tunnels
pkill -9 -f Tunnel=Ethernet
pkill -9 -f .ssh/mn
rm -f ~/.ssh/mn/*
***  Removing SAP NAT rules
*** Cleanup complete.

Comments

Popular posts from this blog

Make UnitTest Report Using HTMLTestRunner

I am a big fan of Python, and I am a big fan of TDD (Test Driven Development). The problem that I face for team development was that it is quite difficult to communicate the testing results to the team, because the results are in terminal so only us and God know :D Fortunately, somebody out there know my problem and create this amazing HTMLTestRunner.py. This tool is very handy and very easy to use. It almost feels like you don't need to do anything. OK, here's one example on how we use HTMLTestRunner. Ah, forget it. Download HTMLTestRunner.py from this website , and put somewhere in your computer. Say in this example, I put in ~/Downloads/HTMLTestRunner folder import unittest import sys _path = r"Downloads/HTMLTestRunner" sys.path.append(_path) import HTMLTestRunner class TestDemo(unittest.TestCase):     def testA(self):         assert True     def testB(self):         assert False class TestDemo2(unittest.TestCase):     def testC(self):         ass

Find JIRA issues mentioned in Confluence Page

I have been walking through a lot of pages in internet but have not found any answer except one. However, the answer is not complete, so I will share my experience here. This feature is very useful, especially to summarize the issues found during certain tests, where the tests are reported in a confluence page. I found that there are so many questions about this, but Atlassian seems does not want to bother with this request. I found one way to do this by the following tricks Take one JIRA issue that related to the target confluence page (in this case, say it is GET-895) Find the global ID of a JIRA issue: http://bach.dc1.scram.com:8080/rest/api/latest/issue/GET-895/remotelink It will show the JSON like this: [{"id":28293,"self":"http://bach.dc1.scram.com:8080/rest/api/latest/issue/GET-895/remotelink/28293","globalId":"appId=662e1ccf-94da-3121-96ae-053d90587b29&pageId=105485659","application":{