<?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: ps_sos.ps1 Microsoft.PowerShell.Commands.WriteErrorException in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/ps-sos-ps1-Microsoft-PowerShell-Commands-WriteErrorException/m-p/161129#M14926</link>
    <description>&lt;P&gt;How do I add something bigger than the small comment size given???&lt;/P&gt;</description>
    <pubDate>Tue, 13 May 2014 23:30:56 GMT</pubDate>
    <dc:creator>dlpco</dc:creator>
    <dc:date>2014-05-13T23:30:56Z</dc:date>
    <item>
      <title>ps_sos.ps1 Microsoft.PowerShell.Commands.WriteErrorException</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/ps-sos-ps1-Microsoft-PowerShell-Commands-WriteErrorException/m-p/161123#M14920</link>
      <description>&lt;P&gt;I am getting the following in splunkd.log for ps_sos.ps1:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;
 D:\Splunk\etc\apps\sos\bin\powershell\ps_sos.ps1 : Exception of type 'Microsoft
 .PowerShell.Commands.WriteErrorException' was thrown.
 At line:1 char:2
 + . &amp;lt;&amp;lt;&amp;lt;&amp;lt;  'D:\Splunk\etc\apps\sos\bin\\powershell\ps_sos.ps1'
     + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorExcep 
    tion
     + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorExceptio 
    n,ps_sos.ps1
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I am running 6.1.1 (free license) and SOS 3.2. Any ideas on what's going on and how to fix it????&lt;/P&gt;

&lt;P&gt;Below in comments I tried to put in the record dumps but ran out of room. Here they are now...&lt;/P&gt;

&lt;P&gt;05/13/14 11:51:26.000 AM&lt;BR /&gt;&lt;BR /&gt;
&lt;PRE&gt;&lt;CODE&gt;&lt;BR /&gt;
PID        pctCPU     RSZ_KB     VSZ_KB     ELAPSED            COMMAND    ARGS&lt;BR /&gt;
1980       0          137468     307072     0-0:42:12          splunkd    service&lt;BR /&gt;
3652       0          24288      90056      0-0:0:30           splunkd    search_--id=rt_1400007053.24_--maxbuckets=300_--ttl=600_--maxout=100000_--maxtime=0_--lookups=1_--reduce_freq=10_--rf=*&lt;BR /&gt;
3908                  22556      88008      0-0:0:30           splunkd    System.Object[]&lt;BR /&gt;
4064                  22572      88008      0-0:0:30           splunkd    System.Object[]&lt;BR /&gt;
4944                  24284      90056      0-0:0:30           splunkd    System.Object[]&lt;BR /&gt;
5324       0          16288      81500      0-0:41:7           splunkd    instrument-resource-usage&lt;BR /&gt;
6676       0          24176      90056      0-0:0:21           splunkd    search_--id=rt_1400007064.25_--maxbuckets=300_--ttl=600_--maxout=100000_--maxtime=0_--lookups=1_--reduce_freq=10_--rf=*&lt;BR /&gt;
7180                  24456      90056      0-0:0:21           splunkd    System.Object[]&lt;BR /&gt;
7580       61         24448      91080      0-0:0:3            splunkd    search_--id=1400007082.30_--maxbuckets=300_--ttl=600_--maxout=500000_--maxtime=0_--lookups=1_--reduce_freq=10_--rf=*&lt;BR /&gt;
2456       0          70816      150620     0-0:42:12          splunkweb&lt;BR /&gt;&lt;BR /&gt;
&lt;/CODE&gt;&lt;/PRE&gt;&lt;/P&gt;

