<?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: Removal or archiving of older metadata server logs in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/Removal-or-archiving-of-older-metadata-server-logs/m-p/686235#M20164</link>
    <description>&lt;P&gt;I have a job (shell script) that runs regularly and concatenates object spawner and metadata server logs per day; that takes care of restarts (rare, but they happen).&lt;/P&gt;
&lt;P&gt;The concatenated logs are read into SAS datasets and then archived, as I want (and need) to have full documentation who used the service, and when. This is part of GDPR compliance.&lt;/P&gt;</description>
    <pubDate>Wed, 23 Sep 2020 22:14:11 GMT</pubDate>
    <dc:creator>Kurt_Bremser</dc:creator>
    <dc:date>2020-09-23T22:14:11Z</dc:date>
    <item>
      <title>Removal or archiving of older metadata server logs</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Removal-or-archiving-of-older-metadata-server-logs/m-p/686227#M20161</link>
      <description>&lt;P&gt;We have been accumulating metadata logs and now need to remove or archive those that are not needed.&amp;nbsp; We are planning to use Python to code this out, but I thought I would ask if anyone has come up with a solution.&amp;nbsp; We plan to deploy as a cron job for weekly execution.&amp;nbsp; It's not just a matter of date based file comparison, some PID's can last weeks, others just days.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Using SAS v9.4M5&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;==================================================&lt;/P&gt;&lt;P&gt;New Metadata logs (see below) are generated on a daily basis, with the date embedded in the filename.&amp;nbsp; Also embedded in the filename is the “process ID” or PID for the latest reboot of the Metadata server.&amp;nbsp; The latest PID can be found in a file within the following directories:&lt;/P&gt;&lt;P&gt;/sasconfig/Lev1/SASMeta/MetadataServer/server.rccsasprd01.pid&lt;/P&gt;&lt;P&gt;/sasconfig/Lev1/ObjectSpawner/server.rccsasprd01.pid&lt;/P&gt;&lt;P&gt;These each contain &lt;U&gt;DIFFERENT&lt;/U&gt; PID’s.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Below we can see that both sets of logs had one PID (Object = 48866, Meta = 48731) which then changes after the server was restarted to (Object = 1900, Meta = 1724)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;sasinst sasadmin&amp;nbsp;&amp;nbsp; 629048 Sep 14 00:00 ObjectSpawner_2020-09-13_rccsasprd01_48866.log&lt;/P&gt;&lt;P&gt;sasinst sasadmin&amp;nbsp;&amp;nbsp; 455682 Sep 14 16:31 ObjectSpawner_2020-09-14_rccsasprd01_48866.log&lt;/P&gt;&lt;P&gt;sasinst sasadmin&amp;nbsp;&amp;nbsp; 203633 Sep 15 00:00 ObjectSpawner_2020-09-14_rccsasprd01_1900.log&lt;/P&gt;&lt;P&gt;sasinst sasadmin&amp;nbsp;&amp;nbsp; 648740 Sep 16 00:00 ObjectSpawner_2020-09-15_rccsasprd01_1900.log&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;sasinst sasadmin 22509544 Sep 14 00:00 SASMeta_MetadataServer_2020-09-13_rccsasprd01_48731.log&lt;/P&gt;&lt;P&gt;sasinst sasadmin 16065378 Sep 14 16:31 SASMeta_MetadataServer_2020-09-14_rccsasprd01_48731.log&lt;/P&gt;&lt;P&gt;sasinst sasadmin&amp;nbsp; 6416455 Sep 15 00:00 SASMeta_MetadataServer_2020-09-14_rccsasprd01_1724.log&lt;/P&gt;&lt;P&gt;sasinst sasadmin 22471372 Sep 16 00:00 SASMeta_MetadataServer_2020-09-15_rccsasprd01_1724.log&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The general advice from SAS was to keep the &lt;U&gt;two&lt;/U&gt; latest sets of PID logs from each server-type.&amp;nbsp; Logs older than that would not be meaningful for any type of error condition, for which SAS would need to review sed logs.&lt;/P&gt;&lt;P&gt;==================================================&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 23 Sep 2020 21:53:12 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Removal-or-archiving-of-older-metadata-server-logs/m-p/686227#M20161</guid>
      <dc:creator>epniv</dc:creator>
      <dc:date>2020-09-23T21:53:12Z</dc:date>
    </item>
    <item>
      <title>Re: Removal or archiving of older metadata server logs</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Removal-or-archiving-of-older-metadata-server-logs/m-p/686235#M20164</link>
      <description>&lt;P&gt;I have a job (shell script) that runs regularly and concatenates object spawner and metadata server logs per day; that takes care of restarts (rare, but they happen).&lt;/P&gt;
&lt;P&gt;The concatenated logs are read into SAS datasets and then archived, as I want (and need) to have full documentation who used the service, and when. This is part of GDPR compliance.&lt;/P&gt;</description>
      <pubDate>Wed, 23 Sep 2020 22:14:11 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Removal-or-archiving-of-older-metadata-server-logs/m-p/686235#M20164</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2020-09-23T22:14:11Z</dc:date>
    </item>
  </channel>
</rss>

