Ad Widget

Collapse

system.run @ Windows [Check access restrictions in Zabbix agent configuration]

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • doronyaary
    Junior Member
    • Jul 2020
    • 4

    #1

    system.run @ Windows [Check access restrictions in Zabbix agent configuration]

    Hello.
    I have installed zabbix agent 5 on windows (the zabbix server is on CentOS). every time I am trying to run a command I am getting the following error:

    zabbix_get: Check access restrictions in Zabbix agent configuration

    This is my configuration file:

    LogFile=C:\Zabbix\zabbix_agentd.log
    DenyKey=system.cpu.intr
    AllowKey=system.run[*]
    EnableRemoteCommands=1
    LogRemoteCommands=1
    Server=MY_ZABBIX_SERVER_IP
    ListenPort=10050
    ListenIP=0.0.0.0
    StartAgents=2
    ServerActive=MY_ZABBIX_SERVER_IP
    Hostname=MY_WINDOWS_SERVER
    Timeout=30
    UnsafeUserParameters=1


    It is important to mention that the zabbix agent is running with administrative user under windows.

    What have I done wrong?

    Many thanks for your help!
  • tim.mooney
    Senior Member
    • Dec 2012
    • 1427

    #2
    I was going to answer that it was because of how Remote Commands changed at 5.x, but I see you've already adjusted DenyKey, so you know about the changes.

    Does it make a difference if you completely comment out DenyKey (and then restart the agent, obviously), just for testing?

    EnableRemoteCommands is deprecated, so you apparently don't need it at all, once you've set AllowKey. Does it make a difference if you comment out EnableRemoteCommands=1 (and restart the agentd)? I'm just wondering if there's some weird interplay between old and new configuration that is causing some problem for you.

    If you bump up the log level of the agent to a debug level, does anything appear in the logs after you attempt a system.run from your server?

    Comment

    • doronyaary
      Junior Member
      • Jul 2020
      • 4

      #3
      Hi Tim,

      First of all, many thanks for your reply. Eventually (Im new to Zabbix so I dont know if this is a documented bug or not), I installed Zabbix agent 5.0.2 instead of 5.0.1 - that solved the entire issue.
      If we are already talking :-) Perhaps you can point me to the documentation area of how can I make a problem raise its severity if it is recurring more than 3 times?

      Many thanks!

      Doron.

      Comment

      Working...