开始新对话

此帖子已超过 5 年

Solved!

Go to Solution

5769

2015年11月2日 01:00

EMC Avamar Virtual Machine Combined Proxy在avamar無法連線了~

Dear all:

今天突然發現EMC Avamar Virtual Machine Combined Proxy 在avamar上顯示沒有連線。

完全沒有頭緒該怎麼解這問題呢?如何讓他重新連線?

圖片 1.png

4K 消息

2015年11月5日 01:00

设置hostname好像挺复杂的,你参考这条KB看看:How to setup new Avamar 6.1 proxy hostname

https://support.emc.com/kb/95194

不过这条KB仅限EMC员工或经销商访问,具体内容可以从这篇帖子中拿到:

Re: How can I re-register a Universal Proxy with the Avamar management console?

6 消息

2015年11月2日 21:00

你可以看一下avagent log (/usr/local/avamarclient/var-proxy-1/avagent.log) 有没有什么报错.

重新注册的话,运行 /usr/local/avamarclient/etc/initproxyappliance.sh start

- Lilian

4K 消息

2015年11月2日 22:00

重新注册试试,注册不上再看看报错

221 消息

2015年11月3日 17:00

感謝各位~剛試試看從新註冊,但還是不能用,我將avagent.log列出來看看,

(192.168.1.174是avanar virtual machine combined proxy 主機的IP)

看到是寫無法連線自己的28001 port?怎麼辦呢?

2015-11-04 09:15:53 avagent Info <6626>: Agent Main: Client ID (cid) = 3239b00ae212f943958262000af1d63323c6617b

2015-11-04 09:15:53 avagent Info <6601>: Hostnamelist: 127.0.0.2,192.168.1.174

2015-11-04 09:15:53 avagent Info <5933>: Checking for plugin information files (.pin) in /usr/local/avamarclient/var-proxy-1

2015-11-04 09:15:53 avagent Info <5933>: Checking for plugin information files (.pin) in /usr/local/avamarclient/bin

2015-11-04 09:15:53 avagent Info <5934>: Reading pin file /usr/local/avamarclient/bin/vcbimage-linux.pin

2015-11-04 09:15:53 avagent Info <7264>: Finished READING xml file - starting parse

2015-11-04 09:15:53 avagent Info <6627>: Checking version of plugin 'vmimagel', executable name 'avvcbimage' (mode:ctl)

2015-11-04 09:15:53 avagent Warning <5790>: Standard error stdout_data from plugin 'vmimagel' version check

2015-11-04 09:15:53 avagent Info <5936>: Plugin version 7.0.102-43 found for vmimagel plugin

2015-11-04 09:15:53 avagent Info <12489>: mess 0 '

'

2015-11-04 09:15:53 avagent Info <5934>: Reading pin file /usr/local/avamarclient/bin/unix.pin

2015-11-04 09:15:53 avagent Info <7264>: Finished READING xml file - starting parse

2015-11-04 09:15:53 avagent Info <6627>: Checking version of plugin 'Unix', executable name 'avtar.bin' (mode:ctl)

2015-11-04 09:15:53 avagent Info <5936>: Plugin version 7.0.102-43 found for Unix plugin

2015-11-04 09:15:53 avagent Info <12489>: mess 1 '

'

2015-11-04 09:15:53 avagent Info <5934>: Reading pin file /usr/local/avamarclient/bin/vmwfile-windows.pin

2015-11-04 09:15:53 avagent Info <7264>: Finished READING xml file - starting parse

2015-11-04 09:15:53 avagent Info <6627>: Checking version of plugin 'vmwfilew', executable name 'avvmwfile' (mode:ctl)

2015-11-04 09:15:53 avagent Warning <5790>: Standard error stdout_data from plugin 'vmwfilew' version check

2015-11-04 09:15:53 avagent Info <5936>: Plugin version 7.0.102-43 found for vmwfilew plugin

2015-11-04 09:15:53 avagent Info <12489>: mess 2 '

'

2015-11-04 09:15:53 avagent Warning <8444>: Ignoring plugin file /usr/local/avamarclient/bin/vappimage.pin, it is not specified in pin_include option!

2015-11-04 09:15:53 avagent Info <5934>: Reading pin file /usr/local/avamarclient/bin/vmwfile-linux.pin

2015-11-04 09:15:53 avagent Info <7264>: Finished READING xml file - starting parse

2015-11-04 09:15:53 avagent Info <6627>: Checking version of plugin 'vmwfilel', executable name 'avvmwfile' (mode:ctl)

