单击“显示已连接的设备”后,Provisioning Server Console中的超时错误

参考KB: http://support.citrix.com/article/CTX133877
当分配给PVS服务器的多个流式NIC时,Provisioning Services(PVS)服务器上会出现以下症状。

具有五个流式NIC的环境具有以下症状:

当显示连接的设备 被点击的PVS控制台,以下症状可能会经历:
服务器超时错误4002

列出连接设备的异常延迟3到4分钟

PVS控制台停止响应
用户添加的图像
单击“显示已连接的设备”后,Provisioning Server Console中的超时错误

小心!在使用注册表编辑器之前,请参阅本文末尾的免责声明。

完成以下操作以解决此问题:
1、在PVS Server计算机上的HKLM \ software \ citrix \ provisioningServices \ Manager项下,创建注册表DWORD RelayedRequestReplyTimeoutMilliseconds,并将其设置为50 ms。
注意:确保选择十进制,而不是十六进制。

2、创建一个DWORD RelayedRequestTryTimes 并将其设置为1。
默认值为2。

3、打开PVS服务器控制台并选择Show Connected Devices命令进行测试。
问题原因
从PVS控制台运行Show Connected Devices命令时,它会将请求发送到绑定到流服务的每个接口,发送到每个目标设备,默认超时为5000毫秒,每个NIC两次,从而导致搜索时间每个设备,每个设备10秒。

示例:
5个NIC,1个当前连接的目标设备将在50秒内返回Show Connected Device。

您可以在流日志中清楚地看到它正在搜索分配给流服务的每个IP地址:

