Hi guys, im currently having trouble with installing a zabbix agent using the win_package module. Im trying to install it in a windows server and i get problems while doing it. The problem is once i run the playbook it freezes and won’t install anything. I’ll provide you the code im using . I want to install it in quiet mode, and pass some arguments that the msi installer needs in order to install correctly.
As long as we’re grasping at straws, let’s speculate that the reason they say not to use the /log option is so that the win_package module can monitor the output. If that’s true (and we’re already on thin ice, but let’s keep going), and if the Zabbix-specific options LOGTYPE=file and LOGFILE="C:/Zabbix/za.log" combine to have the same debilitating affect on the win_package module that /log has, then perhaps win_package is hanging because it’s waiting for output on whatever the Windows equivalent of stdout is but that’s instead being sent to C:\Zabbix\za.log, so it sits around apparently hanging until timeouts expire or an admin pulls the plug.
Try it without /qn, LOGTYPE, and LOGFILE. And if that still doesn’t work, I’m truly out of ideas.
I could resolve it, it was a problem with the syntax of the installer. I tried installing manually on Windows and it threw me the typical error window, and when i fixed it, it ended up working on ansible. Thanks !
The main problem was not using the “” when giving the additional parameters.
So instead of how it was written up on the post, it should be
KEY=“value”
I also removed some Properties Keys that weren’t useful while installing them, such as Logfile or HOSTNAME.
and at last, i added a >- next to the arguments: (i took this from the ansible doc)
You can also check if it works just by trying to install it by command line and passing the parameters. And as you said, i didn’t need to give the /qn parameter.