&lt;P&gt;05/13/14 11:51:21.000 AM&lt;BR /&gt;&lt;BR /&gt;
&lt;PRE&gt;&lt;CODE&gt;&lt;BR /&gt;
PID        pctCPU     RSZ_KB     VSZ_KB     ELAPSED            COMMAND    ARGS&lt;BR /&gt;
1980       0          136340     307072     0-0:42:7           splunkd    service&lt;BR /&gt;
3652       0          24288      90056      0-0:0:25           splunkd    search_--id=rt_1400007053.24_--maxbuckets=300_--ttl=600_--maxout=100000_--maxtime=0_--lookups=1_--reduce_freq=10_--rf=*&lt;BR /&gt;
3908       0          22428      88008      0-0:0:2            splunkd    search_--id=rt_1400007076.28_--maxbuckets=300_--ttl=600_--maxout=100000_--maxtime=0_--lookups=1_--reduce_freq=10_--rf=*&lt;BR /&gt;
4064       0          22564      88008      0-0:0:3            splunkd    search_--id=rt_1400007076.29_--maxbuckets=300_--ttl=600_--maxout=100000_--maxtime=0_--lookups=1_--reduce_freq=10_--rf=*&lt;BR /&gt;
4944       0          22284      88008      0-0:0:5            splunkd    search_--id=rt_1400007074.26_--maxbuckets=300_--ttl=600_--maxout=100000_--maxtime=0_--lookups=1_--reduce_freq=10_--rf=*&lt;BR /&gt;
5324       0          16288      81500      0-0:41:3           splunkd    instrument-resource-usage&lt;BR /&gt;
6676       0          24176      90056      0-0:0:16           splunkd    search_--id=rt_1400007064.25_--maxbuckets=300_--ttl=600_--maxout=100000_--maxtime=0_--lookups=1_--reduce_freq=10_--rf=*&lt;BR /&gt;
7180       0          22448      88008      0-0:0:3            splunkd    search_--id=rt_1400007076.27_--maxbuckets=300_--ttl=600_--maxout=100000_--maxtime=0_--lookups=1_--reduce_freq=10_--rf=*&lt;BR /&gt;
2456       0          70816      150620     0-0:42:6           splunkweb&lt;BR /&gt;&lt;BR /&gt;
&lt;/CODE&gt;&lt;/PRE&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 16:35:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/ps-sos-ps1-Microsoft-PowerShell-Commands-WriteErrorException/m-p/161123#M14920</guid>
      <dc:creator>dlpco</dc:creator>
      <dc:date>2020-09-28T16:35:13Z</dc:date>
    </item>
    <item>
      <title>Re: ps_sos.ps1 Microsoft.PowerShell.Commands.WriteErrorException</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/ps-sos-ps1-Microsoft-PowerShell-Commands-WriteErrorException/m-p/161124#M14921</link>
      <description>&lt;P&gt;Did these errors start after you installed S.o.S 3.2? Were there none before?&lt;/P&gt;

&lt;P&gt;How often do you see these errors - do they occur every time (5s) the script runs?&lt;/P&gt;

&lt;P&gt;Finally, what output do you get if you attempt to run the script manually from the command line?&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;%SPLUNK_HOME%\bin\splunk cmd %SPLUNK_HOME%\etc\apps\sos\bin\sospowershell.cmd ps_sos.ps1&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 12 May 2014 22:11:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/ps-sos-ps1-Microsoft-PowerShell-Commands-WriteErrorException/m-p/161124#M14921</guid>
      <dc:creator>hexx</dc:creator>
      <dc:date>2014-05-12T22:11:46Z</dc:date>
    </item>
    <item>
      <title>Re: ps_sos.ps1 Microsoft.PowerShell.Commands.WriteErrorException</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/ps-sos-ps1-Microsoft-PowerShell-Commands-WriteErrorException/m-p/161125#M14922</link>
      <description>&lt;P&gt;I have been running 3.2 for a while and I am unsure if they happened before splunk 6.1 and 6.1.1. &lt;/P&gt;

&lt;P&gt;These errors do NOT happen every 5s. An example of the time stamps are:&lt;BR /&gt;
05-13-2014 11:15:03.862&lt;BR /&gt;
05-13-2014 11:17:09.409&lt;BR /&gt;
05-13-2014 11:17:09.615&lt;BR /&gt;
05-13-2014 11:17:24.872&lt;BR /&gt;
05-13-2014 11:18:19.241&lt;BR /&gt;
05-13-2014 11:19:04.387&lt;BR /&gt;
05-13-2014 11:26:49.459&lt;BR /&gt;
and now it is 11:48 and no more entries!  Strange hu!!&lt;/P&gt;

&lt;P&gt;When I run the script at the command line, I get the output I would expect from a ps in Linux.&lt;/P&gt;

