VMware Cloud Community
msaravanaganesh
Contributor
Contributor

tun0 error fetching interface information device not found

Our vCOP environment went down after restart I observe below errors.

Start of UI VM in the console I observe

tun0 error fetching interface information device not found

tun0 error fetching interface information device not found

tun0 error fetching interface information device not found

tun0 error fetching interface information device not found

tun0 error fetching interface information device not found

After both UI and Analytical VM booted when I check the vCOP services status.

admin@xxxxxxxxx:/> ssh admin@firstvm-external vcops-admin status
ssh: connect to host secondvm-internal port 22: Connection timed out
Use of uninitialized value $statuses{"activemq"} in string eq at /usr/local/bin/vcops-admin line 1813.
Use of uninitialized value $status in string eq at /usr/local/bin/vcops-admin line 1785.
Use of uninitialized value $status in string eq at /usr/local/bin/vcops-admin line 1785.
Use of uninitialized value $status in string eq at /usr/local/bin/vcops-admin line 1785.
vCenter Operations Manager Status

vCenter Operations Manager Service = Stopped
vCenter Operations Manager Collector Service = Stopped
vCenter Operations Manager Analytics Service = Stopped
vCenter Operations Manager ActiveMQ Broker Service = Stopped
vCenter Operations Manager Web Service = Running
vCenter Operations Manager Web Enterprise Service = Running
vCenter Operations Manager Admin Web Service = Running


I found few services are stopped and also " ssh: connect to host secondvm-internal port 22: Connection timed out" when i try to ping the secondvm-internal getting time out.


Could some one please help to find what needs to checked.

0 Kudos
1 Reply
gradinka
VMware Employee
VMware Employee

well most likely the IP of the second vm (analytics_vm) have changed.

checkout this KB -> http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=203188...

0 Kudos