Hello,
I’m running ansible 2.1.0.0 and when running a playbook against a target system(machine B), there are no messages logged to syslog on the target machine(machine b) during the run. Are there settings necessary to get the modules and options logged to syslog on the target system(machine b)?
If I add log_path=/tmp/ansible.log I get a list of modules and options logged to that file on the manager system(machine A), but still nothing on the target machine (machine b).
Thanks,
Ed
My current setup looks like this:
Machine A - Manager system. OS is debian with Ansible 2.1 installed from packages. This is where I’m running Ansible
Machine B - Target system. OS is RedHat 7.
Anyone know why this change was made? The commit message doesn’t really make sense to me.
Or if there’s a way to now set the verbosity to 3 via the config file?
Or a way to set the verbosity to 3 and not show the full ssh commands on the manager system?
I ask because we’ve got a requirement that any automated configuration management system do at least basic logging on the target system so that changes can be referenced locally.
The -v option ONLY affects the output you see on the controller. You can set debug in ansible.cfg or ANSIBLE_DEBUG=1 in your environment before running ansible to force some logging on the module side. This mostly affects any commands you shell out for, be mindful that not all modules shell out nor does this account for every action in those that do.