<?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 Splunk is down in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-is-down/m-p/58178#M659</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;We have our application running on RHEL. All of sudden it stopped working and did not allow users to login, we were getting error &lt;CODE&gt;Splunkd daemon is not responding: ('[Errno 111] Connection refused')&lt;/CODE&gt;. When we checked node by node, we noticed that on search head splunkd was not running. We restarted splunk on search head node and everything started functioning as usual.&lt;/P&gt;

&lt;P&gt;When we checked logs (splunkd, splunkd_stderr, web_access, web_service, crash) we just found following error or warning messages at different instances. Other than these, nothing else was there.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;06-03-2013 02:03:31.849 +0200 WARN  AuthenticationManagerScripted - Function 'getUsers' failed. Could not find '--status=success' in output
06-03-2013 02:03:31.849 +0200 ERROR AuthenticationManagerScripted - Script function getUsers failed

06-04-2013 07:16:47.423 +0200 ERROR ExecProcessor - message from "python /opt/splunk/etc/apps/SessionManagerStatistics/bin/webservice1.py" INFO:root:Error: &amp;lt;urlopen error [Errno -3] Temporary failure in name resolution&amp;gt;

06-04-2013 09:48:23.507 +0200 ERROR HTTPClient - Cannot find host "splunkbase.splunk.com": Name or service not known
06-04-2013 09:48:23.507 +0200 ERROR ApplicationUpdater - Error checking for update via https://splunkbase.splunk.com/api/apps:resolve/checkforupgrade: Invalid URI

06-04-2013 16:44:10.005 +0200 WARN  EventLoop - Main Thread: about to throw a EventLoopException: error from PolledSocket write: Broken pipe
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;What could be the issue?&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;

&lt;P&gt;Strive&lt;/P&gt;</description>
    <pubDate>Mon, 28 Sep 2020 14:03:29 GMT</pubDate>
    <dc:creator>strive</dc:creator>
    <dc:date>2020-09-28T14:03:29Z</dc:date>
    <item>
      <title>Splunk is down</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-is-down/m-p/58178#M659</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;We have our application running on RHEL. All of sudden it stopped working and did not allow users to login, we were getting error &lt;CODE&gt;Splunkd daemon is not responding: ('[Errno 111] Connection refused')&lt;/CODE&gt;. When we checked node by node, we noticed that on search head splunkd was not running. We restarted splunk on search head node and everything started functioning as usual.&lt;/P&gt;

&lt;P&gt;When we checked logs (splunkd, splunkd_stderr, web_access, web_service, crash) we just found following error or warning messages at different instances. Other than these, nothing else was there.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;06-03-2013 02:03:31.849 +0200 WARN  AuthenticationManagerScripted - Function 'getUsers' failed. Could not find '--status=success' in output
06-03-2013 02:03:31.849 +0200 ERROR AuthenticationManagerScripted - Script function getUsers failed

06-04-2013 07:16:47.423 +0200 ERROR ExecProcessor - message from "python /opt/splunk/etc/apps/SessionManagerStatistics/bin/webservice1.py" INFO:root:Error: &amp;lt;urlopen error [Errno -3] Temporary failure in name resolution&amp;gt;

06-04-2013 09:48:23.507 +0200 ERROR HTTPClient - Cannot find host "splunkbase.splunk.com": Name or service not known
06-04-2013 09:48:23.507 +0200 ERROR ApplicationUpdater - Error checking for update via https://splunkbase.splunk.com/api/apps:resolve/checkforupgrade: Invalid URI

06-04-2013 16:44:10.005 +0200 WARN  EventLoop - Main Thread: about to throw a EventLoopException: error from PolledSocket write: Broken pipe
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;What could be the issue?&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;

&lt;P&gt;Strive&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 14:03:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-is-down/m-p/58178#M659</guid>
      <dc:creator>strive</dc:creator>
      <dc:date>2020-09-28T14:03:29Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk is down</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-is-down/m-p/58179#M660</link>
      <description>&lt;P&gt;Are you Splunking data from the search head OS? - might be worth checking the usual stats from there, as it could be relating to the OS instead of just Splunk.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Jun 2013 08:43:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-is-down/m-p/58179#M660</guid>
      <dc:creator>MHibbin</dc:creator>
      <dc:date>2013-06-10T08:43:40Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk is down</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-is-down/m-p/58180#M661</link>
      <description>&lt;P&gt;We had a similar problem a few months ago. Turned out that it was not a Splunk problem, instead an AD issue. AD was not sending all of the data back that was requested.&lt;/P&gt;

&lt;P&gt;There could be another issue though. It almost seems as if Splunk is not indexing the data coming back in a single event from what you say.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Jun 2013 13:14:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-is-down/m-p/58180#M661</guid>
      <dc:creator>ShaneNewman</dc:creator>
      <dc:date>2013-06-10T13:14:35Z</dc:date>
    </item>
  </channel>
</rss>

