Hi there, a) I have the same behavior on both versions.
b) The status command works, the restart command doesn't. If I run 'service auditd restart' it works as expected. c) I did another ugly hack that works, for now. I got a handler that looks like this. It fires a warning that I should use the 'service' command instead though. ;) <- Cut -> - name: reload_auditd_C7 command: service auditd restart <- Cut -> It almost looks like using the 'service' command in Ansible against Centos7 actually calls the 'systemctl' functionality in the other end? Cheers, Mike On Thu, Apr 13, 2017 at 8:12 AM Phonthip Namkaew <[email protected]> wrote: > a) > Which Ansible version is in use? Same behavior with 2.2.2 or 2.3.0? > b) > Can you run successfully the following on the command line ( centos 7 )? > systemctl status auditd.service > systemctl restart auditd.service > > Does the Ansible user have the rights to restart auditd.service ? > > c) > Ugli hack as a last resort, use Ansible Modul command instead of > Ansible module service for centos 7 only. > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/b5c2a895-4e00-4ec5-bfbe-45d163e172a7%40googlegroups.com > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAMuthMeXu-aFaUPpO492URcKb6XBo5yS79-t_dRY-6hCHn9bWg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