2012-05-25 10:05:24,614 [0x00000fdc] DEBUG CManagerConfig :: GetRelayedRequestTryTimes - <RelayedRequestTryTimes> = 2 2012-05-25 10:05:24,614 [0x00000fdc] DEBUG CManagerConfig :: GetRelayedRequestReplyTimeoutMilliseconds - <RelayedRequestReplyTimeoutMilliseconds> = 5000 2012-05-31 14:47:46,470 [0x00000e7c] DEBUG CManagerConfig :: GetServerIpGroupTryTimes - <ServerIpGroupTryTimes> = 2 2012-05-31 14:47:46,470 [0x00000e7c] DEBUG CManagerConfig :: GetServerReplyTimeoutMilliseconds - <ServerReplyTimeoutMilliseconds> = 50000 2012-05-31 14:47:46,470 [0x00000e7c]调试CManagerReplyReceiver:SendMessageToServer,requestId = 0
2012-05-31 14:47:46,486 [0x00000e7c]在CManagerReplyReceiver中调试:TryEachIpAddressIteratively
2012-05-31 14:47:46,486 [0x00000e7c] DEBUG会尝试向ip address发送请求= 2887140615,port = 6911
2012-05-31 14:47:46,486 [0x00000e7c]调试CManagerReplyReceiver:sendMessageAndWaitForResult
2012-05-31 14:47:46,501 [0x00000e7c] DEBUG为请求ID 0添加了未来
2012-05-31 14:47:46,501 [0x00000e7c] DEBUG到<172.22.69.7:6911>,即将发送80个字节
2012-05-31 14:47:46,501 [0x00000e7c] DEBUG发送80字节的80字节消息
2012-05-31 14:47:56,516 [0x00000e7c] DEBUG futureResult.get失败,错误= 121
2012-05-31 14:47:56,516 [0x00000e7c]错误远程请求超时
2012-05-31 14:47:56,532 [0x00000e7c] DEBUG for requestId = 0,返回结果= -32718(RemoteRequestTimedOut)。等待。
2012-05-31 14:47:56,532 [0x00000e7c] DEBUG futureMap中的条目数= 0
2012-05-31 14:47:56,532 [0x00000e7c] DEBUG将尝试向ip address = 2887140359发送请求,port = 6911
2012-05-31 14:47:56,532 [0x00000e7c]调试CManagerReplyReceiver:sendMessageAndWaitForResult
2012-05-31 14:47:56,532 [0x00000e7c] DEBUG为请求ID 0添加了未来
2012-05-31 14:47:56,532 [0x00000e7c] DEBUG到<172.22.68.7:6911>,即将发送80个字节
2012-05-31 14:47:56,532 [0x00000e7c] DEBUG发送80字节的80字节消息
2012-05-31 14:48:06,547 [0x00000e7c] DEBUG futureResult.get失败,错误= 121
2012-05-31 14:48:06,547 [0x00000e7c] ERROR远程请求超时
2012-05-31 14:48:06,547 [0x00000e7c] DEBUG for requestId = 0,返回result = -32718(RemoteRequestTimedOut)。等待。
2012-05-31 14:48:06,547 [0x00000e7c] DEBUG futureMap中的条目数= 0
2012-05-31 14:48:06,547 [0x00000e7c] DEBUG将尝试向ip address = 2887140103发送请求,port = 6911
2012-05-31 14:48:06,547 [0x00000e7c]在CManagerReplyReceiver中调试:sendMessageAndWaitForResult
2012-05-31 14:48:06,547 [0x00000e7c] DEBUG为请求ID 0添加了未来
2012-05-31 14:48:06,547 [0x00000e7c] DEBUG到<172.22.67.7:6911>,即将发送80个字节
2012-05-31 14:48:06,547 [0x00000e7c] DEBUG发送80字节的80字节消息
2012-05-31 14:48:16,562 [0x00000e7c] DEBUG futureResult.get失败,错误= 121
2012-05-31 14:48:16,562 [0x00000e7c]错误远程请求超时
2012-05-31 14:48:16,562 [0x00000e7c] DEBUG for requestId = 0,返回result = -32718(RemoteRequestTimedOut)。等待。
2012-05-31 14:48:16,562 [0x00000e7c] DEBUG futureMap中的条目数= 0
2012-05-31 14:48:16,562 [0x00000e7c] DEBUG将尝试向ip address发送请求= 2887139847,port = 6911
2012-05-31 14:48:16,562 [0x00000e7c]在CManagerReplyReceiver中调试:sendMessageAndWaitForResult
2012-05-31 14:48:16,562 [0x00000e7c] DEBUG为请求ID 0添加了未来
2012-05-31 14:48:16,562 [0x00000e7c] DEBUG到<172.22.66.7:6911>,即将发送80个字节
2012-05-31 14:48:16,562 [0x00000e7c] DEBUG发送80字节的80字节消息
2012-05-31 14:48:26,577 [0x00000e7c] DEBUG futureResult.get失败,错误= 121
2012-05-31 14:48:26,577 [0x00000e7c]错误远程请求超时
2012-05-31 14:48:26,577 [0x00000e7c] DEBUG for requestId = 0,返回结果= -32718(RemoteRequestTimedOut)。等待。
2012-05-31 14:48:26,577 [0x00000e7c] DEBUG futureMap中的条目数= 0
2012-05-31 14:48:26,577 [0x00000e7c] DEBUG将尝试向ip address发送请求= 2887139591,port = 6911
2012-05-31 14:48:26,577 [0x00000e7c]调试CManagerReplyReceiver:sendMessageAndWaitForResult
2012-05-31 14:48:26,577 [0x00000e7c] DEBUG为请求ID 0添加了未来
2012-05-31 14:48:26,577 [0x00000e7c] DEBUG到<172.22.65.7:6911>,即将发送80个字节
2012-05-31 14:48:26,577 [0x00000e7c] DEBUG发送80字节的80字节消息
2012-05-31 14:48:36,592 [0x00000e7c] DEBUG futureResult.get失败,错误= 121
2012-05-31 14:48:36,592 [0x00000e7c]错误远程请求超时
2012-05-31 14:48:36,592 [0x00000e7c] DEBUG for requestId = 0,返回结果= -32718(RemoteRequestTimedOut)。等待。
2012-05-31 14:48:36,592 [0x00000e7c] DEBUG futureMap中的条目数= 0
2012-05-31 14:48:36,592 [0x00000e7c] DEBUG将尝试向ip address = 2887139335发送请求,port = 6911
2012-05-31 14:48:36,592 [0x00000e7c]调试CManagerReplyReceiver:sendMessageAndWaitForResult
2012-05-31 14:48:36,592 [0x00000e7c] DEBUG为请求ID 0添加了未来
2012-05-31 14:48:36,592 [0x00000e7c] DEBUG到<172.22.64.7:6911>,即将发送80个字节
2012-05-31 14:48:36,592 [0x00000e7c] DEBUG发送80字节的80字节消息
2012-05-31 14:48:37,247 [0x000030fc]调试CManagerReplyReceiver :: dispatchPacket
2012-05-31 14:48:37,247 [0x000030fc] DEBUG标头操作码= -2147221501,请求id = 0
2012-05-31 14:48:37,247 [0x000030fc] DEBUG处理ManagedServer回复
2012-05-31 14:48:37,247 [0x000030fc] CREMoteManagedServer :: handleReply中的DEBUG
2012-05-31 14:48:37,247 [0x000030fc] DEBUG处理请求id = 0的回复
2012-05-31 14:48:37,263 [0x000030fc] DEBUG找到了requestId的未来
2012-05-31 14:48:37,263 [0x000030fc] DEBUG转换重新平衡回复的回复状态,默认成功
2012-05-31 14:48:37,278 [0x000030fc] CREMoteManagedServer中的DEBUG :: harvestReplyDataFromMessage
2012-05-31 14:48:37,278 [0x000030fc] DEBUG回复用于重新平衡请求,requestId = 0
2012-05-31 14:48:37,278 [0x000030fc]来自回复的DEBUG值为21
2012-05-31 14:48:37,278 [0x000030fc] DEBUG条目添加到requestId = 0的数据结果图
2012-05-31 14:48:37,294 [0x00000e7c] DEBUG futureResult.get对requestId = 0,actualResult = 0(成功)成功。等待。

上一篇:Cinder LVM Oversubscription in thin provisioning


下一篇:第五周作业