Ad Widget

Collapse

Agent2 on Windows server - unsupported windows service command recieved

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Gert Vanderstukken
    Junior Member
    • Mar 2011
    • 5

    #1

    Agent2 on Windows server - unsupported windows service command recieved

    Hello all,

    I have been using Zabbix in the past (version 1.6, 1.8, ... 2.4 era ) and now picking up again.

    We installed zabbix 5.2 and I have to say: I am impresses with the improvements. I really like my comeback...


    Anyway, I tried using the agent2 on Windows systems (Microsoft Windows Server 2019 Standard) and ran into the following issue.
    The logfile is filling up with messages like:

    2020/12/08 21:19:19.210982 unsupported windows service command recieved
    This is even after installing an agent on a server that does not yet have a host defined in zabbix => no items.

    Is this a known issue? Or is nobody using agent2 on Windows?


  • GRIFFCOMM
    Junior Member
    • Jan 2021
    • 11

    #2
    We have noticed the same thing, the older (non version 2 agent) appears to work ok !

    Comment

    • dexsternn
      Junior Member
      • Jan 2021
      • 1

      #3
      Also have same problem on WinServ2019 with Agent2

      Comment

      • Ladislav Kotal
        Junior Member
        • Jan 2021
        • 1

        #4
        I face a same issue on Win Server 2019 and Zabbix Agent 2. Did you find any solution?

        Comment

        • cbass
          Junior Member
          • Nov 2020
          • 16

          #5
          I also have this problem. Agent version is 5.0.5. I will update the agent to 5.0.7 to see if that helps and report back.

          Comment

          • GRIFFCOMM
            Junior Member
            • Jan 2021
            • 11

            #6
            I am sure to fix this we remove and re-loaded the client. However we only installed the agent not the proxy, ours are signing in to a Zabbox proxy, so both the server and proxy addresses are the same, and its set to active, then the errors stopped

            Comment

            • cbass
              Junior Member
              • Nov 2020
              • 16

              #7
              I thought upgrading to agent 5.0.7 may have fixed this problem but it appears it has not. I also see in my agent log file "cannot process incoming connections: EOF". Not sure if this is related or not. Also, the agent that is reporting these errors is not able to startup when the host has boot up. I have to manually start the service which seems to work but obviously isn't correct. Anyone else see the "cannot process incoming connections: EOF" errors before?

              Comment

              • mattk0
                Junior Member
                • Feb 2021
                • 3

                #8
                FYI: We are having the same issue with Zabbix2 agent and thinking of moving back to zabbix V1 agent. Not sure if it's related but also have multiple agent Windows Services stopping periodicially

                Comment

                • padl3xx
                  Junior Member
                  • Mar 2021
                  • 7

                  #9
                  Same issues. Server 5.0.9, agent 5.0.10.

                  Comment

                  • gofree
                    Senior Member
                    Zabbix Certified SpecialistZabbix Certified Professional
                    • Dec 2017
                    • 400

                    #10
                    any chance this might have helped

                    Comment

                    Working...