vic

vic copied to clipboard

While investigating a 100% cpu issue with vicadmin I'm noticing too many threads with open net connections, and netstat shows that we have various connections persisting to the pprof servers.

It's possible that this is intentional, but I'd guess not given the number of threads in the vicadmin pprof trace in the attached bundle. logs.zip

Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 127.0.0.1:8080          0.0.0.0:*               LISTEN
tcp        0      0 10.118.66.172:8080      0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN
tcp        0      0 127.0.0.1:6061          0.0.0.0:*               LISTEN
tcp        0      0 127.0.0.1:6062          0.0.0.0:*               LISTEN
tcp        0      0 127.0.0.1:6063          0.0.0.0:*               LISTEN
tcp        0      0 127.0.0.1:6061          10.118.66.172:50708     ESTABLISHED
tcp        0      0 127.0.0.1:6062          10.118.66.172:36204     ESTABLISHED
tcp        0      0 127.0.0.1:8080          10.118.66.172:56040     ESTABLISHED
tcp        0      0 127.0.0.1:56040         127.0.0.1:8080          ESTABLISHED
tcp        0      0 127.0.0.1:8080          10.118.66.172:55640     ESTABLISHED
tcp        0      0 10.118.66.172:8080      10.118.67.124:27078     ESTABLISHED
tcp        0      0 127.0.0.1:6063          10.118.66.172:44302     ESTABLISHED
tcp        0      0 10.118.66.172:37710     10.118.67.35:80         ESTABLISHED
tcp        0    320 10.118.66.172:22        10.16.198.211:59716     ESTABLISHED
tcp        0      0 127.0.0.1:36204         127.0.0.1:6062          ESTABLISHED
tcp        0      0 127.0.0.1:44302         127.0.0.1:6063          ESTABLISHED
tcp        0      0 127.0.0.1:55640         127.0.0.1:8080          ESTABLISHED
tcp        0      0 10.118.66.172:37704     10.118.67.35:80         ESTABLISHED
tcp        0      0 10.118.66.172:8080      10.118.67.121:20284     ESTABLISHED
tcp        0      0 10.118.66.172:37716     10.118.67.35:80         ESTABLISHED
tcp        0      0 127.0.0.1:50708         127.0.0.1:6061          ESTABLISHED
tcp6       0      0 :::53                   :::*                    LISTEN
tcp6       0      0 :::22                   :::*                    LISTEN
tcp6       0      0 :::2375                 :::*                    LISTEN
tcp6       0      0 :::2378                 :::*                    LISTEN
tcp6       0      0 10.118.66.172:2378      10.118.69.222:51102     CLOSE_WAIT
tcp6       0      0 10.118.66.172:2378      10.118.69.222:51830     ESTABLISHED
udp6       0      0 :::53                   :::*

@sgairo Hey Sophie, this is festering. Can you look into this and either close it as fixed or provide a sentence on what we should do about it. Any kind of resource leak is potentially bad.

@corrieb sure thing!