<?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 Re: Invalid URI Fragment error in splunkd.log in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Invalid-URI-Fragment-error-in-splunkd-log/m-p/96837#M20193</link>
    <description>&lt;P&gt;Are you running deployment monitor?  If so, you may be hitting SPL-63568 (located here - &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/ReleaseNotes/Knownissues"&gt;Splunk Known Issues&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Current work around is to delete any stanza's referring to &lt;CODE&gt;dm_license_summary_10m_by_indexer&lt;/CODE&gt; in &lt;CODE&gt;etc/apps/splunk_deployment_monitor/default/savedsearches.conf.&lt;/CODE&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 01 May 2013 14:02:50 GMT</pubDate>
    <dc:creator>bosburn_splunk</dc:creator>
    <dc:date>2013-05-01T14:02:50Z</dc:date>
    <item>
      <title>Invalid URI Fragment error in splunkd.log</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Invalid-URI-Fragment-error-in-splunkd-log/m-p/96834#M20190</link>
      <description>&lt;P&gt;I am receiving the following error messages in splunkd.log every 10 minutes:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;04-16-2013 20:31:37.148 +0000 ERROR HTTPClient - Invalid URI fragment "": can't find hostname
04-16-2013 20:31:37.148 +0000 WARN  SearchOperator:rest - Unable to fetch REST endpoint uri="/services/licenser/slaves?count=0" from server=""
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This is occurring on one of my indexers and my deployment server, but not on other systems (such as heavy forwarders).&lt;/P&gt;

&lt;P&gt;Has anyone seen this before?&lt;/P&gt;</description>
      <pubDate>Tue, 16 Apr 2013 20:44:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Invalid-URI-Fragment-error-in-splunkd-log/m-p/96834#M20190</guid>
      <dc:creator>tvsjr_parsons</dc:creator>
      <dc:date>2013-04-16T20:44:32Z</dc:date>
    </item>
    <item>
      <title>Re: Invalid URI Fragment error in splunkd.log</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Invalid-URI-Fragment-error-in-splunkd-log/m-p/96835#M20191</link>
      <description>&lt;P&gt;I'm getting this too, since I upgrade to Splunk 5.0.2. Did you find out what causes it?&lt;/P&gt;</description>
      <pubDate>Thu, 25 Apr 2013 14:38:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Invalid-URI-Fragment-error-in-splunkd-log/m-p/96835#M20191</guid>
      <dc:creator>marksnelling</dc:creator>
      <dc:date>2013-04-25T14:38:22Z</dc:date>
    </item>
    <item>
      <title>Re: Invalid URI Fragment error in splunkd.log</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Invalid-URI-Fragment-error-in-splunkd-log/m-p/96836#M20192</link>
      <description>&lt;P&gt;I haven't figured it out yet, but I'm seeing it on multiple systems (our current environment is two indexers, four heavy forwarders, and one deployment server), all running 5.0.2. If you're seeing it as well, then I'm thinking I may have found a bug... time to open a support case.&lt;/P&gt;</description>
      <pubDate>Thu, 25 Apr 2013 15:55:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Invalid-URI-Fragment-error-in-splunkd-log/m-p/96836#M20192</guid>
      <dc:creator>tvsjr_parsons</dc:creator>
      <dc:date>2013-04-25T15:55:53Z</dc:date>
    </item>
    <item>
      <title>Re: Invalid URI Fragment error in splunkd.log</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Invalid-URI-Fragment-error-in-splunkd-log/m-p/96837#M20193</link>
      <description>&lt;P&gt;Are you running deployment monitor?  If so, you may be hitting SPL-63568 (located here - &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/ReleaseNotes/Knownissues"&gt;Splunk Known Issues&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Current work around is to delete any stanza's referring to &lt;CODE&gt;dm_license_summary_10m_by_indexer&lt;/CODE&gt; in &lt;CODE&gt;etc/apps/splunk_deployment_monitor/default/savedsearches.conf.&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 01 May 2013 14:02:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Invalid-URI-Fragment-error-in-splunkd-log/m-p/96837#M20193</guid>
      <dc:creator>bosburn_splunk</dc:creator>
      <dc:date>2013-05-01T14:02:50Z</dc:date>
    </item>
  </channel>
</rss>

