epoptes team mailing list archive

[Alek_A <ackbeat@xxxxxxxxx>]

Thanks for the info, again!

The problem is in determining ip address inside info()
I can see that command `ip -oneline -family inet addr show dev eth0` returns several IPs:
2: eth0    inet 91.90.38.142/30 brd 91.90.38.143 scope global eth0\       valid_lft forever preferred_lft forever
2: eth0    inet 172.22.21.128/23 brd 172.22.21.255 scope global eth0:1\       valid_lft forever preferred_lft forever
2: eth0    inet 192.168.3.200/24 brd 192.168.3.255 scope global eth0:2\       valid_lft forever preferred_lft forever

In the statement:
IP=$(ip -oneline -family inet addr show dev "$def_iface" \
      | sed "s/.* \([0-9.]*\)\/.*/\\1/")
I added ';q' to sed script to force it to handle only 1st line:
      | sed "s/.* \([0-9.]*\)\/.*/\\1/;q")
and now it works! Client appears in epoptes!

OTHER OBSERVATIONS:
1. You should probably set LC_ALL=C when calling info() to pick values correctly, for example RAM is not determined because of Russian locale. The output of `free -m`:
             total       used       free     shared    buffers     cached
Память:       3828        531       3297         46         51        266
-/+ буферы/кэш:        213       3615
Swap:         3967          0       3967

So `grep "^Mem"` does not work. But `LC_ALL=C free -m` works.

2. Once after reboot I found that when when I execute info() on client it for some reason tun0 examined instead of eth0, other things were the same but MAC was different: 
MAC=6:0:CAAE1500DCFFFAAEDEDEFADEFAE100E

To check why I ran the following commands:
root@sklad:~# ip -oneline -family inet link show dev tun0
6: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 100\    link/none
root@sklad:~# ip -oneline -family inet link show dev tun0 | sed 'y/abcdef-/ABCDEF:/;s/[^A-F0-9:]//g'
6:0:CAAE1500DCFFFAAEDEDEFADEFAE100E

This happened only once, but I'm not sure whether or not it will happen
again...

-- 
You received this bug notification because you are a member of Epoptes
Developers, which is subscribed to Epoptes.
https://bugs.launchpad.net/bugs/1549467

Title:
  Standalone client is not showing in epoptes

Status in Epoptes:
  New

Bug description:
  Hello,

  I have two clients (172.22.21.128 and 172.22.21.129).
  Systems is almost identical Lubuntu 14.04 except that one box is also a router.

  I do epoptes-client from both clients with the same output:
   * Epoptes-client connecting to 172.22.11.20:789...
     ...done.
  Command line is not complete. Try option "help"

  Also on the server I run: netstat -tp | grep 789
  tcp        0      0 ts.ad.aris-omsk.ru:789  172.22.21.129:33903     ESTABLISHED 26304/python    
  tcp        0      0 ts.ad.aris-omsk.ru:789  172.22.21.128:34489     ESTABLISHED 26304/python    

  Client 172.22.21.129 appears  in epoptes console, client 172.22.21.128
  does not whatever I do.

  I'm sorry. I don't know how to debug this. Could you help me please.

To manage notifications about this bug go to:
https://bugs.launchpad.net/epoptes/+bug/1549467/+subscriptions