<?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 forwarder (version 7.2.2) creating zombie thread. in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-forwarder-version-7-2-2-creating-zombie-thread/m-p/419532#M51146</link>
    <description>&lt;P&gt;We recently installed Splunk forwarder v 7.2.2  the moment it started creating a defunct PID with SYSTEMCLT. I want to know why this keeps on happening. Let us know if we need to change something.&lt;/P&gt;

&lt;P&gt;FYI.. &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Z     5820  7359 systemctl  
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;--&amp;gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;4 S root      5820     1  0  80   0 - 96658 ep_pol Apr12 ?        00:04:43 splunkd --under-systemd --systemd-delegate=yes -p 8089 _internal_launch_under_systemd
4 Z root      7359  5820  0  80   0 -     0 do_exi Apr12 ?        00:00:00 [systemctl] 
5 S root      7458  5820  0  80   0 - 21465 ep_pol Apr12 ?        00:00:00 [splunkd pid=5820] splunkd --under-systemd --systemd-delegate=yes -p 8089 _internal_launch_under_systemd [process-runner]
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Thu, 18 Apr 2019 14:19:59 GMT</pubDate>
    <dc:creator>sreechallagundl</dc:creator>
    <dc:date>2019-04-18T14:19:59Z</dc:date>
    <item>
      <title>Splunk forwarder (version 7.2.2) creating zombie thread.</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-forwarder-version-7-2-2-creating-zombie-thread/m-p/419532#M51146</link>
      <description>&lt;P&gt;We recently installed Splunk forwarder v 7.2.2  the moment it started creating a defunct PID with SYSTEMCLT. I want to know why this keeps on happening. Let us know if we need to change something.&lt;/P&gt;

&lt;P&gt;FYI.. &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Z     5820  7359 systemctl  
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;--&amp;gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;4 S root      5820     1  0  80   0 - 96658 ep_pol Apr12 ?        00:04:43 splunkd --under-systemd --systemd-delegate=yes -p 8089 _internal_launch_under_systemd
4 Z root      7359  5820  0  80   0 -     0 do_exi Apr12 ?        00:00:00 [systemctl] 
5 S root      7458  5820  0  80   0 - 21465 ep_pol Apr12 ?        00:00:00 [splunkd pid=5820] splunkd --under-systemd --systemd-delegate=yes -p 8089 _internal_launch_under_systemd [process-runner]
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 18 Apr 2019 14:19:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-forwarder-version-7-2-2-creating-zombie-thread/m-p/419532#M51146</guid>
      <dc:creator>sreechallagundl</dc:creator>
      <dc:date>2019-04-18T14:19:59Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk forwarder (version 7.2.2) creating zombie thread.</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-forwarder-version-7-2-2-creating-zombie-thread/m-p/419533#M51147</link>
      <description>&lt;P&gt;Were you able to sort it out? I'm facing the exact same issue&lt;/P&gt;

&lt;P&gt;Thanks in advance&lt;/P&gt;</description>
      <pubDate>Mon, 20 May 2019 09:36:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-forwarder-version-7-2-2-creating-zombie-thread/m-p/419533#M51147</guid>
      <dc:creator>ptcrusher</dc:creator>
      <dc:date>2019-05-20T09:36:23Z</dc:date>
    </item>
  </channel>
</rss>

