<?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: Errors in Syslog in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/errors-in-syslog/m-p/4445674#M358048</link>
    <description>Hi Arun,&lt;BR /&gt;&lt;BR /&gt;Detailed information you could find in /var/opt/resmon/log/event.log about the errors.</description>
    <pubDate>Wed, 24 Jun 2009 10:46:50 GMT</pubDate>
    <dc:creator>Ganesan R</dc:creator>
    <dc:date>2009-06-24T10:46:50Z</dc:date>
    <item>
      <title>Errors in Syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/errors-in-syslog/m-p/4445671#M358045</link>
      <description>Hi All,&lt;BR /&gt;&lt;BR /&gt;I have HP rp5470 server connected with IBM DS4800 Storage. Daily we perform LUN copy activity on this machine from storage.&lt;BR /&gt;yesterday night syslog stored some errors that are following... Please suggest&lt;BR /&gt;===============================================&lt;BR /&gt;DIAGNOSTIC SYSTEM WARNING:&lt;BR /&gt;in stm to start it.&lt;BR /&gt;If the diaglogd daemon is active, use the logtool utility in stm to determine which I/O subsystem is logging excessive errors.&lt;BR /&gt;DIAGNOSTIC SYSTEM WARNING:&lt;BR /&gt;The diagnostic logging facility is no longer receiving excessive errors from the I/O subsystem.  2 I/O error entries were lost. The diagnostic logging facility has started receiving excessive errors from the I/O subsystem.  I/O error entries will be lost until the cause of the excessive I/O logging is corrected.&lt;BR /&gt;===========================================&lt;BR /&gt;&lt;BR /&gt;Best regards:&lt;BR /&gt;Arun Jain</description>
      <pubDate>Wed, 24 Jun 2009 02:51:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/errors-in-syslog/m-p/4445671#M358045</guid>
      <dc:creator>Arun Jain</dc:creator>
      <dc:date>2009-06-24T02:51:03Z</dc:date>
    </item>
    <item>
      <title>Re: Errors in Syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/errors-in-syslog/m-p/4445672#M358046</link>
      <description>What this usually means is that a device has started reporting I/O errors faster than dialogd can deal with them.&lt;BR /&gt;&lt;BR /&gt;Normally, you would need to do what it suggests to identify what the hardware causing the problem is:&lt;BR /&gt;use the logtool utility in stm&lt;BR /&gt;to determine which I/O subsystem is logging excessive errors.&lt;BR /&gt;&lt;BR /&gt;Back up your data, take this system out of production if possible and consult HP or IBM  hardware even if you pay time and materials.&lt;BR /&gt;&lt;BR /&gt;You could have a bad disk.&lt;BR /&gt;You could have a bad scsi controller.&lt;BR /&gt;You could have a bad terminator on a scsi device.&lt;BR /&gt;You could have a bad cable&lt;BR /&gt;You could have a bad drive cage(if applicable).</description>
      <pubDate>Wed, 24 Jun 2009 03:32:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/errors-in-syslog/m-p/4445672#M358046</guid>
      <dc:creator>Jeeshan</dc:creator>
      <dc:date>2009-06-24T03:32:48Z</dc:date>
    </item>
    <item>
      <title>Re: Errors in Syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/errors-in-syslog/m-p/4445673#M358047</link>
      <description>Hi Arun,&lt;BR /&gt;&lt;BR /&gt;Please try to run the complete command , Which the EMS will provie you in the syslog , like the one below&lt;BR /&gt;&lt;BR /&gt;Jun 24 04:00:29 Test EMS [5069]: ------ EMS Event Notification ------   Value:  MAJORWARNING (3)  for Resource:  /adapters/events/TL_adapter/1_0_2_0_0.25      (Threshold:  &amp;gt;=   3 )    Execute the following command to obtain event details:   /opt/resmon/bin/resdata -R 332215474 -r /adapters/events/TL_adapter/1_0_2_0_0.25 -n 332202588 -a &lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Jitesh</description>
      <pubDate>Wed, 24 Jun 2009 10:08:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/errors-in-syslog/m-p/4445673#M358047</guid>
      <dc:creator>Jitesh purohit_1</dc:creator>
      <dc:date>2009-06-24T10:08:48Z</dc:date>
    </item>
    <item>
      <title>Re: Errors in Syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/errors-in-syslog/m-p/4445674#M358048</link>
      <description>Hi Arun,&lt;BR /&gt;&lt;BR /&gt;Detailed information you could find in /var/opt/resmon/log/event.log about the errors.</description>
      <pubDate>Wed, 24 Jun 2009 10:46:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/errors-in-syslog/m-p/4445674#M358048</guid>
      <dc:creator>Ganesan R</dc:creator>
      <dc:date>2009-06-24T10:46:50Z</dc:date>
    </item>
  </channel>
</rss>

