<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Ansible: restart splunk returning exit code in Installation</title>
    <link>https://community.splunk.com/t5/Installation/Ansible-restart-splunk-returning-exit-code/m-p/547311#M7308</link>
    <description>&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;I am using Ansible to automate Splunk operations. I have a handler that simply runs:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;- name: restart splunk
  shell: "{{ splunk_home }}/bin/splunk restart"
  become: yes
  become_user: "{{ splunk_nix_user }}"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Occasionally (1 out of every 5), this command will return an exit code with the following output.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[...]
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!&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any help is much appreciated&lt;/P&gt;</description>
    <pubDate>Fri, 09 Apr 2021 08:29:37 GMT</pubDate>
    <dc:creator>callemang</dc:creator>
    <dc:date>2021-04-09T08:29:37Z</dc:date>
    <item>
      <title>Ansible: restart splunk returning exit code</title>
      <link>https://community.splunk.com/t5/Installation/Ansible-restart-splunk-returning-exit-code/m-p/547311#M7308</link>
      <description>&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;I am using Ansible to automate Splunk operations. I have a handler that simply runs:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;- name: restart splunk
  shell: "{{ splunk_home }}/bin/splunk restart"
  become: yes
  become_user: "{{ splunk_nix_user }}"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Occasionally (1 out of every 5), this command will return an exit code with the following output.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[...]
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!&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any help is much appreciated&lt;/P&gt;</description>
      <pubDate>Fri, 09 Apr 2021 08:29:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Ansible-restart-splunk-returning-exit-code/m-p/547311#M7308</guid>
      <dc:creator>callemang</dc:creator>
      <dc:date>2021-04-09T08:29:37Z</dc:date>
    </item>
  </channel>
</rss>

