Ad Widget

Collapse

Bugs: Win32 Agent Crash

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • rvillaca
    Member
    • Sep 2005
    • 33

    #1

    Bugs: Win32 Agent Crash

    Hi all,

    I am experiencing the following issue, one of my sql servers have some custom parameters that check for application erros inside the database.

    Every day we run some jobs on the databases at 11:00 PM and slow down the execution. The agent timeout is set to 30.

    Every time that the agent got a timeout, it crashes and stop the service.

    As a workarround, i have setup windows to restart the service if it crashes, but last night the agent cannot bind the port. I stopped the zabbix process, but the port still in use. I have tried to use tcpview (sysinternals) and have found that the port is open, but dont have any proccess associated. I try to close the connection, but it doesn't work.

    I have to change the agent port to make the agent work again (i have to monitor that server anyway).

    So, we have two issues: The agent cannot handle a userparameter timeout (its happening every day) and it leave the listening socket when the proccess stoped (that ocurred only yesterday).

    Thanks for making the best open nms,

    Rodrigo
  • qix
    Senior Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • Oct 2006
    • 423

    #2
    I am experiencing the same problem only on a stable version of the Zabbix agent, I think (Zabbix Win32 Agent Version 1.1 Build of Jun 5 2006.)

    Somehow the agent stopped reacting (a collegue of mine did some work on a proccess that zabbix was monitoring via a script).
    I stopped the agent, but now when starting it returns this error:

    [23-Oct-2006 13:45:45] Unable to bind socket: Only one usage of each socket address (protocol/network address/port) is normally permitted.

    Also, the temp files in the windows temp directory are locked.
    ZabbixW32.exe proccess does no longer shows in the tasklist, 'netstat -a' does however show that the port is listening.

    Again, a reconfiguration of the listening port worked to get the agent started again.

    I think i could probably reboot the server and the problem will be gone, but this is a live productiuon environment in which we want as litle downtime as possible (don't we all )

    Does anybody have an idea how I can free up the listening port and stop the agent from crashing?

    thanx in advance!
    Last edited by qix; 23-10-2006, 14:51.
    With kind regards,

    Raymond

    Comment

    • qix
      Senior Member
      Zabbix Certified SpecialistZabbix Certified Professional
      • Oct 2006
      • 423

      #3
      Ok, we rebooted the server and all is well.
      Still would like to know how such a thing could happen...


      Anyway, since I'm not using a beta/alpha agent I opened up this thread:

      Last edited by qix; 23-10-2006, 17:50.
      With kind regards,

      Raymond

      Comment

      Working...