Ad Widget

Collapse

Service apper starting in win agent, but never works

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • CEGR
    Junior Member
    • Feb 2007
    • 4

    #1

    Service apper starting in win agent, but never works

    We are experiencing a problem, when we put the zabbix agent in ours Windows servers, the message, STARTING appears but it never works.

    Someone could help me?

    Thanks!
    Last edited by CEGR; 15-02-2007, 20:43.
  • CEGR
    Junior Member
    • Feb 2007
    • 4

    #2
    Já sei como resolver. Fábio

    Comment

    • Villain
      Member
      • Aug 2006
      • 84

      #3
      I am now having this problem on one of our servers. We recently added an Exchange server to our network, and when I install the service, everything is fine. When I go to start it, I am told that it is starting, then it comes back with an error stating that the service failed to respond to the start request in a timely manner.

      I have copied over a fresh ZabbixW32 file, and still getting the same result.

      Any ideas?

      Comment

      • Villain
        Member
        • Aug 2006
        • 84

        #4
        Just a bump, but more info

        I'm still not making progress with this issue. I have completely removed the service, re-write the zabbix_agentd.conf file from scratch, yet the service still will not start. It sits at 'Starting' and goes no further, then I get an error stating that it is not able to start in a timely manner.

        Is there a reason that this happens to some computers, but not others. Since this issue occured, I have not had problems installing the service into another Win2003 Server, nor a problem installing it into several WinXP workstations, as well.

        Comment

        • Villain
          Member
          • Aug 2006
          • 84

          #5
          I think I finally found the culprit. I edited the conf file to use a real path to the log file, and we'll see if that fixes things. Since this is on our Exchange server, I can't test it until after hours. So, we'll see how this comes out tomorrow.

          Comment

          • Ismael Medina
            Junior Member
            • Mar 2007
            • 15

            #6
            You are right

            I have the same problem the last week, if you use a bad log path the service appears as starting, i'm killed the process and the log file wasn't be created, reviewing the .conf file the log path was wrong.

            I fix it and the service starts successfully.

            Good Luck.

            Comment

            Working...