<?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: Venafi logs have stopped ingesting into Splunk in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Venafi-logs-have-stopped-ingesting-into-Splunk/m-p/453450#M78546</link>
    <description>&lt;P&gt;thanks Woodcock, i guess that works , let me try that &lt;/P&gt;</description>
    <pubDate>Tue, 02 Jul 2019 20:00:14 GMT</pubDate>
    <dc:creator>splunker545</dc:creator>
    <dc:date>2019-07-02T20:00:14Z</dc:date>
    <item>
      <title>Venafi logs have stopped ingesting into Splunk</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Venafi-logs-have-stopped-ingesting-into-Splunk/m-p/453448#M78544</link>
      <description>&lt;P&gt;Venafi logs stopped ingesting into Splunk.&lt;/P&gt;

&lt;P&gt;We have appropriate role created and capabilities(edit_tcp) also attached&lt;BR /&gt;
when we tested with dev environment below errors appearing from Venafi end &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;"An error occurred while connecting to splunk-dev.XXXXX:8089.  Error: 401: Unauthorized
  Warning: Login failed  Details:    at Splunk.Client.Response.d__b.MoveNext()
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;--- End of stack trace from previous location where exception was thrown ---&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at Splunk.Client.Response.d__4.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at Splunk.Client.Service.d__b.MoveNext()"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Below are the internal  logs generated from Splunk side:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;07-01-2019 14:43:45.929 -0400 ERROR UserManagerPro - LDAP Login failed, could not find a valid user="venafi_input" on any configured servers
host =  XXXXX  source = /opt/splunk/var/log/splunk/splunkd.log sourcetype = splunkd
7/1/19
2:39:31.621 PM  
07-01-2019 14:39:31.621 -0400 ERROR UserManagerPro - LDAP Login failed, could not find a valid user="venafi_input" on any configured servers
host =  XXXXX source =  /opt/splunk/var/log/splunk/splunkd.log sourcetype = splunkd
7/1/19
3:00:57.328 AM  
07-01-2019 03:00:57.328 -0400 ERROR UserManagerPro - LDAP Login failed, could not find a valid user="venafi_input" on any configured servers
host =  XXXXX source =  /opt/splunk/var/log/splunk/splunkd.log sourcetype = splunkd
6/30/19
3:02:55.905 AM  
06-30-2019 03:02:55.905 -0400 ERROR UserManagerPro - LDAP Login failed, could not find a valid user="venafi_input" on any configured servers
host =  XXXXX  source = /opt/splunk/var/log/splunk/splunkd.log sourcetype = splunkd
6/29/19
3:13:47.592 AM  
06-29-2019 03:13:47.592 -0400 ERROR UserManagerPro - LDAP Login failed, could not find a valid user="venafi_input" on any configured servers
host =  XXXXX source =  /opt/splunk/var/log/splunk/splunkd.log sourcetype = splunkd
6/28/19
9:56:27.005 AM  
06-28-2019 09:56:27.005 -0400 ERROR UserManagerPro - LDAP Login failed, could not find a valid user="venafi_input" on any configured servers
host =  XXXXX source =  /opt/splunk/var/log/splunk/splunkd.log sourcetype = splunkd
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Note: Venafi application hosted in Windows server &lt;BR /&gt;
please provide your insights ,TIA&lt;/P&gt;</description>
      <pubDate>Mon, 01 Jul 2019 19:48:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Venafi-logs-have-stopped-ingesting-into-Splunk/m-p/453448#M78544</guid>
      <dc:creator>splunker545</dc:creator>
      <dc:date>2019-07-01T19:48:44Z</dc:date>
    </item>
    <item>
      <title>Re: Venafi logs have stopped ingesting into Splunk</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Venafi-logs-have-stopped-ingesting-into-Splunk/m-p/453449#M78545</link>
      <description>&lt;P&gt;The log could hardly be more clear.  The user that is being used to access the logs ( &lt;CODE&gt;venafi_input&lt;/CODE&gt; ) is no longer valid.  Fix that user or create a new one and switch to using the new one.&lt;/P&gt;</description>
      <pubDate>Mon, 01 Jul 2019 22:10:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Venafi-logs-have-stopped-ingesting-into-Splunk/m-p/453449#M78545</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2019-07-01T22:10:00Z</dc:date>
    </item>
    <item>
      <title>Re: Venafi logs have stopped ingesting into Splunk</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Venafi-logs-have-stopped-ingesting-into-Splunk/m-p/453450#M78546</link>
      <description>&lt;P&gt;thanks Woodcock, i guess that works , let me try that &lt;/P&gt;</description>
      <pubDate>Tue, 02 Jul 2019 20:00:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Venafi-logs-have-stopped-ingesting-into-Splunk/m-p/453450#M78546</guid>
      <dc:creator>splunker545</dc:creator>
      <dc:date>2019-07-02T20:00:14Z</dc:date>
    </item>
  </channel>
</rss>

