<?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: Zombie SAS process on Windows server in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/Zombie-SAS-process-on-Windows-server/m-p/192615#M9838</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sometimes a client is disconnected from a Workspace Server process in a way that causes it to hang completely. Normal termination signals will not work at all. On UNIX, this means to use kill -9, which causes the kernel to deallocate the process without any cooperation from the process itself.&lt;/P&gt;&lt;P&gt;There must be a similar radical command in Windows.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 22 Jan 2015 14:04:26 GMT</pubDate>
    <dc:creator>Kurt_Bremser</dc:creator>
    <dc:date>2015-01-22T14:04:26Z</dc:date>
    <item>
      <title>Zombie SAS process on Windows server</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Zombie-SAS-process-on-Windows-server/m-p/192614#M9837</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have SAS EBI on a windows server.&amp;nbsp;&amp;nbsp; The server admin is worried about the amount of SAS process, some of them were started weeks ago.&amp;nbsp;&amp;nbsp; We decided to try to schedule a restart of the Object Spawner, every Sunday morning, so all the SAS process spawned would be kill.&amp;nbsp;&amp;nbsp; It worked for some of them.&amp;nbsp;&amp;nbsp; Here is our batch file:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;net stop "SAS [SASCONFIG-Lev1] Object Spawner"&lt;/P&gt;&lt;P&gt;TIMEOUT /T 60 /NOBREAK&lt;/P&gt;&lt;P&gt;net start "SAS [SASCONFIG-Lev1] Object Spawner"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are missing something ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there another way to clean up those zombie process ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Laurent&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Jan 2015 13:57:57 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Zombie-SAS-process-on-Windows-server/m-p/192614#M9837</guid>
      <dc:creator>tlk</dc:creator>
      <dc:date>2015-01-22T13:57:57Z</dc:date>
    </item>
    <item>
      <title>Re: Zombie SAS process on Windows server</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Zombie-SAS-process-on-Windows-server/m-p/192615#M9838</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sometimes a client is disconnected from a Workspace Server process in a way that causes it to hang completely. Normal termination signals will not work at all. On UNIX, this means to use kill -9, which causes the kernel to deallocate the process without any cooperation from the process itself.&lt;/P&gt;&lt;P&gt;There must be a similar radical command in Windows.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Jan 2015 14:04:26 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Zombie-SAS-process-on-Windows-server/m-p/192615#M9838</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2015-01-22T14:04:26Z</dc:date>
    </item>
    <item>
      <title>Re: Zombie SAS process on Windows server</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Zombie-SAS-process-on-Windows-server/m-p/192616#M9839</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As far as I know the kill command in Windows behave the same as kill -9 on UNIX.&amp;nbsp;&amp;nbsp; Is there a way to identify those process ? Can I find way to know if a client is still connected to the process.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Jan 2015 14:49:15 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Zombie-SAS-process-on-Windows-server/m-p/192616#M9839</guid>
      <dc:creator>tlk</dc:creator>
      <dc:date>2015-01-22T14:49:15Z</dc:date>
    </item>
    <item>
      <title>Re: Zombie SAS process on Windows server</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Zombie-SAS-process-on-Windows-server/m-p/192617#M9840</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When the processes are real zombies they will not go away when the initiator (object spawner) is gone.&lt;/P&gt;&lt;P&gt;The root cause can be a hangup in the closing part.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Similar radical commands exist in Windows &lt;A href="https://technet.microsoft.com/en-us/sysinternals/bb896649.aspx" title="https://technet.microsoft.com/en-us/sysinternals/bb896649.aspx"&gt;PsTools&lt;/A&gt; (TechNet) PSkill -&lt;A href="https://technet.microsoft.com/en-us/library/bb491009.aspx" title="https://technet.microsoft.com/en-us/library/bb491009.aspx"&gt;Taskkill&lt;/A&gt;&amp;nbsp; lseems to be a normal interenal command. On my W7 it is giving a reaction. /F as -9 switch.&lt;BR /&gt;If you are worried think on restarting all serverice and validate the machine is clean and setup on a regular planned schedule moment.&lt;/P&gt;&lt;P&gt;There are a lot of sasprocesess that are services (multithreaded).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Jan 2015 15:09:55 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Zombie-SAS-process-on-Windows-server/m-p/192617#M9840</guid>
      <dc:creator>jakarman</dc:creator>
      <dc:date>2015-01-22T15:09:55Z</dc:date>
    </item>
    <item>
      <title>Re: Zombie SAS process on Windows server</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Zombie-SAS-process-on-Windows-server/m-p/192618#M9841</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Zencos has a helpful video about locating these processes: &lt;A href="http://www.zencos.com/resources/how-to-videos/how-to-detect-zombie-sessions/"&gt;How to Detect Zombie Sessions&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Feb 2015 12:19:13 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Zombie-SAS-process-on-Windows-server/m-p/192618#M9841</guid>
      <dc:creator>TriciaAanderud</dc:creator>
      <dc:date>2015-02-18T12:19:13Z</dc:date>
    </item>
  </channel>
</rss>

