<?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: CPU load High in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/cpu-load-high/m-p/4141305#M317680</link>
    <description>They are diagnostics daemons.  Stop and restart them:&lt;BR /&gt;&lt;BR /&gt;/sbin/init.d/diagnostic stop&lt;BR /&gt;/sbin/init.d/diagnostic start&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete</description>
    <pubDate>Wed, 06 Feb 2008 15:57:23 GMT</pubDate>
    <dc:creator>Pete Randall</dc:creator>
    <dc:date>2008-02-06T15:57:23Z</dc:date>
    <item>
      <title>CPU load High</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cpu-load-high/m-p/4141304#M317679</link>
      <description>I found the following processes running in the HP-UX 10.20 server&lt;BR /&gt;&lt;BR /&gt;CPUload    processes   &lt;BR /&gt;89.76      diaglogd       &lt;BR /&gt;8.23       diagmond&lt;BR /&gt;&lt;BR /&gt;What are these processes?&lt;BR /&gt;As these processes are utilizing lot of CPU load,  I have taken charge of the setup recently so dont know much as of now.&lt;BR /&gt;&lt;BR /&gt;I would be greatful if you'll could help me out &lt;BR /&gt;&lt;BR /&gt;RG&lt;BR /&gt;sam</description>
      <pubDate>Wed, 06 Feb 2008 15:54:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cpu-load-high/m-p/4141304#M317679</guid>
      <dc:creator>sam_25_1</dc:creator>
      <dc:date>2008-02-06T15:54:15Z</dc:date>
    </item>
    <item>
      <title>Re: CPU load High</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cpu-load-high/m-p/4141305#M317680</link>
      <description>They are diagnostics daemons.  Stop and restart them:&lt;BR /&gt;&lt;BR /&gt;/sbin/init.d/diagnostic stop&lt;BR /&gt;/sbin/init.d/diagnostic start&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Wed, 06 Feb 2008 15:57:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cpu-load-high/m-p/4141305#M317680</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2008-02-06T15:57:23Z</dc:date>
    </item>
    <item>
      <title>Re: CPU load High</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cpu-load-high/m-p/4141306#M317681</link>
      <description>Hi ,&lt;BR /&gt;Thanks a lot for your speedy reply.&lt;BR /&gt;I sincerely appreciate it.&lt;BR /&gt;At the moment diaglogd daemon is showing 93% at this moment. if i stop and start will it affect any other running processes. how could we get it down permanently.&lt;BR /&gt;&lt;BR /&gt;Hope to hear from u soon.&lt;BR /&gt;&lt;BR /&gt;SAM.</description>
      <pubDate>Wed, 06 Feb 2008 16:01:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cpu-load-high/m-p/4141306#M317681</guid>
      <dc:creator>sam_25_1</dc:creator>
      <dc:date>2008-02-06T16:01:59Z</dc:date>
    </item>
    <item>
      <title>Re: CPU load High</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cpu-load-high/m-p/4141307#M317682</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;This is likely fixed in a patch update. Though your system is out of support, you can get the last bi-annual 10.20 patch from this site:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www12.itrc.hp.com/service/patch/mainPage.do" target="_blank"&gt;http://www12.itrc.hp.com/service/patch/mainPage.do&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;You may need to search and add patches for the diagnostic subsystem in addition.&lt;BR /&gt;&lt;BR /&gt;If possible, I recommend the ftp script method of patch download.&lt;BR /&gt;&lt;BR /&gt;I'd also recommend replacing the system at some point with something that has OS and hardware support.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 06 Feb 2008 16:36:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cpu-load-high/m-p/4141307#M317682</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2008-02-06T16:36:26Z</dc:date>
    </item>
    <item>
      <title>Re: CPU load High</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cpu-load-high/m-p/4141308#M317683</link>
      <description>Sam,&lt;BR /&gt;&lt;BR /&gt;No harm in stopping/restarting, at least in my experience.  I have seen the exact same circumstances where the diag processes are consuming massive amounts of CPU.  Stopping and restarting them restores them to a normal state  and their CPU usage also returns to normal.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Wed, 06 Feb 2008 16:41:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cpu-load-high/m-p/4141308#M317683</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2008-02-06T16:41:32Z</dc:date>
    </item>
    <item>
      <title>Re: CPU load High</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cpu-load-high/m-p/4141309#M317684</link>
      <description>I stopped and started the diagnostic tool but still %cpu is 96 for the process from top command, what is the consequence of this ?&lt;BR /&gt;&lt;BR /&gt;what is the Dianostic tool used for ?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;SAM</description>
      <pubDate>Wed, 06 Feb 2008 18:25:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cpu-load-high/m-p/4141309#M317684</guid>
      <dc:creator>sam_25_1</dc:creator>
      <dc:date>2008-02-06T18:25:54Z</dc:date>
    </item>
    <item>
      <title>Re: CPU load High</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cpu-load-high/m-p/4141310#M317685</link>
      <description>It monitors hardware state in order to notify you of a problem.  Maybe you have an issue with your hardware which is causing diagnostics to run so much.  Any yellow lights appearing on your server or its associated hardware?  Any messages in syslog?  In dmesg output?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Wed, 06 Feb 2008 18:36:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cpu-load-high/m-p/4141310#M317685</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2008-02-06T18:36:09Z</dc:date>
    </item>
    <item>
      <title>Re: CPU load High</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cpu-load-high/m-p/4141311#M317686</link>
      <description>Hi Pete,&lt;BR /&gt;&lt;BR /&gt;Thanks a lot for your inputs. I tried the dmesg and got the following message. &lt;BR /&gt;DIAGNOSTIC SYSTEM WARNING:&lt;BR /&gt;   The diagnostic logging facility has started receiving excessive&lt;BR /&gt;   errors from the I/O subsystem.  I/O error entries will be lost&lt;BR /&gt;   until the cause of the excessive I/O logging is corrected.&lt;BR /&gt;   If the DEMLOG daemon is not active, use the DIAGSYSTEM command&lt;BR /&gt;   in SYSDIAG to start it.&lt;BR /&gt;   If the DEMLOG daemon is active, use the LOGTOOL utility in SYSDIAG&lt;BR /&gt;   to determine which I/O subsystem is logging excessive errors.&lt;BR /&gt;&lt;BR /&gt;sysmap: rmap ovflo, lost [44586l,44639l)&lt;BR /&gt;sysmap: rmap ovflo, lost [44584l,44585l)&lt;BR /&gt;sysmap: rmap ovflo, lost [44570l,44571l)&lt;BR /&gt;sysmap: rmap ovflo, lost [44567l,44568l)&lt;BR /&gt;sysmap: rmap ovflo, lost [44554l,44558l)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;The top command displays the follwoing output&lt;BR /&gt;&lt;BR /&gt;System:                                    Wed Feb  6 14:57:06 2008&lt;BR /&gt;Load averages: 0.75, 0.96, 1.14&lt;BR /&gt;472 processes: 470 sleeping, 2 running&lt;BR /&gt;Cpu states:&lt;BR /&gt;CPU   LOAD   USER   NICE    SYS   IDLE  BLOCK  SWAIT   INTR   SSYS&lt;BR /&gt; 0    0.70  40.8%   0.0%  37.3%  21.9%      0.0%   0.0%   0.0%   0.0%&lt;BR /&gt; 1    0.81  25.1%   0.0%  58.8%  16.1%   0.0%   0.0%   0.0%   0.0%&lt;BR /&gt;---   ----  -----  -----  -----  -----  -----  -----  -----  -----&lt;BR /&gt;avg   0.75  33.0%   0.0%  48.1%  18.9%   0.0%   0.0%   0.0%   0.0%&lt;BR /&gt;&lt;BR /&gt;Memory: 227020K (36584K) real, 253440K (55816K) virtual, 21172K free  Page# 1/11&lt;BR /&gt;&lt;BR /&gt;CPU TTY   PID USERNAME PRI NI   SIZE    RES STATE    TIME %WCPU  %CPU COMMAND&lt;BR /&gt; 1 rroot 28573 root     218 10   252K   228K run    188:53 99.61 99.43 diaglogd&lt;BR /&gt; 0 pty/ttyq8 23727 dikunj   148 20  5684K  2472K sleep    0:44 11.71 11.69 _progres&lt;BR /&gt; 0 rroot 27942 root     154 10   248K   320K sleep   15:52  8.60  8.59 diagmond&lt;BR /&gt;&lt;BR /&gt;This is the output of the syslog command &lt;BR /&gt;&lt;BR /&gt;  6 10:38:29 server1 sshd[5024]: Bad protocol version identification 'Big-Brother-Monitor-1.9i' from 172.16.18.98&lt;BR /&gt;Feb  6 10:43:32 server1 sshd[6610]: Bad protocol version identification 'Big-Brother-Monitor-1.9i' from 172.16.18.98&lt;BR /&gt;Feb  6 10:48:33  sshd[8315]: Bad protocol version identification 'Big-Brother-Monitor-1.9i' from 172.16.18.98&lt;BR /&gt;Feb  6 10:53:32 server1  sshd[10502]: Bad protocol version identification 'Big-Brother-Monitor-1.9i' from 172.16.18.98&lt;BR /&gt;Feb  6 10:58:30 server1 sshd[13161]: Bad protocol version identification 'Big-Brother-Monitor-1.9i' from 172.16.18.98&lt;BR /&gt;Feb  6 11:03:31 server1 sshd[14874]: Bad protocol version identification 'Big-Brother-Monitor-1.9i' from 172.16.18.98&lt;BR /&gt;Feb  6 11:08:29 server1 sshd[16978]: Bad protocol version identification 'Big-Brother-Monitor-1.9i' from 172.16.18.98&lt;BR /&gt;&lt;BR /&gt;Please help me out, thanks once again for your speedy reply.. &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 06 Feb 2008 20:04:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cpu-load-high/m-p/4141311#M317686</guid>
      <dc:creator>sam_25_1</dc:creator>
      <dc:date>2008-02-06T20:04:34Z</dc:date>
    </item>
  </channel>
</rss>

