<?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 DIAGNOSTIC SYSTEM WARNING in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/diagnostic-system-warning/m-p/4397510#M351111</link>
    <description>Plz help me to find out what is the real warning:&lt;BR /&gt;Mar 28 03:26:51 server01 vmunix: DIAGNOSTIC SYSTEM WARNING:&lt;BR /&gt;Mar 28 03:26:51 server01 vmunix:    The diagnostic logging facility has started receiving excessive&lt;BR /&gt;Mar 28 03:26:51 server01 vmunix:    errors from the I/O subsystem.  I/O error entries will be lost&lt;BR /&gt;Mar 28 03:26:51 server01 vmunix:    until the cause of the excessive I/O logging is corrected.&lt;BR /&gt;Mar 28 03:26:51 server01 vmunix:    If the diaglogd daemon is not active, use the Daemon Startup command&lt;BR /&gt;Mar 28 03:26:51 server01 vmunix:    in stm to start it.&lt;BR /&gt;Mar 28 03:26:51 server01 vmunix:    If the diaglogd daemon is active, use the logtool utility in stm&lt;BR /&gt;Mar 28 03:26:51 server01 vmunix:    to determine which I/O subsystem is logging excessive errors.&lt;BR /&gt;Mar 28 03:26:51 server01 vmunix: DIAGNOSTIC SYSTEM WARNING:&lt;BR /&gt;Mar 28 03:26:51 server01 vmunix:    The diagnostic logging facility is no longer receiving excessive&lt;BR /&gt;Mar 28 03:26:51 server01 vmunix:    errors from the I/O subsystem.  5 I/O error entries were lost.&lt;BR /&gt;Mar 28 03:26:51 server01 vmunix:    The diagnostic logging facility has started receiving excessive&lt;BR /&gt;Mar 28 03:26:51 server01 vmunix:    errors from the I/O subsystem.  I/O error entries will be lost&lt;BR /&gt;Mar 28 03:26:51 server01 vmunix:    until the cause of the excessive I/O logging is corrected.&lt;BR /&gt;&lt;BR /&gt;Thanks in Advance</description>
    <pubDate>Wed, 08 Apr 2009 09:42:37 GMT</pubDate>
    <dc:creator>rana sarkar</dc:creator>
    <dc:date>2009-04-08T09:42:37Z</dc:date>
    <item>
      <title>DIAGNOSTIC SYSTEM WARNING</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/diagnostic-system-warning/m-p/4397510#M351111</link>
      <description>Plz help me to find out what is the real warning:&lt;BR /&gt;Mar 28 03:26:51 server01 vmunix: DIAGNOSTIC SYSTEM WARNING:&lt;BR /&gt;Mar 28 03:26:51 server01 vmunix:    The diagnostic logging facility has started receiving excessive&lt;BR /&gt;Mar 28 03:26:51 server01 vmunix:    errors from the I/O subsystem.  I/O error entries will be lost&lt;BR /&gt;Mar 28 03:26:51 server01 vmunix:    until the cause of the excessive I/O logging is corrected.&lt;BR /&gt;Mar 28 03:26:51 server01 vmunix:    If the diaglogd daemon is not active, use the Daemon Startup command&lt;BR /&gt;Mar 28 03:26:51 server01 vmunix:    in stm to start it.&lt;BR /&gt;Mar 28 03:26:51 server01 vmunix:    If the diaglogd daemon is active, use the logtool utility in stm&lt;BR /&gt;Mar 28 03:26:51 server01 vmunix:    to determine which I/O subsystem is logging excessive errors.&lt;BR /&gt;Mar 28 03:26:51 server01 vmunix: DIAGNOSTIC SYSTEM WARNING:&lt;BR /&gt;Mar 28 03:26:51 server01 vmunix:    The diagnostic logging facility is no longer receiving excessive&lt;BR /&gt;Mar 28 03:26:51 server01 vmunix:    errors from the I/O subsystem.  5 I/O error entries were lost.&lt;BR /&gt;Mar 28 03:26:51 server01 vmunix:    The diagnostic logging facility has started receiving excessive&lt;BR /&gt;Mar 28 03:26:51 server01 vmunix:    errors from the I/O subsystem.  I/O error entries will be lost&lt;BR /&gt;Mar 28 03:26:51 server01 vmunix:    until the cause of the excessive I/O logging is corrected.&lt;BR /&gt;&lt;BR /&gt;Thanks in Advance</description>
      <pubDate>Wed, 08 Apr 2009 09:42:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/diagnostic-system-warning/m-p/4397510#M351111</guid>
      <dc:creator>rana sarkar</dc:creator>
      <dc:date>2009-04-08T09:42:37Z</dc:date>
    </item>
    <item>
      <title>Re: DIAGNOSTIC SYSTEM WARNING</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/diagnostic-system-warning/m-p/4397511#M351112</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;Pls chk,&lt;BR /&gt;#dmesg&lt;BR /&gt;#/var/opt/resmon/log/event.log&lt;BR /&gt;&lt;BR /&gt;-Ram</description>
      <pubDate>Sat, 11 Apr 2009 05:20:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/diagnostic-system-warning/m-p/4397511#M351112</guid>
      <dc:creator>Ramesh S</dc:creator>
      <dc:date>2009-04-11T05:20:08Z</dc:date>
    </item>
    <item>
      <title>Re: DIAGNOSTIC SYSTEM WARNING</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/diagnostic-system-warning/m-p/4397512#M351113</link>
      <description>Hi RanaSarkar,&lt;BR /&gt;&lt;BR /&gt;Just do a &lt;BR /&gt;ioscan -fnC disk&lt;BR /&gt;to find the disk in that path.&lt;BR /&gt;&lt;BR /&gt;Doing a ioscan should log messages into syslog.log file.&lt;BR /&gt;&lt;BR /&gt;Is not the error info but the data that was being moved when the error occured.&lt;BR /&gt;1. Backup this disks data.&lt;BR /&gt;2. Watch it very closely.&lt;BR /&gt;3. Have a disk ready to replace it.&lt;BR /&gt;&lt;BR /&gt;Rgds//&lt;BR /&gt;Taifur&lt;BR /&gt;</description>
      <pubDate>Sat, 11 Apr 2009 06:51:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/diagnostic-system-warning/m-p/4397512#M351113</guid>
      <dc:creator>Taifur</dc:creator>
      <dc:date>2009-04-11T06:51:39Z</dc:date>
    </item>
  </channel>
</rss>

