Ad Widget

Collapse

TIME_WAIT and zabbix_agentd - dozens of sockets always open

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • pyite
    Junior Member
    • Aug 2007
    • 3

    #1

    TIME_WAIT and zabbix_agentd - dozens of sockets always open

    This is a serious problem for me, there are a ton of sockets being left open.

    Is there any way for zabbix_agent and zabbix_server to keep one socket open and re-use it instead of re-connecting all of the time?
  • swaterhouse
    Senior Member
    • Apr 2006
    • 268

    #2
    please do a search this has been discussed many times before.

    Comment

    • pyite
      Junior Member
      • Aug 2007
      • 3

      #3
      Thank you for your kind reply.

      I did about an hour's worth of searches, and none ended up with a proper solution; there was an option to set NoTimeWait=1, but that was considered "experimental" and "dangerous". Is there a better answer, or is NoTimeWait the way to go?

      Comment

      • Alexei
        Founder, CEO
        Zabbix Certified Trainer
        Zabbix Certified SpecialistZabbix Certified Professional
        • Sep 2004
        • 5654

        #4
        Originally posted by pyite
        This is a serious problem for me, there are a ton of sockets being left open.
        What exactly is the problem? Does the ton of open sockets hurt your system or something? This is absolutely normal situation for busy WEB, FTP, whatever servers including ZABBIX.
        Last edited by Alexei; 23-08-2007, 21:07.
        Alexei Vladishev
        Creator of Zabbix, Product manager
        New York | Tokyo | Riga
        My Twitter

        Comment

        • pyite
          Junior Member
          • Aug 2007
          • 3

          #5
          Thanks again for the reply.

          Perhaps I will just get used to it. I was having performance problems and was looking at a lot of netstats.

          I am using OpenVZ with about 15 VM's on this box, each one with dozens of sockets open from zabbix. The problem turned out to be on the browser side, though, actually it ended up being a DSL modem that was randomly shutting down sockets. Quite strange.

          Comment

          Working...