getsockname returns sockaddr full of NULL bytes

Solution In Progress - Updated -

Issue

  • On RHEL 7.2 acting as an Apache Traffic Server transparent proxy handling 22000 connections per second with 3.2 million total connections, occasionally a getsockname() succeedsm but the sockaddr data structure returned is completely filled with NULLs.
  • This does not occur on ELRepo kernel 4.3.3-1.

Environment

  • Red Hat Enterprise Linux 7.2
  • kernel-3.10.0-327.el7.x86_64
  • Apache Traffic Server as fully transparent caching proxy
  • getsockname() system call

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content