&lt;P&gt;I can also look with a Splunk search (source="ps_sos.ps1") and I can see the data coming in ever 5s.&lt;/P&gt;</description>
      <pubDate>Tue, 13 May 2014 18:54:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/ps-sos-ps1-Microsoft-PowerShell-Commands-WriteErrorException/m-p/161125#M14922</guid>
      <dc:creator>dlpco</dc:creator>
      <dc:date>2014-05-13T18:54:04Z</dc:date>
    </item>
    <item>
      <title>Re: ps_sos.ps1 Microsoft.PowerShell.Commands.WriteErrorException</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/ps-sos-ps1-Microsoft-PowerShell-Commands-WriteErrorException/m-p/161126#M14923</link>
      <description>&lt;P&gt;This is good to know. Now, if you don't mind digging a bit further: Do you see any records in the &lt;CODE&gt;sos&lt;/CODE&gt; index for the times when the script reports an error? Or are there gaps? If there are records there, can you show a sample event produced during a run of &lt;CODE&gt;ps_sos.ps1&lt;/CODE&gt; that also yielded an error?&lt;/P&gt;</description>
      <pubDate>Tue, 13 May 2014 19:13:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/ps-sos-ps1-Microsoft-PowerShell-Commands-WriteErrorException/m-p/161126#M14923</guid>
      <dc:creator>hexx</dc:creator>
      <dc:date>2014-05-13T19:13:17Z</dc:date>
    </item>
    <item>
      <title>Re: ps_sos.ps1 Microsoft.PowerShell.Commands.WriteErrorException</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/ps-sos-ps1-Microsoft-PowerShell-Commands-WriteErrorException/m-p/161127#M14924</link>
      <description>&lt;P&gt;Okay - lets see if I got this right.&lt;/P&gt;

&lt;P&gt;The log shows 2 failures at 11:51:24.906 and 11:51:25.243&lt;/P&gt;

&lt;P&gt;Looking in the records I see: (Let me know if this is what you wanted...)&lt;/P&gt;</description>
      <pubDate>Tue, 13 May 2014 23:23:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/ps-sos-ps1-Microsoft-PowerShell-Commands-WriteErrorException/m-p/161127#M14924</guid>
      <dc:creator>dlpco</dc:creator>
      <dc:date>2014-05-13T23:23:39Z</dc:date>
    </item>
    <item>
      <title>Re: ps_sos.ps1 Microsoft.PowerShell.Commands.WriteErrorException</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/ps-sos-ps1-Microsoft-PowerShell-Commands-WriteErrorException/m-p/161128#M14925</link>
      <description>&lt;P&gt;The text of the event appears to not have carried over in your comment. Perhaps you can insert it in your question?&lt;/P&gt;</description>
      <pubDate>Tue, 13 May 2014 23:29:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/ps-sos-ps1-Microsoft-PowerShell-Commands-WriteErrorException/m-p/161128#M14925</guid>
      <dc:creator>hexx</dc:creator>
      <dc:date>2014-05-13T23:29:19Z</dc:date>
    </item>
    <item>
      <title>Re: ps_sos.ps1 Microsoft.PowerShell.Commands.WriteErrorException</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/ps-sos-ps1-Microsoft-PowerShell-Commands-WriteErrorException/m-p/161129#M14926</link>
      <description>&lt;P&gt;How do I add something bigger than the small comment size given???&lt;/P&gt;</description>
      <pubDate>Tue, 13 May 2014 23:30:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/ps-sos-ps1-Microsoft-PowerShell-Commands-WriteErrorException/m-p/161129#M14926</guid>
      <dc:creator>dlpco</dc:creator>
      <dc:date>2014-05-13T23:30:56Z</dc:date>
    </item>
    <item>
      <title>Re: ps_sos.ps1 Microsoft.PowerShell.Commands.WriteErrorException</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/ps-sos-ps1-Microsoft-PowerShell-Commands-WriteErrorException/m-p/161130#M14927</link>
      <description>&lt;P&gt;I added it to the base question. Is that what you wanted???&lt;/P&gt;

