GUI error for STA position for telemetry in containernet

[srikrishna acharya]

I was testing the two stations one access point configuration. the script launches the dockers properly and everything is working but the gui is creating the issue. 

the error is :

Exception in thread Thread-1:

Traceback (most recent call last):

  File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner

    self.run()

  File "/usr/lib/python2.7/threading.py", line 754, in run

    self.__target(*self.__args, **self.__kwargs)

  File "/usr/local/lib/python2.7/dist-packages/mininet_wifi-2.5-py2.7.egg/mn_wifi/telemetry.py", line 73, in start

    parseData(nodes, self.axes, single, data_type=data_type, fig=fig, **kwargs)

  File "/usr/local/lib/python2.7/dist-packages/mininet_wifi-2.5-py2.7.egg/mn_wifi/telemetry.py", line 177, in __init__

    self.start(nodes, axes, single, data_type, fig, **kwargs)

  File "/usr/local/lib/python2.7/dist-packages/mininet_wifi-2.5-py2.7.egg/mn_wifi/telemetry.py", line 321, in start

    self.phys, self.ifaces = telemetry.get_phys(nodes, inNamespaceNodes)

  File "/usr/local/lib/python2.7/dist-packages/mininet_wifi-2.5-py2.7.egg/mn_wifi/telemetry.py", line 121, in get_phys

    shell=True).decode().split("\n")

  File "/usr/lib/python2.7/subprocess.py", line 223, in check_output

    raise CalledProcessError(retcode, cmd, output=output)

CalledProcessError: Command '/usr/local/lib/python2.7/dist-packages/mininet_wifi-2.5-py2.7.egg//util/m mybot1 ls /sys/class/ieee80211/' returned non-zero exit status 2

[Ramon Fontes]

You may have to change <telemetry.py> if you are running the code in docker containers.

[srikrishna acharya]

What should I change specfically.. 

[Ramon Fontes]

You have the line number which threw an exception, right? So I suggest starting from there.

[srikrishna acharya]

I didn't get any errors if I use mininet_wifi instead of containernet. 

[Ramon Fontes]

As I said, changes might be required in telemetry.py if you want to make it work with docker containers - I've never run it with containernet. So considering that you have the line number which threw an exception, you should start from there.

[srikrishna acharya]

Using Containernet, the telemetry class method get_phys is creating command using subprocess

 /usr/local/lib/python2.7/dist-packages/mininet_wifi-2.5-py2.7.egg/util/m mybot1 ls /sys/class/ieee80211/ 

results error shown below

 Error: found multiple mininet:mybot1 processes

but at the same time using mininet-wifi the command outputs the phy address say  mn26351p01s01

without mininet util/m 

ls /sys/class/ieee80211/ results 

mn30122p01s01  phy0

can you suggest some pointers to look into

 

[srikrishna acharya]

I further looked into /util/m file where it tries to find the process at line number 12

pid=`ps ax | grep "mininet:$host$" | grep bash | grep -v mnexec | awk '{print $1};'`

ps ax | grep mininet:sta1   results two processes 

acharya   5670  0.0  0.0  14432  1052 pts/4    S+   14:54   0:00 grep --color=auto mininet:sta1

root     30308  0.0  0.1 1214992 55992 pts/3   Sl+  14:33   0:00 docker exec -it mn.sta1 env PS1=? bash --norc -is mininet:sta1

root     30331  0.0  0.0   5992  3796 pts/1    Ss+  14:33   0:00 bash --norc -is mininet:sta1

whereas using mininet-wifi results in only one process

root      6349  0.0  0.0  21344  3516 pts/6    Ss+  14:56   0:00 bash --norc --noediting -is mininet:sta1

acharya   6674  0.0  0.0  14432  1092 pts/4    S+   14:56   0:00 grep --color=auto mininet:sta1

[srikrishna acharya]

Which process should I select

[Ramon Fontes]

> Error: found multiple mininet:mybot1 processes

How many nodes named mybot1 does the network topology have?

--
You received this message because you are subscribed to the Google Groups "mininet-wifi-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mininet-wifi-dis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mininet-wifi-discuss/22f58087-71b2-4c09-b9c3-b19e3c6555e8n%40googlegroups.com.

[Ramon Fontes]

You can try bash --norc --noediting -is mininet:sta1

[srikrishna acharya]

If I select process 

17606 pts/1    Ss+    0:00 bash --norc -is mininet:mybot1

Results in : No such file or directory error

if I select process 

17584 pts/3    Sl+    0:00 docker exec -it mn.mybot1 env PS1=? bash --norc -is mininet:mybot1

there is no error but the AP is selected in all the cases.. 

[Ramon Fontes]

Well, changes in containernet might be required if you want to get the process running on the host. By the way tools such as linssid may fit your needs.

Sent from my android

--

You received this message because you are subscribed to the Google Groups "mininet-wifi-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mininet-wifi-dis...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/mininet-wifi-discuss/810f82c1-7473-497f-9bf6-c8e26da397dcn%40googlegroups.com.

[srikrishna acharya]

Thank you.. I will check it out.