Announcements
This site is in read only until July 22 as we migrate to a new platform; refer to this community post for more details.
Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

Message-processor/management server has many connections in FIN_WAIT2 state hanging and impacting the health of the system.

Case: OPDK: 4.15.01.00 on RHEL 6.6

A situation where management-server is opening TCP connections to message-processor port xxxx. As a result the message-processor server has about 2400 connections in FIN_WAIT2.

1. FIN_WAIT2 connections are released only if we restart message-processor, they do not timeout.

2. Timeout setting are:

cat /proc/sys/net/ipv4/tcp_fin_timeout

60

3. Connectivity is fine between the 2 machines.

4. Curl call from the management server to MP gives a 200 OK.

curl -v http://<MP>:8082/v1/runtime/organizations

0 1 386
1 REPLY 1