&lt;P&gt;You notice they are a little off the previous and following records that are timestamped at:&lt;BR /&gt;
7 5/13/14 11:51:30.000 AM &lt;BR /&gt;
10 5/13/14 11:51:15.000 AM&lt;/P&gt;</description>
      <pubDate>Tue, 13 May 2014 23:48:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/ps-sos-ps1-Microsoft-PowerShell-Commands-WriteErrorException/m-p/161130#M14927</guid>
      <dc:creator>dlpco</dc:creator>
      <dc:date>2014-05-13T23:48:41Z</dc:date>
    </item>
    <item>
      <title>Re: ps_sos.ps1 Microsoft.PowerShell.Commands.WriteErrorException</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/ps-sos-ps1-Microsoft-PowerShell-Commands-WriteErrorException/m-p/161131#M14928</link>
      <description>&lt;P&gt;Yes indeed! Thank you, I'll take a look.&lt;/P&gt;</description>
      <pubDate>Wed, 14 May 2014 00:02:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/ps-sos-ps1-Microsoft-PowerShell-Commands-WriteErrorException/m-p/161131#M14928</guid>
      <dc:creator>hexx</dc:creator>
      <dc:date>2014-05-14T00:02:45Z</dc:date>
    </item>
    <item>
      <title>Re: ps_sos.ps1 Microsoft.PowerShell.Commands.WriteErrorException</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/ps-sos-ps1-Microsoft-PowerShell-Commands-WriteErrorException/m-p/161132#M14929</link>
      <description>&lt;P&gt;&lt;STRONG&gt;UPDATE&lt;/STRONG&gt;: This defect is now fixed as of S.o.S 3.2.1 / S.o.S TA for Windows 2.3.4&lt;/P&gt;

&lt;HR /&gt;

&lt;P&gt;Thank you for digging for the information I requested.&lt;/P&gt;

&lt;P&gt;This is a resurgence of a bug I thought I had squashed in version 3.2 (internal reference: SUP-812). This new iteration is on file as product defect SOS-11.&lt;/P&gt;

&lt;P&gt;The issue is that the &lt;CODE&gt;ps_sos.ps1&lt;/CODE&gt; scripted input first collects a list of PIDs to report on, and then walks through that list one by one to collect additional information - most notably the ARGS and pctCPU fields.&lt;/P&gt;

&lt;P&gt;Sometimes, the process ends between the time when we establish the list and the time when we get to the actual process for further introspection.&lt;/P&gt;

&lt;P&gt;Note that we see the string &lt;CODE&gt;System.Object[]&lt;/CODE&gt; as a value for ARGS for 4 processes in your output:&lt;BR /&gt;
&lt;PRE&gt;&lt;BR /&gt;
3908                  22556      88008      0-0:0:30           splunkd    System.Object[]&lt;BR /&gt;
4064                  22572      88008      0-0:0:30           splunkd    System.Object[]&lt;BR /&gt;
4944                  24284      90056      0-0:0:30           splunkd    System.Object[]&lt;BR /&gt;
7180                  24456      90056      0-0:0:21           splunkd    System.Object[]&lt;BR /&gt;
&lt;/PRE&gt;&lt;/P&gt;

&lt;P&gt;From the previous event, we know that these PIDs correspond to ad-hoc real-time searches:&lt;BR /&gt;
&lt;PRE&gt;&lt;BR /&gt;
3908       0          22428      88008      0-0:0:2            splunkd    search_--id=rt_1400007076.28_--maxbuckets=300_--ttl=600_--maxout=100000_--maxtime=0_--lookups=1_--reduce_freq=10_--rf=*&lt;BR /&gt;
4064       0          22564      88008      0-0:0:3            splunkd    search_--id=rt_1400007076.29_--maxbuckets=300_--ttl=600_--maxout=100000_--maxtime=0_--lookups=1_--reduce_freq=10_--rf=*&lt;BR /&gt;
4944       0          22284      88008      0-0:0:5            splunkd    search_--id=rt_1400007074.26_--maxbuckets=300_--ttl=600_--maxout=100000_--maxtime=0_--lookups=1_--reduce_freq=10_--rf=*&lt;BR /&gt;
7180       0          22448      88008      0-0:0:3            splunkd    search_--id=rt_1400007076.27_--maxbuckets=300_--ttl=600_--maxout=100000_--maxtime=0_--lookups=1_--reduce_freq=10_--rf=*&lt;BR /&gt;
&lt;/PRE&gt;&lt;/P&gt;

&lt;P&gt;It seems likely that these processes ended between the time that ps_sos.ps1 established a list of relevant processes, and the time it prodded each of these processes in turn to retrieve ARGS and pctCPU.&lt;/P&gt;

