Testing run_local_eve_adam.sh on Ubuntu Desktop 18.04. February 25, 2020
Host machine:
Intel(R) Core(TM) i5-3317U CPU @ 1.70GHz
MemTotal: 3852592 kB
Ubuntu Desktop 18.04
Logged in via ssh by user "root":
inna@Inna-PC:~$ ssh -p 22221 root@77.234.203.244
Moved to the github/itmo-eve/eveadm directory
root@eve:~# cd github/itmo-eve/eveadm
Perform "git pull":
root@eve:~/github/itmo-eve/eveadm# git pull
Already up to date.
Run "run_local_eve_adam.sh"
root@eve:~/github/itmo-eve/eveadm# ./tests/run_local_eve_adam.sh
========================================
Temp directory for test: /tmp/eveadam-2020-02-25-14-24-22-OfjNZTXXMr
========================================
Hit:1 http://ru.archive.ubuntu.com/ubuntu bionic InRelease
Get:2 http://ru.archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Get:3 http://ru.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Get:4 http://ru.archive.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Ign:5 http://ubuntu-cloud.archive.canonical.com/ubuntu bionic-updates/train InRelease
Hit:6 http://ubuntu-cloud.archive.canonical.com/ubuntu bionic-updates/train Release
Fetched 252 kB in 1s (252 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The log ends with the following:
========================================
Try to modify EVE config
========================================
You can connect to eve via telnet:
telnet localhost 49526
========================================
Trying again. Try #0
Trying again. Try #1
Trying again. Try #2
Trying again. Try #3
Trying again. Try #4
Trying again. Try #5
Trying again. Try #6
Trying again. Try #7
Trying again. Try #8
Trying again. Try #9
Trying again. Try #10
Trying again. Try #11
Trying again. Try #12
Trying again. Try #13
Trying again. Try #14
Trying again. Try #15
Trying again. Try #16
Trying again. Try #17
Trying again. Try #18
Trying again. Try #19
Trying again. Try #20
Trying again. Try #21
Trying again. Try #22
Trying again. Try #23
Trying again. Try #24
Trying again. Try #25
Trying again. Try #26
Trying again. Try #27
Trying again. Try #28
Trying again. Try #29
Failed to list devices!
========================================
You can connect to eve via telnet:
telnet localhost 49526
========================================
Do you want to try again? (y/n)
Full run_local_eve_adam.sh log
Сonnect to eve via telnet:
root@eve:~# telnet localhost 49526
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Execute the command "ip a"
linuxkit-525400123456:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff
inet6 fe80::867:2024:fde6:7c85/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 52:54:00:12:34:57 brd ff:ff:ff:ff:ff:ff
inet6 fe80::e851:dab7:4f8c:a2a7/64 scope link
valid_lft forever preferred_lft forever
4: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN qlen 1000
link/ipip 0.0.0.0 brd 0.0.0.0
5: ip6tnl0@NONE: <NOARP> mtu 1452 qdisc noop state DOWN qlen 1000
link/tunnel6 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 brd 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
eth0 / eth1 does not have IP addresses
Execute the command "eve enter"
linuxkit-525400123456:~# eve enter
(ns: pillar) linuxkit-525400123456:/#
Execute the command "dhcpcd --noipv4ll -4 eth0"
(ns: pillar) linuxkit-525400123456:/# dhcpcd --noipv4ll -4 eth0
DUID 00:01:00:01:25:e7:f1:e0:52:54:00:12:34:56
eth0: IAID 00:12:34:56
eth0: soliciting a DHCP lease
eth0: offered 192.168.0.10 from 192.168.0.2
eth0: probing address 192.168.0.10/24
eth0: leased 192.168.0.10 for 86400 seconds
eth0: adding route to 192.168.0.0/24
eth0: adding default route via 192.168.0.2
forked to background, child pid 4809
Execute the command "dhcpcd --noipv4ll -4 eth1"
(ns: pillar) linuxkit-525400123456:/# dhcpcd --noipv4ll -4 eth1
DUID 00:01:00:01:25:e7:f1:e0:52:54:00:12:34:56
eth1: IAID 00:12:34:57
eth1: soliciting a DHCP lease
eth1: offered 192.168.3.10 from 192.168.3.2
eth1: probing address 192.168.3.10/24
eth1: leased 192.168.3.10 for 86400 seconds
eth1: adding route to 192.168.3.0/24
eth1: adding default route via 192.168.3.2
forked to background, child pid 4866
Execute the command "ip a" again
(ns: pillar) linuxkit-525400123456:/# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.10/24 brd 192.168.0.255 scope global noprefixroute eth0
valid_lft forever preferred_lft forever
inet6 fe80::867:2024:fde6:7c85/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 52:54:00:12:34:57 brd ff:ff:ff:ff:ff:ff
inet 192.168.3.10/24 brd 192.168.3.255 scope global noprefixroute eth1
valid_lft forever preferred_lft forever
inet6 fe80::e851:dab7:4f8c:a2a7/64 scope link
valid_lft forever preferred_lft forever
4: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
link/ipip 0.0.0.0 brd 0.0.0.0
5: ip6tnl0@NONE: <NOARP> mtu 1452 qdisc noop state DOWN group default qlen 1000
link/tunnel6 :: brd ::
Now eth0 / eth1 have IP addresses. But there is no connection to the controller.
WARNING: 0 out of 2 ports specified to have EV controller connectivity passed test
Run "/opt/zededa/bin/diag". The results of the execution can be found in the test log.
/opt/zededa/bin/diag