Installation

Ansible: restart splunk returning exit code

callemang
Explorer

Hello!

I am using Ansible to automate Splunk operations. I have a handler that simply runs:

 

- name: restart splunk
  shell: "{{ splunk_home }}/bin/splunk restart"
  become: yes
  become_user: "{{ splunk_nix_user }}"

 

Occasionally (1 out of every 5), this command will return an exit code with the following output.

 

[...]
All preliminary checks passed.

Starting splunk server daemon (splunkd)...  
Done

Waiting for web server at https://127.0.0.1:8443 to be available.....

WARNING: web interface does not seem to be available!

 

This causes my Ansible Tower job to fail and send out failure notifications to the team. Seconds later, the web interface is available and all is well (except for my pride because of the failure notification).

 

Is there any way to have Splunk wait longer to check for the web UI to be up? Or possibly a way for Ansible to not fail on this exit code or zero?

 

Any help is much appreciated

Labels (2)
Tags (1)
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...