Getting Data In

Invalid URI Fragment error in splunkd.log

tvsjr_parsons
Engager

I am receiving the following error messages in splunkd.log every 10 minutes:

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=""

This is occurring on one of my indexers and my deployment server, but not on other systems (such as heavy forwarders).

Has anyone seen this before?

Tags (4)

bosburn_splunk
Splunk Employee
Splunk Employee

Are you running deployment monitor? If so, you may be hitting SPL-63568 (located here - Splunk Known Issues

Current work around is to delete any stanza's referring to dm_license_summary_10m_by_indexer in etc/apps/splunk_deployment_monitor/default/savedsearches.conf.

tvsjr_parsons
Engager

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.

0 Karma

marksnelling
Communicator

I'm getting this too, since I upgrade to Splunk 5.0.2. Did you find out what causes it?

0 Karma
Get Updates on the Splunk Community!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...