<?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: Time Processor failed? in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/time-processor-failed/m-p/4061068#M68847</link>
    <description>hi kelly &lt;BR /&gt;&lt;BR /&gt;did you get this issue resolved?&lt;BR /&gt;&lt;BR /&gt;regards</description>
    <pubDate>Wed, 30 Apr 2008 23:17:44 GMT</pubDate>
    <dc:creator>KarloChacon</dc:creator>
    <dc:date>2008-04-30T23:17:44Z</dc:date>
    <item>
      <title>Time Processor failed?</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/time-processor-failed/m-p/4061064#M68843</link>
      <description>I got the following event from Insight Manager and before I could even start troubleshooting, the error corrected itself.  What does it mean and how would I have corrected it?&lt;BR /&gt;^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^&lt;BR /&gt;Event Name: Processor Time Failed (19002)&lt;BR /&gt;URL: https://gisserver:2381/&lt;BR /&gt;Event originator: gisserver&lt;BR /&gt;Event Severity: Critical&lt;BR /&gt;Event received: 27-Aug-2007, 14:09:22&lt;BR /&gt; &lt;BR /&gt;Event description: The Processor Time performance property is set to critical.&lt;BR /&gt; &lt;BR /&gt;OS Cache Instance: 0&lt;BR /&gt;Percent Cpu Time: 95&lt;BR /&gt;^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^&lt;BR /&gt;&lt;BR /&gt;Thank you!&lt;BR /&gt;KBeauchaine</description>
      <pubDate>Mon, 27 Aug 2007 14:24:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/time-processor-failed/m-p/4061064#M68843</guid>
      <dc:creator>Kelly Beauchaine</dc:creator>
      <dc:date>2007-08-27T14:24:27Z</dc:date>
    </item>
    <item>
      <title>Re: Time Processor failed?</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/time-processor-failed/m-p/4061065#M68844</link>
      <description>Hello Kelly,&lt;BR /&gt;&lt;BR /&gt;Microsoft Windows Event ID and SNMP Traps Reference Guide:&lt;BR /&gt;&lt;A href="http://h50177.www5.hp.com/FILE/74746/74746.pdf" target="_blank"&gt;http://h50177.www5.hp.com/FILE/74746/74746.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Page 14 of 137:&lt;BR /&gt;Log Message: The Processor Performance Instance, '%4' is failed with Processor Time of %5 percent&lt;BR /&gt;&lt;BR /&gt;This event should be logged when Percent Cpu Time reaches 95++&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Tue, 28 Aug 2007 09:54:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/time-processor-failed/m-p/4061065#M68844</guid>
      <dc:creator>TY 007</dc:creator>
      <dc:date>2007-08-28T09:54:19Z</dc:date>
    </item>
    <item>
      <title>Re: Time Processor failed?</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/time-processor-failed/m-p/4061066#M68845</link>
      <description>Thanks.  I disabled a service I had running on it called Diskeeper.  Ever since, there have been no errors.  The Diskeeper application is only supposed to use idle resources, and it's been running on this server for over two months now.  Not sure why all of sudden I would start getting these errors.  Is there a way to positively identify what process is causing the threshold to rise like this?&lt;BR /&gt;K</description>
      <pubDate>Tue, 28 Aug 2007 10:23:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/time-processor-failed/m-p/4061066#M68845</guid>
      <dc:creator>Kelly Beauchaine</dc:creator>
      <dc:date>2007-08-28T10:23:13Z</dc:date>
    </item>
    <item>
      <title>Re: Time Processor failed?</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/time-processor-failed/m-p/4061067#M68846</link>
      <description>Ahhhhh!  It's happening again even though I disabled what I thought was the cause.  It must have spiked briefly though because when I checked the system homepage it didn't show any errors.  Is there a way to determine what is causing this?  &lt;BR /&gt;Thanks!</description>
      <pubDate>Fri, 31 Aug 2007 09:36:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/time-processor-failed/m-p/4061067#M68846</guid>
      <dc:creator>Kelly Beauchaine</dc:creator>
      <dc:date>2007-08-31T09:36:45Z</dc:date>
    </item>
    <item>
      <title>Re: Time Processor failed?</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/time-processor-failed/m-p/4061068#M68847</link>
      <description>hi kelly &lt;BR /&gt;&lt;BR /&gt;did you get this issue resolved?&lt;BR /&gt;&lt;BR /&gt;regards</description>
      <pubDate>Wed, 30 Apr 2008 23:17:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/time-processor-failed/m-p/4061068#M68847</guid>
      <dc:creator>KarloChacon</dc:creator>
      <dc:date>2008-04-30T23:17:44Z</dc:date>
    </item>
    <item>
      <title>Re: Time Processor failed?</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/time-processor-failed/m-p/4061069#M68848</link>
      <description>I did not get this issue resolved, but I no longer am having the issue either!  I'm not sure what ever was causing this or how it resolved itself.  Still a mystery to me!</description>
      <pubDate>Thu, 01 May 2008 11:21:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/time-processor-failed/m-p/4061069#M68848</guid>
      <dc:creator>Kelly Beauchaine</dc:creator>
      <dc:date>2008-05-01T11:21:35Z</dc:date>
    </item>
  </channel>
</rss>

