HummerBoy wrote:
> 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.
> 

One thing that could be worth a try is putting:

Code:
# These ensure that TIME_WAIT ports either get reused or closed fast.
net.ipv4.tcp_fin_timeout = 1
net.ipv4.tcp_tw_recycle = 1


Into the /etc/sysctl.conf file of your zenoss server and reload the sysctl 
configuration with 'sysctl -p'. 
This will tell your Zenoss server to close TCP connections faster and probably 
solves your problem.




-------------------- m2f --------------------

Read this topic online here:
http://forums.zenoss.com/viewtopic.php?p=36933#36933

-------------------- m2f --------------------



_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to