<?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: Not receiving syslog events in my Splunk Edge Processor in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Not-getting-data-in-Edge-Processor/m-p/678074#M113327</link>
    <description>&lt;P&gt;Please don't post the same question twice.&amp;nbsp; Please delete one of them.&lt;/P&gt;</description>
    <pubDate>Tue, 20 Feb 2024 13:31:15 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2024-02-20T13:31:15Z</dc:date>
    <item>
      <title>Not getting data in Edge Processor</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Not-getting-data-in-Edge-Processor/m-p/678068#M113321</link>
      <description>&lt;P&gt;Hello everyone,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;I am trying to send syslog data to my Edge Processor and it is the first time and it seems that it is not as simple as Splunk proposes.&lt;/P&gt;
&lt;P&gt;I am sending the data to port 514 TCP which is listening, the edge processor service is up and seems to be working.&lt;/P&gt;
&lt;P&gt;With a tcpdump it seems to get something to port 514, I put an example of the output:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;root@siacemsself01:/splunk-edge/etc# tcpdump -i any dst port 514 -Ans0
tcpdump: data link type LINUX_SLL2
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on any, link-type LINUX_SLL2 (Linux cooked v2), snapshot length 262144 bytes
12:00:33.644148 ens32 In IP 10.100.11.46.34344 &amp;gt; 10.100.11.237.514: Flags [.], ack 791814934, win 502, options [nop,nop,TS val 441690529 ecr 2755011762], length 0
E..43.@.@...
d..
d...(...^../2#......S.....
.S...6$.&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;But in the instance section nothing appears as inbound data.&lt;/P&gt;
&lt;P&gt;I also found this in the edge.log file:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;2024/02/20 11:40:33 workload exit: collector failed to start in idle mode, stuck in closing/closed state
{"level":"INFO","time":"2024-02-20T11:40:49.752Z","location":"teleport/plugin.go:100","message":"starting plugin","service":"edge-processor","hostname":"siacemsself01","commit":"92e64ca1","version":"1.0.0"}
{"level":"INFO","time":"2024-02-20T11:40:49.752Z","location":"teleport/plugin.go:179","message":"starting collector in idle mode","service":"edge-processor","hostname":"siacemsself01","commit":"92e64ca1","version":"1.0.0"}
{"level":"INFO","time":"2024-02-20T11:40:49.752Z","location":"logging/redactor.go:55","message":"startup package settings","service":"edge-processor","hostname":"siacemsself01","commit":"92e64ca1","version":"1.0.0","settings":{}}
{"level":"INFO","time":"2024-02-20T11:40:49.752Z","location":"teleport/plugin.go:198","message":"waiting new connector to start","service":"edge-processor","hostname":"siacemsself01","commit":"92e64ca1","version":"1.0.0"}
{"level":"INFO","time":"2024-02-20T11:40:49.752Z","location":"config/conf_map_factory.go:127","message":"settings is empty. returning nop configuration map","service":"edge-processor","hostname":"siacemsself01","commit":"92e64ca1","version":"1.0.0"}
{"level":"WARN","time":"2024-02-20T11:40:49.752Z","location":"logging/redactor.go:50","message":"unable to clone map","service":"edge-processor","hostname":"siacemsself01","commit":"92e64ca1","version":"1.0.0","error":"json: unsupported type: map[interface {}]interface {}"}
{"level":"INFO","time":"2024-02-20T11:40:49.753Z","location":"service@v0.92.0/telemetry.go:86","message":"Setting up own telemetry...","service":"edge-processor","hostname":"siacemsself01","commit":"92e64ca1","version":"1.0.0"}
{"level":"INFO","time":"2024-02-20T11:40:49.753Z","location":"service@v0.92.0/telemetry.go:203","message":"Serving Prometheus metrics","service":"edge-processor","hostname":"siacemsself01","commit":"92e64ca1","version":"1.0.0","address":"localhost:8888","level":"Basic"}
{"level":"INFO","time":"2024-02-20T11:40:49.754Z","location":"service@v0.92.0/service.go:151","message":"Starting otelcol-acies...","service":"edge-processor","hostname":"siacemsself01","commit":"92e64ca1","version":"1.0.0","Version":"92e64ca1","NumCPU":2}
{"level":"INFO","time":"2024-02-20T11:40:49.754Z","location":"extensions/extensions.go:34","message":"Starting extensions...","service":"edge-processor","hostname":"siacemsself01","commit":"92e64ca1","version":"1.0.0"}
{"level":"INFO","time":"2024-02-20T11:40:49.754Z","location":"service@v0.92.0/service.go:177","message":"Everything is ready. Begin running and processing data.","service":"edge-processor","hostname":"siacemsself01","commit":"92e64ca1","version":"1.0.0"}
{"level":"ERROR","time":"2024-02-20T11:40:49.754Z","location":"otelcol@v0.92.0/collector.go:255","message":"Asynchronous error received, terminating process","service":"edge-processor","hostname":"siacemsself01","commit":"92e64ca1","version":"1.0.0","error":"listen tcp 127.0.0.1:8888: bind: address already in use","callstack":"go.opentelemetry.io/collector/otelcol.(*Collector).Run\n\tgo.opentelemetry.io/collector/otelcol@v0.92.0/collector.go:255\ncd.splunkdev.com/data-availability/acies/teleport.(*Plugin).startCollector.func1\n\tcd.splunkdev.com/data-availability/acies/teleport/plugin.go:193"}
{"level":"INFO","time":"2024-02-20T11:40:49.754Z","location":"service@v0.92.0/service.go:191","message":"Starting shutdown...","service":"edge-processor","hostname":"siacemsself01","commit":"92e64ca1","version":"1.0.0"}
{"level":"INFO","time":"2024-02-20T11:40:49.754Z","location":"extensions/extensions.go:59","message":"Stopping extensions...","service":"edge-processor","hostname":"siacemsself01","commit":"92e64ca1","version":"1.0.0"}
{"level":"INFO","time":"2024-02-20T11:40:49.754Z","location":"service@v0.92.0/service.go:205","message":"Shutdown complete.","service":"edge-processor","hostname":"siacemsself01","commit":"92e64ca1","version":"1.0.0"}
{"level":"ERROR","time":"2024-02-20T11:40:49.754Z","location":"teleport/plugin.go:194","message":"failing to startup","service":"edge-processor","hostname":"siacemsself01","commit":"92e64ca1","version":"1.0.0"}
{"level":"ERROR","time":"2024-02-20T11:40:49.852Z","location":"teleport/plugin.go:227","message":"collector failed to start in idle mode, stuck in closing/closed state","service":"edge-processor","hostname":"siacemsself01","commit":"92e64ca1","version":"1.0.0"}&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any idea about what it's happening?&lt;/P&gt;</description>
      <pubDate>Tue, 20 Feb 2024 13:20:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Not-getting-data-in-Edge-Processor/m-p/678068#M113321</guid>
      <dc:creator>adrifesa95</dc:creator>
      <dc:date>2024-02-20T13:20:56Z</dc:date>
    </item>
    <item>
      <title>Re: Not receiving syslog events in my Splunk Edge Processor</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Not-getting-data-in-Edge-Processor/m-p/678074#M113327</link>
      <description>&lt;P&gt;Please don't post the same question twice.&amp;nbsp; Please delete one of them.&lt;/P&gt;</description>
      <pubDate>Tue, 20 Feb 2024 13:31:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Not-getting-data-in-Edge-Processor/m-p/678074#M113327</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2024-02-20T13:31:15Z</dc:date>
    </item>
    <item>
      <title>Re: Not getting data in Edge Processor</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Not-getting-data-in-Edge-Processor/m-p/678117#M113328</link>
      <description>&lt;P&gt;I deleted onee&lt;/P&gt;</description>
      <pubDate>Tue, 20 Feb 2024 18:44:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Not-getting-data-in-Edge-Processor/m-p/678117#M113328</guid>
      <dc:creator>adrifesa95</dc:creator>
      <dc:date>2024-02-20T18:44:05Z</dc:date>
    </item>
    <item>
      <title>Re: Not getting data in Edge Processor</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Not-getting-data-in-Edge-Processor/m-p/678176#M113335</link>
      <description>&lt;P&gt;There is only one! I deleted the others. Can someone help me?&lt;/P&gt;</description>
      <pubDate>Wed, 21 Feb 2024 11:43:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Not-getting-data-in-Edge-Processor/m-p/678176#M113335</guid>
      <dc:creator>adrifesa95</dc:creator>
      <dc:date>2024-02-21T11:43:07Z</dc:date>
    </item>
  </channel>
</rss>

