<?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 SASWIPClientAccess9.4.log occupying more space in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/SASWIPClientAccess9-4-log-occupying-more-space/m-p/478689#M13626</link>
    <description>&lt;P&gt;Hi Admins,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;On our Mid-tier server the&amp;nbsp;SASWIPClientAccess9.4.log is occupying about 40GB. Do some one have any recommendation how to deal with that. IS that fine if I can delete that file? I don't see any error but concerns is Config folder is full due to that log file. Please suggest.&lt;/P&gt;
&lt;P&gt;path of the file is&amp;nbsp;/sso/biconfig/940/Lev1/Web/Logs/SASServer1_1/&lt;SPAN&gt;SASWIPClientAccess9.4.log&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Thanks in advance.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 17 Jul 2018 15:21:33 GMT</pubDate>
    <dc:creator>maheshtalla</dc:creator>
    <dc:date>2018-07-17T15:21:33Z</dc:date>
    <item>
      <title>SASWIPClientAccess9.4.log occupying more space</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SASWIPClientAccess9-4-log-occupying-more-space/m-p/478689#M13626</link>
      <description>&lt;P&gt;Hi Admins,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;On our Mid-tier server the&amp;nbsp;SASWIPClientAccess9.4.log is occupying about 40GB. Do some one have any recommendation how to deal with that. IS that fine if I can delete that file? I don't see any error but concerns is Config folder is full due to that log file. Please suggest.&lt;/P&gt;
&lt;P&gt;path of the file is&amp;nbsp;/sso/biconfig/940/Lev1/Web/Logs/SASServer1_1/&lt;SPAN&gt;SASWIPClientAccess9.4.log&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Thanks in advance.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Jul 2018 15:21:33 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SASWIPClientAccess9-4-log-occupying-more-space/m-p/478689#M13626</guid>
      <dc:creator>maheshtalla</dc:creator>
      <dc:date>2018-07-17T15:21:33Z</dc:date>
    </item>
    <item>
      <title>Re: SASWIPClientAccess9.4.log occupying more space</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SASWIPClientAccess9-4-log-occupying-more-space/m-p/478936#M13634</link>
      <description>&lt;P&gt;I would:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;stop the Web Application Server, and make sure that no tomcat instance is left running&lt;/LI&gt;
&lt;LI&gt;move the file to another place&lt;/LI&gt;
&lt;LI&gt;start the Web Application Server&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Note that stopping/starting the WAS takes quite some time, so get some scheduled downtime for that (unless your situation is already critical and services have stopped working)&lt;/P&gt;
&lt;P&gt;After that, inspect the file. Start at the end to see if some rapidly repeating pattern caused the size increase. If not, you might contemplate to use SAS to read the log and do statistical analyses to see if a lot of messages were written within a rather short timeframe.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You might find that it was caused by someone trying some kind of brute force attack (intentional or unintentional). This can happen when penetration tests are run by security people.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Jul 2018 07:27:11 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SASWIPClientAccess9-4-log-occupying-more-space/m-p/478936#M13634</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2018-07-18T07:27:11Z</dc:date>
    </item>
  </channel>
</rss>

