Error setsockopt(TCP_KEEPCNT): failed: invalid argument.

Products

• VMware Tanzu Greenplum / Gemfire
• VMware Tanzu Greenplum
• VMware Tanzu Data Suite
• VMware Tanzu Data Suite

Issue/Introduction

Greenplum logs files (coordinator and/or segment logs) report messages like:

2025-05-28 00:00:00.096588 +03,,,p1683996,th1343197952,,,,0,,,seg1,,,,,"LOG","00000","setsockopt(TCP_KEEPCNT) failed: Invalid argument",,,,,,,0,,"pqcomm.c",2070,

Cause

The messages are due to Greenplum trying to set the socket option TCP_KEEPCNT on the socket connection to the coordinator or segment.

This is controlled by GUC tcp_keepalives_count. If the host OS does not support the option it will report the error message.

Resolution

Reset the GUC tcp_keepalives_count to the default of 0.

gpconfig -r tcp_keepalives_count

A database restart is needed for the change to take effect.

Additional Information

Other GUCs associated with keepalive:

• tcp_keepalives_idle
• tcp_keepalives_interval

Note: all require a database restart for the changes to take effect