I have the same problem which is addressed here https://communities.vmware.com/docs/DOC-28682?z=BYJ9FY
Though in this case, it doesn't show up in the /mob nor it doesn't tell anything specific about failing in the vcenter logs. My vcenter is an appliance (newest 5.5 version, updated today).
Openstack is mentioned in the vcenter only on these places:
find / -xdev -type f -print0 | xargs -0 grep -H "openstack"
Binary file /usr/lib/vmware-vpx/sps/resources/cachedb/sms-cache0.h2.db matches
Binary file /usr/lib/vmware-vpx/sps/resources/cachedb/sms-cache1.h2.db matches
/etc/services:openstack-id 35357/tcp # OpenStack ID Service [Rackspace_Hosting] [Ziad_Sawalha]
ESXi host is also running newest 5.5. VIO management server appliance boots up ok (though it sets up localhost.localdom system name, and there's fqdn + reverse configured during the installation)
Management server reboot doesn't solve the issue, neither does reloggin from web client. Both vcenter and management server are in the same private subnet ( /24) and can ssh to each other.
Please check your DNS server name, from the the error message it seems that the DNS server name didn't start with a letter character.
by the way it will be good that if you can do the follow things.
run $> viogetlogs
on the management server and upload the log file.
Hi yjia,
Thanks for your feedback, I have checked the DNS server as shown below (ran lookup from OMS server as well the DNS machine with the same results), DNS appears to be working fine for other machines in the environment "jumpserver" is the designated primary name server for viotest.lab domain:
deploy@jumpserver:~$ hostname
jumpserver
deploy@jumpserver:~$ nslookup jumpserver
Server: 192.168.30.5
Address: 192.168.30.5#53
Name: jumpserver.viotest.lab
Address: 192.168.30.5
deploy@jumpserver:~$ nslookup 192.168.30.5
Server: 192.168.30.5
Address: 192.168.30.5#53
5.30.168.192.in-addr.arpa name = ns.viotest.lab.
5.30.168.192.in-addr.arpa name = jumpserver.viotest.lab.
I have also ran the "viogetlogs" as suggested with the following result (ran the command as both viouser + root):
root@vio-manager:/var/log# viogetlogs
Configuration failed on the following nodes: ['127.0.0.1'].
Success: Collected logs to '/var/log/201505260708.tgz'
root@vio-manager:/var/log# ls -ltr
total 61328
drwxr-xr-x 2 root root 4096 Apr 12 2014 dist-upgrade
drwxr-xr-x 2 ntp ntp 4096 Dec 20 11:47 ntpstats
drwxr-xr-x 2 root root 4096 Mar 6 15:44 fsck
drwxr-xr-x 2 root root 4096 Mar 6 15:44 apt
drwxr-x--- 2 omsapp adm 4096 Mar 6 15:49 oms
drwxr-xr-x 2 jarvis viogrp 4096 Mar 6 15:49 support
drwxr-x--- 2 jarvis adm 4096 Mar 6 15:49 jarvis
drwxr-x--- 2 omsapp adm 4096 Mar 6 15:49 osvmw
drwxr-xr-x 3 root root 4096 Mar 6 15:49 installer
-rw-r--r-- 1 root root 0 Mar 6 15:49 alternatives.log
-rw-r----- 1 root adm 0 Mar 6 15:49 dmesg.0
-rw-r--r-- 1 root root 0 Mar 6 15:49 bootstrap.log
-rw-r----- 1 root adm 28 Mar 6 15:49 dmesg.1.gz
-rw-r--r-- 1 root root 648 Mar 6 15:49 dpkg.log
-rw-r--r-- 1 root root 255052 May 22 16:22 udev
-rw-r----- 1 root adm 90927 May 22 16:22 dmesg
-rw-r--r-- 1 root root 3423 May 22 16:22 boot.log
-rw-r--r-- 1 root root 32096 May 22 16:22 faillog
-rw-r--r-- 1 root root 3729 May 22 16:23 bootsequence.log
-rw-r----- 1 syslog adm 140921 May 22 16:23 kern.log.1
-rw-r----- 1 syslog adm 297788 May 23 00:17 syslog.4.gz
-rw-r----- 1 syslog adm 839228 May 24 00:17 syslog.3.gz
drwxr-x--- 2 apache adm 4096 May 24 00:17 apache2
-rw-r----- 1 syslog adm 18070091 May 24 00:17 auth.log.1
-rw-r----- 1 syslog adm 0 May 24 00:17 kern.log
-rw-r----- 1 syslog adm 835170 May 25 00:17 syslog.2.gz
-rw-r----- 1 syslog adm 8534767 May 26 00:17 syslog.1
drwxr-xr-x 2 root root 4096 May 26 00:17 upstart
-rw-rw---- 1 root utmp 768 May 26 06:36 btmp
-rw-rw-r-- 1 root utmp 11136 May 26 06:37 wtmp
-rw-rw-r-- 1 root utmp 292876 May 26 06:37 lastlog
-rw-r----- 1 syslog adm 2453659 May 26 07:08 syslog
-rw-r----- 1 syslog adm 31067297 May 26 07:08 auth.log
root@vio-manager:/var/log#
Thanks
Steve
OK, it seem you give the management server a host name ?
and the hostname isn't a valid FQDN name, can you please leave it as blank when you deploy the vApp ?
Hi again,
OK I have removed the DNS entries relating to the OMS server itself & redployed the Vapp without providing a hostname as suggested.
This has improved things in that I can now see some logs being generated in /oms, however I'm still unable to see the plugin present in the VC web console.
I have re-applied the 1.0.1 patch
I have had a look at the /var/log/oms.log file (attached) and seem some errors, but unsure how to proceed ... ?
The register-plugin.log is currently empty
Thanks for your help, much appreciated
Hi yjia,
Many thanks for your assistance & the troubleshooting PDF - we have recerated the VC SSL cert & we are now able to see the VIO plugin with the web client 8-)
Thanks again
Regards
Steve
Your are welcome!