2015-11-04 09:15:53 avagent Warning <5790>: Standard error stdout_data from plugin 'vmwfilel' version check

2015-11-04 09:15:53 avagent Info <5936>: Plugin version 7.0.102-43 found for vmwfilel plugin

2015-11-04 09:15:53 avagent Info <12489>: mess 3 '

'

2015-11-04 09:15:53 avagent Info <5934>: Reading pin file /usr/local/avamarclient/bin/vcbimage-windows.pin

2015-11-04 09:15:53 avagent Info <7264>: Finished READING xml file - starting parse

2015-11-04 09:15:53 avagent Info <6627>: Checking version of plugin 'vmimagew', executable name 'avvcbimage' (mode:ctl)

2015-11-04 09:15:53 avagent Warning <5790>: Standard error stdout_data from plugin 'vmimagew' version check

2015-11-04 09:15:53 avagent Info <5936>: Plugin version 7.0.102-43 found for vmimagew plugin

2015-11-04 09:15:53 avagent Info <12489>: mess 4 '

'

2015-11-04 09:15:54 avagent Info <5470>: Updating registration information with the MCS (192.168.1.174), paging enabled

2015-11-04 09:15:54 avagent Error <5365>: Cannot connect to 192.168.1.174:28001.

2015-11-04 09:15:54 avagent Info <5059>: unable to connect, sleep(60) then retrying

2015-11-04 09:16:54 avagent Error <5365>: Cannot connect to 192.168.1.174:28001.

2015-11-04 09:16:54 avagent Info <5059>: unable to connect, sleep(60) then retrying

2015-11-04 09:17:54 avagent Error <5365>: Cannot connect to 192.168.1.174:28001.

2015-11-04 09:17:54 avagent Info <5059>: unable to connect, sleep(60) then retrying

2015-11-04 09:18:54 avagent Error <5365>: Cannot connect to 192.168.1.174:28001.

2015-11-04 09:18:54 avagent Info <5059>: unable to connect, sleep(60) then retrying

2015-11-04 09:19:54 avagent Error <5365>: Cannot connect to 192.168.1.174:28001.

2015-11-04 09:19:54 avagent Info <5059>: unable to connect, sleep(60) then retrying

2015-11-04 09:20:54 avagent Error <5365>: Cannot connect to 192.168.1.174:28001.

2015-11-04 09:20:54 avagent Info <18054>: agent_commands::register_agent Registered MC address = ::1

2015-11-04 09:20:54 avagent Error <6210>: Unable to register 'localhost-proxy-1' with MCS at 192.168.1.174:28001

2015-11-04 09:20:54 avagent Error <7500>: Registration error: NULL message received

2015-11-04 09:20:54 avagent Info <5321>: Unable to connect to Management Console (192.168.1.174), sleep 44 minutes, 2 seconds before retry

221 消息

2015年11月3日 21:00

您好:

確認網路通的,並且參照上方的指令執行過( /usr/local/avamarclient/etc/initproxyappliance.sh start),

也將EMC Avamar Virtual Machine Combined Proxy主機重新啟動過,仍然無效~


圖片 1.png

4K 消息

2015年11月3日 21:00

网络确认是连通的?试过重启了不?

6 消息

2015年11月3日 23:00

"192.168.1.174" 这个是proxy的ip吗? 注册的时候需要输入的是Avamar server的ip或hostname.

- Lilian

5 Practitioner

 • 

274.2K 消息

2015年11月4日 16:00

这里应该有两个问题:

1. proxy 的主机名字是“localhost”,这个应该是不正确的。导致问题的原因应该是proxy上的DNS服务器没有正确配置。 请在proxy上先设置主机名,并配置正确的DNS服务器,确保对proxy IP的反向解析能够识别出该主机名。然后重启proxy,确保主机名显示正确

2.  Avamar 服务器的IP为192.168.1.174,请确保此IP正确,或者重新注册,运行 /usr/local/avamarclient/etc/initproxyappliance.sh start,并输入正确的Avamar 主机IP。另外,如果需要测试网络,运行:curl AvamarIP:28001. 用curl命令去检测Avamar服务器的28001端口,确保连接正常

221 消息

2015年11月4日 22:00

Hi simom:

您看到問題點了,沒錯,我後來才發現hostname的問題~哈,感謝您。

但有另一個狀況,就是我每次改完etc/hosts 存檔離開,重新開機,hostname又會被改為錯誤的!!

221 消息

2015年11月5日 01:00

感謝roger提供的連結,我再試試看

找不到事件!

Top