&lt;P&gt;In fixing this bug, we will evaluate process entries before printing them and do one of two things:&lt;BR /&gt;
 * Do not print out any entries for which we failed to retrieve ARGS or pctCPU because the process disappeared mid-execution&lt;BR /&gt;
 * Keep the script output as it is, but deal with the error more gracefully by suppressing it, avoiding the pollution of splunkd.log&lt;/P&gt;

&lt;P&gt;The bottom line is: We will fix it in a future version of the S.o.S app, but for the time being you can ignore these errors in splunkd.log and consider them benign.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 16:36:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/ps-sos-ps1-Microsoft-PowerShell-Commands-WriteErrorException/m-p/161132#M14929</guid>
      <dc:creator>hexx</dc:creator>
      <dc:date>2020-09-28T16:36:21Z</dc:date>
    </item>
    <item>
      <title>Re: ps_sos.ps1 Microsoft.PowerShell.Commands.WriteErrorException</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/ps-sos-ps1-Microsoft-PowerShell-Commands-WriteErrorException/m-p/161133#M14930</link>
      <description>&lt;P&gt;Sounds like a plan. I noticed that most things have 0%cpu but the elapsed seem to be correct.&lt;/P&gt;

&lt;P&gt;Seems to be a good answer - you have any idea when the update will come out?&lt;/P&gt;</description>
      <pubDate>Wed, 14 May 2014 08:12:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/ps-sos-ps1-Microsoft-PowerShell-Commands-WriteErrorException/m-p/161133#M14930</guid>
      <dc:creator>dlpco</dc:creator>
      <dc:date>2014-05-14T08:12:56Z</dc:date>
    </item>
    <item>
      <title>Re: ps_sos.ps1 Microsoft.PowerShell.Commands.WriteErrorException</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/ps-sos-ps1-Microsoft-PowerShell-Commands-WriteErrorException/m-p/161134#M14931</link>
      <description>&lt;P&gt;We just released S.o.S 3.2, so it won't be for a few weeks at the very least, possibly a few months.&lt;/P&gt;</description>
      <pubDate>Thu, 15 May 2014 05:57:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/ps-sos-ps1-Microsoft-PowerShell-Commands-WriteErrorException/m-p/161134#M14931</guid>
      <dc:creator>hexx</dc:creator>
      <dc:date>2014-05-15T05:57:13Z</dc:date>
    </item>
    <item>
      <title>Re: ps_sos.ps1 Microsoft.PowerShell.Commands.WriteErrorException</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/ps-sos-ps1-Microsoft-PowerShell-Commands-WriteErrorException/m-p/161135#M14932</link>
      <description>&lt;P&gt;I just updated to S.o.S 3.2.1 but am still seeing these errors pretty often... &lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;P&gt;E:\Program&lt;BR /&gt;
Files\Splunk\etc\apps\TA-sos_win\bin\powershell\ps_sos.ps1&lt;BR /&gt;
: Exception of type&lt;BR /&gt;
'Microsoft.PowerShell.Commands.WriteErrorException'&lt;BR /&gt;
was thrown. At line:1 char:1&lt;BR /&gt;
+ . 'E:\Program Files\Splunk\etc\apps\TA-sos_win\bin\powershell\ps_sos.ps1'&lt;BR /&gt;
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~&lt;BR /&gt;
    + CategoryInfo          : NotSpecified: (:) [Write-Error],&lt;BR /&gt;
WriteErrorException&lt;BR /&gt;
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,ps_sos.ps1&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;</description>
      <pubDate>Mon, 28 Sep 2020 19:04:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/ps-sos-ps1-Microsoft-PowerShell-Commands-WriteErrorException/m-p/161135#M14932</guid>
      <dc:creator>brooklynotss</dc:creator>
      <dc:date>2020-09-28T19:04:12Z</dc:date>
    </item>
    <item>
      <title>Re: ps_sos.ps1 Microsoft.PowerShell.Commands.WriteErrorException</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/ps-sos-ps1-Microsoft-PowerShell-Commands-WriteErrorException/m-p/161136#M14933</link>
      <description>&lt;P&gt;marked as answered, cool?&lt;/P&gt;</description>
      <pubDate>Mon, 02 Mar 2015 15:49:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/ps-sos-ps1-Microsoft-PowerShell-Commands-WriteErrorException/m-p/161136#M14933</guid>
      <dc:creator>halr9000</dc:creator>
      <dc:date>2015-03-02T15:49:42Z</dc:date>
    </item>
  </channel>
</rss>

