On 23.05.16 20:13 Cos Bug wrote: > #Run backup job > 00 20 * * * (pushd $ANSIBLE_DIR && ansible-playbook backup.yml -e > @server.json > -vv) >/dev/null 2>&1
> Could you please advise how to troubleshoot such type of issues? I'd like to know why you need ansible for this, running the actual backup script from cron seems like a more direct way. But you may have your reasons, so to debug this, I would get rid of the ">/dev/null 2>&1" in your cron job to get more output. So you would get an e-mail for each running job. Also, I would include some connectivity tests in the playbook, just to make sure the network is not the problem. Also, a cron job just pinging the target before the actual job might be an idea. Johannes -- 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/57440753.4030905%40ojkastl.de. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
