Hello,
we have a really big problem with the Zabbix agent configuration file.
We are using templates to monitor DHCP, SQL and IIS and each of them requires PowerShell scripts to be run on the host and also userparameters to be configured.
We added 3 or 4 lines to our common config file which is used on all Windows Servers - those parameters include additional configuration directory to be read by Zabbix agent, allow to use user unsafe parameters and change timeout to 30 seconds.
After we send this config file to appropriate hosts with PowerShell and restart the agent - this works file some time but after the file is restored to the previous version without any information in the agent log.
If we change the config file manually (not with PowerShell) it is exactly the same.
We tried even to remove agent service and install it again with new config - same situation.
How this is possible that agent config file is being restored to previous version?
In the sever log we see following entries (examples):
124422:20190730:150602.854 item "hostname:dhcp[ScopeinUse,A.B.C.D]" became supported
124419:20190730:154530.094 item "hostname:dhcp[ScopeinUse,A.B.C.D]" became not supported: Unsupported item key.
I replaced real hostnames and scope IPs with placeholders.
Did anybody encourter such situation?
we have a really big problem with the Zabbix agent configuration file.
We are using templates to monitor DHCP, SQL and IIS and each of them requires PowerShell scripts to be run on the host and also userparameters to be configured.
We added 3 or 4 lines to our common config file which is used on all Windows Servers - those parameters include additional configuration directory to be read by Zabbix agent, allow to use user unsafe parameters and change timeout to 30 seconds.
After we send this config file to appropriate hosts with PowerShell and restart the agent - this works file some time but after the file is restored to the previous version without any information in the agent log.
If we change the config file manually (not with PowerShell) it is exactly the same.
We tried even to remove agent service and install it again with new config - same situation.
How this is possible that agent config file is being restored to previous version?
In the sever log we see following entries (examples):
124422:20190730:150602.854 item "hostname:dhcp[ScopeinUse,A.B.C.D]" became supported
124419:20190730:154530.094 item "hostname:dhcp[ScopeinUse,A.B.C.D]" became not supported: Unsupported item key.
I replaced real hostnames and scope IPs with placeholders.
Did anybody encourter such situation?
Please provide us any hints because right now Zabbix is totally unusable because of this.
Comment