It seems, unfortunately, the process of monitoring the port we need open is actually killing the service that uses it. My zenoss server is polling a specific port on our OES boxes and keeping the connection open. Next time it polls it opens a new one. Eventually (about a day) these unclosed connections are building up and killing the httpstkd and it stops responding. See the small sample below. Everything I read says that the application that opened the port , this case Zenoss, is the problem and needs to close it correctly. At the moment the only solution I have found is to restart httpstkd every night on every server. Not really the solution I want. Anyone have an idea how to get Zenoss to play nicely?
Code: httpstkd 25015 root 1003u IPv4 44732314 TCP 10.2.4.50:8009->10.251.1.114:35418 (CLOSE_WAIT) httpstkd 25015 root 1004u IPv4 44732790 TCP 10.2.4.51:8009->10.251.1.114:59063 (CLOSE_WAIT) httpstkd 25015 root 1005u IPv4 44732795 TCP 10.2.4.50:8009->10.251.1.114:35764 (CLOSE_WAIT) httpstkd 25015 root 1006u IPv4 44733342 TCP 10.2.4.51:8009->10.251.1.114:59409 (CLOSE_WAIT) httpstkd 25015 root 1007u IPv4 44733347 TCP 10.2.4.50:8009->10.251.1.114:36112 (CLOSE_WAIT) -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=36931#36931 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
