Hello Team,
Can someone please help me out if anybody come across the following situation?
- Part of the PeerNest testing, I have taken 3 clients with 2 clients having 9.5.11 version installed and 1 client with 9.5.13
- I have enabled both TCP/UDP port 52311 between the clients and all 3 clients are reporting to the same relay.
- All 3 clients belong to the same subnet and all of them does not have IPV6 enabled, so I have used setting called “_BESClient_Comm_IpCommunicationsMode” = “onlyIpv4”
- All 3 clients have the following settings enabled,
_BESClient_PeerNest_Enabled=1
_BESClient_PeerNest_IsPassive=0
_BESClient_PeerNest_ResponseTimeoutSeconds=300 (Initially kept 30 seconds, but since I could see time-out message in the peer to peer debug log, have increased to 300, but still it is getting timed-out)
- The following setting is enabled only on the client with 9.5.13 version
_BESClient_PeerNest_Priority=500
Rest of the 2 clients does not have the above setting, so by default the priority value taken will be 100.
- From the Peer to Peer debug log, I could see Timed-out response even after increasing to 300 seconds.
At 08:48:38 -0500 PeerNest: Socket was already joined to the IPv4 multicast group. Dropping it.
At 08:48:46 -0500 PeerNest: configure peer nest: Enabled: True; IsPassive: False; Priority: 100; Timeout: 300
At 08:48:47 -0500 PeerNest: Interface selected is 12 with address ::ffff:x.x.x.x (IP Address)
At 08:48:52 -0500 PeerNest: successfully joined the multicast group x.x.x.x
At 08:53:15 -0500 PeerNest: Asking for file SHA1 value
At 08:53:15 -0500 PeerNest: Sending peer message 1 for file SHA1 value
At 08:53:15 -0500 PeerNest: sent ipv4 peer multicast UDP message.
At 08:55:15 -0500 PeerNest: Timeout reached: 300
At 08:56:27 -0500 PeerNest: Sending peer message 4 for file SHA1 value
At 08:56:27 -0500 PeerNest: sent ipv4 peer multicast UDP message.
At 08:56:28 -0500 PeerNest: Action (ID) removed from peer list.
- From the client log, I could see the download is happening only through the relays
At 08:24:41 -0500 -
ActionLogMessage: (action:(ActionID)) Action signature verified for Downloads
At 08:29:27 -0500 -
DownloadPing command received (ID=(ActionID))
At 08:29:41 -0500 -
DownloadsAvailable: checking for 'http://relayIP:52311/bfmirror/downloads/(ActionID)/0’
DownloadsAvailable: true (action id (ActionID))
DownloadsAvailable: checking for 'http://relayIP:52311/bfmirror/downloads/(ActionID)/0’
DownloadsAvailable: true (action id (ActionID))
ActionLogMessage: (action:(ActionID)) Non-Distributed - DownloadsAvailable
ActionLogMessage: (action:(ActionID)) Submitting download request
- All those 3 clients do not have command polling enabled.
I am not sure where this is going wrong? I assume it could be because of the UDP response being timed-out which is being seen in the P2P debug log. And to check if UDP is working between the clients, I have installed relay and could see other 2 clients are able to receive UDP message through sent refresh, actions are being received without command polling enabled. Then made sure UDP is fine between the clients and un-installed relay on one of the client.
Can anyone please help me with suggestions? Thanks in Advance.