merge 377038 374758 thanks hi Robert,
On Thu, Jul 06, 2006 at 11:57:00AM +0200, Robert Millan [ackstorm] wrote: > After stopping zabbix, there's a race condition with the old process > terminating > its children, which still are binding ports, and new process starting that > attempt to claim the same port. yes, thats a problem in zabbix-agent and zabbix-server. Both agent and server do not close their open file descriptors on termination, which leaves the sockets in the TIME_WAIT state until the kernel gets rid of them (usually after 60 seconds). This has been fixed for the server already (re-uses already open sockets on startup), but not for the agent. Upstream is aware of this problem and i hope its fixed for the agent soon too. I dont think a work around within the init script's is best practise (at least not in this case). Lets wait for the next release. I may add the patch with one of the next uploads. http://www.zabbix.com/forum/showthread.php?t=3384 bye, - michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
