Hi

For the handler you have to explicitly state to use the "service" instead 
of "systemctl" command. For me it worked with a notify and a handler 
definition like so:

- name: restart auditd
  systemd:
    name: auditd
    state: restarted
    use: service

With that handler you can use "notify: restart auditd" in your task and 
that should work. I'm working with RHEL 7 but that should not be different 
from centOS 7 in that regard.

Best,
Cyril


On Monday, 17 February 2020 15:54:00 UTC+1, Bala Mutyam wrote:
>
> Service module is also failing with the same error.
>
> fatal: [192.168.69.33]: FAILED! => {"changed": false, "msg": "Unable to 
> restart service auditd: Failed to restart auditd.service: Operation 
> refused, unit auditd.service may be requested by dependency only (it is 
> configured to refuse manual start/stop).\nSee system logs and 'systemctl 
> status auditd.service' for details.\n"}
>
>
> On Monday, February 17, 2020 at 1:42:37 PM UTC, Stefan Hornburg (Racke) 
> wrote:
>>
>> On 2/17/20 2:36 PM, Bala Mutyam wrote: 
>> > Hi all, 
>> > 
>> > Anisble Version: ansible 2.7.7 
>> > 
>> > 
>> > I'm  configuring auditd on centos7 but the auditd service is failing to 
>> restart. 
>> > 
>> > Handler: 
>> > 
>> > - name: centos7 restart auditd 
>> >   become: yes 
>> >   command: service auditd restart 
>> > 
>> > Error: 
>> > 
>> > FAILED! => {"changed": false, "msg": "Unable to restart service auditd: 
>> Failed to restart auditd.service: Operation 
>> > refused, unit auditd.service may be requested by dependency only (it is 
>> configured to refuse manual start/stop).\nSee 
>> > system logs and 'systemctl status auditd.service' for details.\n"} 
>> > 
>> > I can restart the service via commandline on the host using "service 
>> auditd restart" 
>> > 
>> > I'm running playbook as root user 
>> > 
>> > Could someone help me please? 
>>
>> It might not solve your problem, but you should certainly use the 
>> "service" module instead of "command". If it still 
>> fails, please provide corresponding log messages as instructed in the 
>> error message. 
>>
>> Regards 
>>         Racke 
>>
>> > 
>> > -- 
>> > 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] <mailto:
>> [email protected]>. 
>> > To view this discussion on the web visit 
>> > 
>> https://groups.google.com/d/msgid/ansible-project/417abda6-bbfd-4af8-9eed-8ee023e5eb73%40googlegroups.com
>>  
>> > <
>> https://groups.google.com/d/msgid/ansible-project/417abda6-bbfd-4af8-9eed-8ee023e5eb73%40googlegroups.com?utm_medium=email&utm_source=footer>.
>>  
>>
>>
>>
>> -- 
>> Ecommerce and Linux consulting + Perl and web application programming. 
>> Debian and Sympa administration. Provisioning with Ansible. 
>>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/9c7710cf-fa92-4434-95fd-eddd8bb8b4a7%40googlegroups.com.

Reply via email to