no_log / no_target_syslog ??

355 views
Skip to first unread message

Hajo Kliemeck

unread,
Jan 29, 2016, 5:56:59 AM1/29/16
to Ansible Development
Hey,

on the documentation its said: "no_target_syslog - prevents logging of tasks, but only on the targets, data is still logged on the master/controller"

whats the meaning of log on "master/controller". syslog, stdout of ansible or both?

thanks!


Brian Coca

unread,
Jan 29, 2016, 9:16:13 AM1/29/16
to Hajo Kliemeck, Ansible Development
I'm not sure what the question is, but hope this clarifies it:

no_log prevents loggin AND output on both target and
'master/controller' (no_log implies no_target_syslog).

no_target_syslog only prevents logging on the target (its a subset of no_log).


--
Brian Coca

Hajo Kliemeck

unread,
Jan 29, 2016, 9:53:11 AM1/29/16
to Ansible Development, hajo.k...@googlemail.com
i will clarify:

without no_log / no_target_syslog it seems that output is displayed on master/controller (console) and logging (syslog) is done on target. NO logging (syslog) is done on master/controller

is this correct?

Brian Coca

unread,
Jan 29, 2016, 9:57:58 AM1/29/16
to Hajo Kliemeck, Ansible Development
depends on your setup/configuration, but that would be the 'default'


--
Brian Coca

Hajo Kliemeck

unread,
Jan 29, 2016, 10:28:33 AM1/29/16
to Ansible Development, hajo.k...@googlemail.com
what do you mean by default?

one case would be master/controller == target but i can not find any other case. any ideas?

Brian Coca

unread,
Jan 29, 2016, 10:40:55 AM1/29/16
to Hajo Kliemeck, Ansible Development
default, as settings out of the box? not sure what you are looking for here.



--
Brian Coca
Message has been deleted

Hajo Kliemeck

unread,
Jan 29, 2016, 11:11:12 AM1/29/16
to Ansible Development
I do not want to log ANYTHING to syslog, regardless of type (master or target), but for debugging purposes i want to display the output of ansible-playbook on master for console executions (e.g. error on task XY with params YY on role ZZ)

Hajo Kliemeck

unread,
Feb 2, 2016, 3:15:12 AM2/2/16
to Ansible Development
thought about it: something like a no_syslog option

Hajo Kliemeck

unread,
Feb 8, 2016, 7:05:52 AM2/8/16
to Ansible Development
push
Reply all
Reply to author
Forward
0 new messages