Thank you for the reply.
I ended up removing the TIMEOUTs from the vendor’s script and replaced them
with pings.
> On Apr 19, 2023, at 2:10 PM, jbor...@gmail.com wrote:
>
> Try just doing - win_command: '{{ install_app_download_dir
> }}\Prerequisites\install_rabbitmq.bat'. You could also pre
Try just doing - win_command: '{{ install_app_download_dir
}}\Prerequisites\install_rabbitmq.bat'. You could also prefix that command
with cmd.exe /c path\to\install.bat and see if it helps. Another option is
to use '- win_shell: exit (Start-Process -FilePath ... -Wait
-PassThru).ExitCode' to s
Thanks, I will try that.
On Wednesday, April 19, 2023 at 1:19:14 PM UTC-4 Will McDonald wrote:
> It works as expected for me on a test Fedora machine.
>
> As a test user, create a debug playbook and test it runs.
>
> [test-user@fedora ~]$ id
> uid=1001(test-user) gid=1001(test-user) groups=1001(t
It works as expected for me on a test Fedora machine.
As a test user, create a debug playbook and test it runs.
[test-user@fedora ~]$ id
uid=1001(test-user) gid=1001(test-user) groups=1001(test-user)
context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
[test-user@fedora ~]$ cat debug.yam
Yes, there are copy/paste errors as I am transcribing and scrubbing info
from a high-side environment.
On Wednesday, April 19, 2023 at 12:21:47 PM UTC-4 Dick Visser wrote:
> Also the file name extensions are different (yml vs yaml). Are we looking
> at some copy paste errors?
>
> On Wed, 19 Ap
There's a discrepancy between your job as defined in your playbook and your
output as listed from crontab -l. I suspect that's just transcription but
worth double-checking? (Walter and Dick have also spotted that.)
I'd also check that the ec2-user which is who you're creating the crontab
as has ap
Also the file name extensions are different (yml vs yaml). Are we looking
at some copy paste errors?
On Wed, 19 Apr 2023 at 18:18, 'Rowe, Walter P. (Fed)' via Ansible Project <
ansible-project@googlegroups.com> wrote:
> job: "/home/jwelby/ansible/sub-playbooks/ansible-playbook -i
> dev-ho
job: "/home/jwelby/ansible/sub-playbooks/ansible-playbook -i dev-hosts
/home/jwelby/ansible/sub-playbooks/patching.yml"
30 15 * * 3 /home/jwelby/ansible/sub-playbooks/patching.yaml
These don't match. cron isn't running ansible-playbook. It is trying to run the
YAML file itself.
Wal
Things run from cron usually have a very limited set of time environments
variables available to them.
I assume you have no output at all now, so you don't know where to start
looking.
Start by ensuring that you receive any output from cron (pipe to email,
write to log, whatever is appropriate in
---
- name: Create a cronjob to patch dev instances
hosts: controller
tasks:
- name: Schedule cron
ansible.builtin.cron:
name: This cronjob is scheduled by Ansible
minute: "15"
hour: "12"
day: "*"
month: "*"
weekday: "3"
user: e
More information would be helpful here.
1. Can you share your usage of ansible.builtin.cron?
2. Can you share the output of crontab -l for the user you're creating the
cron job for/as, or the contents of /etc/crontab and/or /etc/cron.* ?
3. What's in your cronlog or systemd journal?
4. Obvious que
All,
Can a playbook be run by 'job', i.e. instead of a script.
I created a playbook that creates an entry in crontab, which it does
successfully, but it does not execute the playbook I specified in job:
Thanks!
John
--
You received this message because you are subscribed to the Google Groups
Add the change to the module is my vote.
Mike
> On Apr 19, 2023, at 05:05, Mélodie O wrote:
>
> Hello,
>
> I am generating random passwords using the lookup plugin. My issue is that I
> would like these passwords to be stored securely. I have searched everywhere
> but haven't found a solutio
Hello,
I am generating random passwords using the lookup plugin. My issue is that
I would like these passwords to be stored securely. I have searched
everywhere but haven't found a solution to my problem.
Therefore, I modified the lookup plugin and am using ansible-vault to
encrypt and store t
14 matches
Mail list logo