<?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 Issue: Azure add-on - receiving   error: HTTP 503 Service Unavailable -- KV Store initialization failed. in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/Issue-Azure-add-on-receiving-error-HTTP-503-Service-Unavailable/m-p/543427#M5251</link>
    <description>&lt;P&gt;Azure add-on has been install on HF for months.&amp;nbsp;&lt;/P&gt;&lt;P&gt;The certificate expired last week. appears to have caused an issue with the Azure add-on. no data ingesting since certificate expired.&amp;nbsp;&lt;/P&gt;&lt;P&gt;* certificate was replaced.&amp;nbsp;&lt;/P&gt;&lt;P&gt;* data started ingested again right after the new certificate was working.&amp;nbsp;&lt;/P&gt;&lt;P&gt;* then after about 4 hrs no data was being ingested again on the HF for the azure add-on&lt;/P&gt;&lt;P&gt;* from recommendations on answers, changed the "&lt;SPAN&gt;Max Batch Set Iterations" to 1000&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;-- didn't help&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;* why would data be ingesting into SPlunk after the certificate was replaced but then stop being ingested into Splunkl&lt;/SPAN&gt;&lt;/P&gt;&lt;DIV class="col-sm-10 controls control-placeholder"&gt;&amp;nbsp;&lt;/DIV&gt;</description>
    <pubDate>Thu, 11 Mar 2021 17:17:30 GMT</pubDate>
    <dc:creator>kcooper</dc:creator>
    <dc:date>2021-03-11T17:17:30Z</dc:date>
    <item>
      <title>Issue: Azure add-on - receiving   error: HTTP 503 Service Unavailable -- KV Store initialization failed.</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Issue-Azure-add-on-receiving-error-HTTP-503-Service-Unavailable/m-p/543427#M5251</link>
      <description>&lt;P&gt;Azure add-on has been install on HF for months.&amp;nbsp;&lt;/P&gt;&lt;P&gt;The certificate expired last week. appears to have caused an issue with the Azure add-on. no data ingesting since certificate expired.&amp;nbsp;&lt;/P&gt;&lt;P&gt;* certificate was replaced.&amp;nbsp;&lt;/P&gt;&lt;P&gt;* data started ingested again right after the new certificate was working.&amp;nbsp;&lt;/P&gt;&lt;P&gt;* then after about 4 hrs no data was being ingested again on the HF for the azure add-on&lt;/P&gt;&lt;P&gt;* from recommendations on answers, changed the "&lt;SPAN&gt;Max Batch Set Iterations" to 1000&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;-- didn't help&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;* why would data be ingesting into SPlunk after the certificate was replaced but then stop being ingested into Splunkl&lt;/SPAN&gt;&lt;/P&gt;&lt;DIV class="col-sm-10 controls control-placeholder"&gt;&amp;nbsp;&lt;/DIV&gt;</description>
      <pubDate>Thu, 11 Mar 2021 17:17:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Issue-Azure-add-on-receiving-error-HTTP-503-Service-Unavailable/m-p/543427#M5251</guid>
      <dc:creator>kcooper</dc:creator>
      <dc:date>2021-03-11T17:17:30Z</dc:date>
    </item>
    <item>
      <title>Re: Issue: Azure add-on - receiving   error: HTTP 503 Service Unavailable -- KV Store initialization failed.</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Issue-Azure-add-on-receiving-error-HTTP-503-Service-Unavailable/m-p/543694#M5277</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Is the certificate got replaced from azure end?&lt;/P&gt;&lt;P&gt;If it is for every new certificate the API key will change. Check the API was same or not in Azure and compare it with your Splunk configuration.&lt;/P&gt;</description>
      <pubDate>Sat, 13 Mar 2021 20:45:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Issue-Azure-add-on-receiving-error-HTTP-503-Service-Unavailable/m-p/543694#M5277</guid>
      <dc:creator>Vardhan</dc:creator>
      <dc:date>2021-03-13T20:45:45Z</dc:date>
    </item>
  </channel>
</rss>

