A node drops off a TIBCO Data Virtualization Cluster due to an error "no Inet4Address associated with interface"
Article ID: KB0074488
Updated On:
| Products | Versions |
|---|---|
| TIBCO Data Virtualization | 8.0.x and higher. |
Description
A node drops off a TIBCO Data Virtualization Cluster. The cs_server.log contains the following error corresponding to the time that the node was dropped.
-----------------------------------
WARN [Reconnector] 2020-10-06 15:12:45.034 -0400 TCP - failed to join /224.0.75.75:7500 on net4: java.net.SocketException: Unrecognized Windows Sockets error: 0: no Inet4Address associated with interface
-----------------------------------
-----------------------------------
WARN [Reconnector] 2020-10-06 15:12:45.034 -0400 TCP - failed to join /224.0.75.75:7500 on net4: java.net.SocketException: Unrecognized Windows Sockets error: 0: no Inet4Address associated with interface
-----------------------------------
Issue/Introduction
A node drops off a TIBCO Data Virtualization Cluster due to an error "no Inet4Address associated with interface"
Resolution
TDV uses a library called JGroups for clustering. JGroups sends a query to the OS, asking the OS for:
(1) The IP address of the network interface.
(2) Multicast groups for the network interface.
The OS in turn gets this information from the network interface. In this case, the query failed to return the IP address (and/or the multicast groups) as expected, resulting in an error " no Inet4Address associated with interface".
The error is typically caused by a temporary network issue. Check whether the network interface has an IP address and multicast groups as follows:
On Windows:
(1) Run ipconfig /all. Inspect the output to verify that there is an IPv4 address enabled.
Example
(2) Run netsh interface ip show joins. In the output, the rows listed under the interface are the multicast groups.
Example
If there are no rows listed under the network interface, it means that multicast is not enabled, and so the network administrator will need to enable it.
On Linux:
(1) Run ifconfig -a. Inspect the output to verify that there is an IPv4 address enabled.
(2) Run netstat -g. Inspect the output to see whether there are multicast groups associated with the interface.
If the above checks indicate that the network interface does have:
In that case, to resolve the issue first try clicking on the Re-group Cluster button in the Web Manager.
If this does not resolve the issue, it may be that the network interface details that JGroups has stored in memory need to be cleared, and so restart the TDV server. The restart will ensure that all in-memory caches are emptied and reinitialized.
(1) The IP address of the network interface.
(2) Multicast groups for the network interface.
The OS in turn gets this information from the network interface. In this case, the query failed to return the IP address (and/or the multicast groups) as expected, resulting in an error " no Inet4Address associated with interface".
The error is typically caused by a temporary network issue. Check whether the network interface has an IP address and multicast groups as follows:
On Windows:
(1) Run ipconfig /all. Inspect the output to verify that there is an IPv4 address enabled.
Example
(2) Run netsh interface ip show joins. In the output, the rows listed under the interface are the multicast groups.
Example
If there are no rows listed under the network interface, it means that multicast is not enabled, and so the network administrator will need to enable it.
On Linux:
(1) Run ifconfig -a. Inspect the output to verify that there is an IPv4 address enabled.
(2) Run netstat -g. Inspect the output to see whether there are multicast groups associated with the interface.
If the above checks indicate that the network interface does have:
- an IP address
- multicast groups
In that case, to resolve the issue first try clicking on the Re-group Cluster button in the Web Manager.
If this does not resolve the issue, it may be that the network interface details that JGroups has stored in memory need to be cleared, and so restart the TDV server. The restart will ensure that all in-memory caches are emptied and reinitialized.
Feedback
Yes
No
Powered by
