search

platinasystems / go

Other
9 stars 68 forks source link

redis ip of i-44 not reachable #144

Closed sandeep-dutta closed 5 years ago

sandeep-dutta commented 5 years ago

Goes Version root@invader29:/home/sandeep# goes vnetd -version fe1: v1.1.3 fe1a: v1.1.0 vnet-platina-mk1: v1.0.0

Goes build checksum- 5046b7c2cdea8604d331dd7e5dd2fb9c85fa21ff

Kernel version root@invader29:/home/sandeep# dpkg --list |grep kernel ii linux-image-4.13-platina-mk1 4.13-165-gbf3b5fef4591 amd64 Linux kernel, version 4.13-platina-mk1

Noticed that redis ip of invader-44 is not accessible & due to that unable to power cycle the box through its redis ip. Tried power cycling the box using the cmd "curl http://admin:1234@172.17.3.99:80/outlet?3=CCL # cycle" but that did not help is bringing the redis ip of the invader.

sandeep@invader28:~/xeth/go/ansible/regtest$ ping 172.17.3.44 PING 172.17.3.44 (172.17.3.44) 56(84) bytes of data. --- 172.17.3.44 ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1031ms

sandeep-dutta commented 5 years ago

I can reach the redis ip 172.17.3.44. Was there any issue with redis server for i-44 (172.17.2.44) or some ip related issues?

Thanks, Sandeep

sandeep-dutta commented 5 years ago

However I noticed that when we tried to power cycle i-44 it is throwing redis error.

root@invader43:/home/sandeep# ping 172.17.3.44 PING 172.17.3.44 (172.17.3.44) 56(84) bytes of data. 64 bytes from 172.17.3.44: icmp_seq=1 ttl=64 time=5.27 ms ^C --- 172.17.3.44 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 5.276/5.276/5.276/0.000 ms root@invader43:/home/sandeep# redis-cli -h 172.17.3.44 hset platina psu.powercycle true (error) ERROR can't hset platina psu.powercycle

This issue has been observed on all the invaders of setup-2 (i-45, i-43, i-42) as well.

As a work around , power cycled i-44 through curl cmd mentioned below curl http://admin:1234@172.17.3.99:80/outlet?3=CCL # cycle

sandeep-dutta commented 5 years ago

Due to recent changes in redis cmds , the cmd which we were using to power cycle the invaders is not valid now. The updated cmd is

We are able to power cycle the invaders now.

Closing the bug.