Possible semaphore leak under Solaris 10, Agent 4.2.1

XMLWordPrintable

    • Type: Incident report
    • Resolution: Duplicate
    • Priority: Major
    • None
    • Affects Version/s: 4.2.1
    • Component/s: Agent (G)
    • None
    • Environment:
      Solaris 10 8/11 X86

      Steps to reproduce:

      1. Build Zabbix Agent for Solaris 10
      2. Run agent unconfigured/configured - doesn't seem to make a difference whether its actually doing any real work or not.
      3. Run ipcs -s | grep zabbix periodically to watch the semaphore count grow until it maxes out
      4. Stop the agent
      5. Run ipcs -s | grep zabbix to check the count and notice only 1 was removed after exiting
      6. Run ipcrm to clean up semaphores

      Result:
      See attached zabbix agent log file, alongside a log of output from a loop that's counting the number of Zabbix semaphores:

      for i in `seq 1 1000000`; do date >> /oanda/var/tmp/semaphore.log; ipcs -s | grep zabbix | wc -l >> /oanda/var/tmp/semaphore.log; sleep 1; done

       

      Expected:
      Semaphores were stable under 4.0.5, so I'm unclear when this changed exactly.

        1. semaphore.log.gz
          231 kB
          David Angelovich
        2. zabbix_agentd.log.gz
          2.83 MB
          David Angelovich

            Assignee:
            Zabbix Support Team
            Reporter:
            David Angelovich
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: