- 论坛徽章:
- 0
|
故障状态\r\n1、当ESX4.0服务器重启后,30到40分钟都无法连接到vCenter,也无法通过vSphere Client和vSphere Web Access访问;\r\n2、重启管理agent之后,一样会很长时间无发连到ESX主机(10分钟或更长时间);\r\n3、在/etc/resov.conf中已经设定了DNS服务器了,但是,DNS解析不成功;\r\n4、使用vSphere Client直接连ESX主机时提示如下错误:\r\n The server could not interpret the communication from the client. (The remote server returned an error: (503) Server Unavailable.)\r\n5、在/var/log里面现实的vmware-authd服务重启的信息如下:\r\n \r\nSep 27 11:14:20 esx02 xinetd[2973]: START: vmware-authd pid=21102 from=127.0.0.1 \r\nSep 27 11:14:20 esx02 xinetd[2973]: EXIT: vmware-authd status=255 pid=21102 duration=0(sec) \r\nSep 27 11:14:20 esx02 xinetd[2973]: START: vmware-authd pid=21103 from=127.0.0.1 Sep 27 11:14:20 esx02 xinetd[2973]: EXIT: vmware-authd status=255 pid=21103 duration=0(sec) \r\n\r\n6、/var/log/vmware/hostd.log文件中包含了关于hostdsvc插件启动超时的日志信息:\r\n[2009-09-27 11:02:08.815 F664F6D0 info \'App\'] Trying blklistsvc \r\n[2009-09-27 11:02:08.820 F664F6D0 info \'App\'] Trying cimsvc [2009-09-27 11:02:08.831 F664F6D0 info \'App\'] Trying directorysvc \r\n[2009-09-27 11:02:08.845 F664F6D0 info \'App\'] Trying hostsvc\r\n[2009-09-27 11:02:20.100 F664F6D0 info \'App\'] Trying httpnfcsvc[2009-09-27 11:02:20.100 F664F6D0 verbose \'App\'] [DiskLibWrapperLoader_Init] Trying to load disk lib: diskLibWrapper.so, \r\n\r\n故障分析\r\n这可能由于DNS解析失败导致的\r\n\r\n解决方案\r\n务必确认ESX主机的DNS解析是否成功,解决方式如下:\r\n1、利用SSH登录到ESX主机,然后执行下列命令来确认DNS的解析端口是否正常:\r\n tcpdump -nvvvl -i vswif0 port 53\r\n如果弹出类似如下信息,则表示DNS服务器有问题:\r\n16:32:26.773870 IP (tos 0x0, ttl 64, id 62337, offset 0, flags [DF], proto: UDP (17), length: 66) 10.21.64.129.58720 > 192.199.99.255.domain: [bad udp cksum af30!] 61766+ PTR? 0.0.0.0.in-addr.arpa. (38)\r\n\r\n2、然后就去解决DNS服务器的问题,同时建议在/etc/hosts文件中加入本地文件解析的方式,做一个双保险! |
|