<?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: High load average &amp;amp; a root d3 process in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average-amp-a-root-d3-process/m-p/4604089#M376124</link>
    <description>He # ps -ef|grep 1232&lt;BR /&gt;    root  1232     1  0  Jan 24  ?         1:23 /usr/sbin/inetd&lt;BR /&gt;    root  4488 29527  0 14:38:35 ttyp4     0:00 grep 1232&lt;BR /&gt;    root  2374  1232  0  Jan 24  ?         0:00 /etc/opt/resmon/lbin/registrar&lt;BR /&gt;    root 27348  1232  0 10:25:23 ?         0:00 -d3&lt;BR /&gt;    root 20127  1232  0 09:30:34 ?         0:00 -d3&lt;BR /&gt;    root 17309  1232  0 09:13:30 ?         0:00 -d3&lt;BR /&gt;    root 28205  1232  0 13:57:14 ?         0:00 -d3&lt;BR /&gt;    root 26099  1232  0 13:43:13 ?         0:00 -d3&lt;BR /&gt;    root  3947  1232  0 14:35:37 ?         0:00 -d3&lt;BR /&gt;    root 11251  1232  0 08:42:01 ?         0:00 -d3&lt;BR /&gt;    root 11362  1232  0 08:42:29 ?         0:00 -d3&lt;BR /&gt;    root 18244  1232  0 09:19:01 ?         0:00 -d3&lt;BR /&gt;    root  8167  1232  0 08:17:27 ?         0:00 -d3&lt;BR /&gt;    root 28639  1232  0 14:00:05 ?         0:00 -d3&lt;BR /&gt;    root 22681  1232  0 13:18:00 ?         0:00 -d3&lt;BR /&gt;    root 23713  1232  0 13:25:12 ?         0:00 -d3&lt;BR /&gt;    root 19268  1232  0 09:25:54 ?         0:00 -d3&lt;BR /&gt;    root  6548  1232  0 08:08:43 ?         0:01 -d3&lt;BR /&gt;    root 17664  1232  0 09:14:39 ?         0:00 -d3&lt;BR /&gt;    root  7933  1232  0 08:16:43 ?         0:00 -d3&lt;BR /&gt;    root  9317  1232  0 08:27:10 ?         0:00 -d3&lt;BR /&gt;    root 15563  1232  0 12:38:26 ?         0:01 -d3&lt;BR /&gt;    root 21773  1232  0 09:43:14 ?         0:00 -d3&lt;BR /&gt;    root  1502  1232  0 14:19:25 ?         0:00 -d3&lt;BR /&gt;    root 19692  1232  0 09:28:15 ?         0:00 -d3&lt;BR /&gt;    root  7619  1232  0 08:14:51 ?         0:00 -d3&lt;BR /&gt;    root 16442  1232  0 12:42:56 ?         0:00 -d3&lt;BR /&gt;    root 13558  1232  0 08:51:59 ?         0:00 -d3&lt;BR /&gt;    root 14146  1232  0 08:55:12 ?         0:00 -d3&lt;BR /&gt;    root 10656  1232  0 08:37:07 ?         0:00 -d3&lt;BR /&gt;    root  8087  1232  0 08:17:05 ?         0:00 -d3&lt;BR /&gt;    root  3763  1232 255  Jan 31  ?        63414:03 -d3&lt;BR /&gt;    root 10144  1232  0 08:33:40 ?         0:02 -d3&lt;BR /&gt;    root  5640  1232  0 08:03:03 ?         0:00 -d3&lt;BR /&gt;    root  7715  1232  0 08:15:26 ?         0:00 -d3&lt;BR /&gt;    root  1592  1232  0 14:19:44 ?         0:00 -d3&lt;BR /&gt;    root 10262  1232  0 08:33:49 ?         0:00 -d3&lt;BR /&gt;    root  6323  1232  0 08:07:22 ?         0:00 -d3&lt;BR /&gt;&lt;BR /&gt;It looks like whatever it is, it just keeps running today over &amp;amp; over. Is it safe to kill them all?</description>
    <pubDate>Fri, 19 Mar 2010 18:33:44 GMT</pubDate>
    <dc:creator>SandiC</dc:creator>
    <dc:date>2010-03-19T18:33:44Z</dc:date>
    <item>
      <title>High load average &amp; a root d3 process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average-amp-a-root-d3-process/m-p/4604085#M376120</link>
      <description>What is the d3 or d3 _slave process? I haven't noticed this before but today it's showing up as my top process under the user root &amp;amp; my load averages are unusually high for the number of users I have on the system.&lt;BR /&gt;&lt;BR /&gt;Thanks in Advance!&lt;BR /&gt;SandiC</description>
      <pubDate>Fri, 19 Mar 2010 17:34:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average-amp-a-root-d3-process/m-p/4604085#M376120</guid>
      <dc:creator>SandiC</dc:creator>
      <dc:date>2010-03-19T17:34:28Z</dc:date>
    </item>
    <item>
      <title>Re: High load average &amp; a root d3 process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average-amp-a-root-d3-process/m-p/4604086#M376121</link>
      <description>what is your OS? what is its PPID?</description>
      <pubDate>Fri, 19 Mar 2010 17:47:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average-amp-a-root-d3-process/m-p/4604086#M376121</guid>
      <dc:creator>John Guster</dc:creator>
      <dc:date>2010-03-19T17:47:43Z</dc:date>
    </item>
    <item>
      <title>Re: High load average &amp; a root d3 process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average-amp-a-root-d3-process/m-p/4604087#M376122</link>
      <description>Sorry for leaving that out! Running HPUX 11.31 on a rp4440 pa-risc. The ppid is showing 1232 for all of them. Could this be from a remote login that was dropped?</description>
      <pubDate>Fri, 19 Mar 2010 17:54:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average-amp-a-root-d3-process/m-p/4604087#M376122</guid>
      <dc:creator>SandiC</dc:creator>
      <dc:date>2010-03-19T17:54:54Z</dc:date>
    </item>
    <item>
      <title>Re: High load average &amp; a root d3 process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average-amp-a-root-d3-process/m-p/4604088#M376123</link>
      <description>do ps -ef|grep 1232 to see what is the command associate with.</description>
      <pubDate>Fri, 19 Mar 2010 18:22:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average-amp-a-root-d3-process/m-p/4604088#M376123</guid>
      <dc:creator>John Guster</dc:creator>
      <dc:date>2010-03-19T18:22:07Z</dc:date>
    </item>
    <item>
      <title>Re: High load average &amp; a root d3 process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average-amp-a-root-d3-process/m-p/4604089#M376124</link>
      <description>He # ps -ef|grep 1232&lt;BR /&gt;    root  1232     1  0  Jan 24  ?         1:23 /usr/sbin/inetd&lt;BR /&gt;    root  4488 29527  0 14:38:35 ttyp4     0:00 grep 1232&lt;BR /&gt;    root  2374  1232  0  Jan 24  ?         0:00 /etc/opt/resmon/lbin/registrar&lt;BR /&gt;    root 27348  1232  0 10:25:23 ?         0:00 -d3&lt;BR /&gt;    root 20127  1232  0 09:30:34 ?         0:00 -d3&lt;BR /&gt;    root 17309  1232  0 09:13:30 ?         0:00 -d3&lt;BR /&gt;    root 28205  1232  0 13:57:14 ?         0:00 -d3&lt;BR /&gt;    root 26099  1232  0 13:43:13 ?         0:00 -d3&lt;BR /&gt;    root  3947  1232  0 14:35:37 ?         0:00 -d3&lt;BR /&gt;    root 11251  1232  0 08:42:01 ?         0:00 -d3&lt;BR /&gt;    root 11362  1232  0 08:42:29 ?         0:00 -d3&lt;BR /&gt;    root 18244  1232  0 09:19:01 ?         0:00 -d3&lt;BR /&gt;    root  8167  1232  0 08:17:27 ?         0:00 -d3&lt;BR /&gt;    root 28639  1232  0 14:00:05 ?         0:00 -d3&lt;BR /&gt;    root 22681  1232  0 13:18:00 ?         0:00 -d3&lt;BR /&gt;    root 23713  1232  0 13:25:12 ?         0:00 -d3&lt;BR /&gt;    root 19268  1232  0 09:25:54 ?         0:00 -d3&lt;BR /&gt;    root  6548  1232  0 08:08:43 ?         0:01 -d3&lt;BR /&gt;    root 17664  1232  0 09:14:39 ?         0:00 -d3&lt;BR /&gt;    root  7933  1232  0 08:16:43 ?         0:00 -d3&lt;BR /&gt;    root  9317  1232  0 08:27:10 ?         0:00 -d3&lt;BR /&gt;    root 15563  1232  0 12:38:26 ?         0:01 -d3&lt;BR /&gt;    root 21773  1232  0 09:43:14 ?         0:00 -d3&lt;BR /&gt;    root  1502  1232  0 14:19:25 ?         0:00 -d3&lt;BR /&gt;    root 19692  1232  0 09:28:15 ?         0:00 -d3&lt;BR /&gt;    root  7619  1232  0 08:14:51 ?         0:00 -d3&lt;BR /&gt;    root 16442  1232  0 12:42:56 ?         0:00 -d3&lt;BR /&gt;    root 13558  1232  0 08:51:59 ?         0:00 -d3&lt;BR /&gt;    root 14146  1232  0 08:55:12 ?         0:00 -d3&lt;BR /&gt;    root 10656  1232  0 08:37:07 ?         0:00 -d3&lt;BR /&gt;    root  8087  1232  0 08:17:05 ?         0:00 -d3&lt;BR /&gt;    root  3763  1232 255  Jan 31  ?        63414:03 -d3&lt;BR /&gt;    root 10144  1232  0 08:33:40 ?         0:02 -d3&lt;BR /&gt;    root  5640  1232  0 08:03:03 ?         0:00 -d3&lt;BR /&gt;    root  7715  1232  0 08:15:26 ?         0:00 -d3&lt;BR /&gt;    root  1592  1232  0 14:19:44 ?         0:00 -d3&lt;BR /&gt;    root 10262  1232  0 08:33:49 ?         0:00 -d3&lt;BR /&gt;    root  6323  1232  0 08:07:22 ?         0:00 -d3&lt;BR /&gt;&lt;BR /&gt;It looks like whatever it is, it just keeps running today over &amp;amp; over. Is it safe to kill them all?</description>
      <pubDate>Fri, 19 Mar 2010 18:33:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average-amp-a-root-d3-process/m-p/4604089#M376124</guid>
      <dc:creator>SandiC</dc:creator>
      <dc:date>2010-03-19T18:33:44Z</dc:date>
    </item>
    <item>
      <title>Re: High load average &amp; a root d3 process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average-amp-a-root-d3-process/m-p/4604090#M376125</link>
      <description>This looks like a runaway login attempt where the name of the login shell is d3 (that's why there is a dash -d3 in the listing. Look at the password file:&lt;BR /&gt; &lt;BR /&gt;grep d3 /etc/passwd&lt;BR /&gt; &lt;BR /&gt;It is probably a mistake made by a user trying to create a new shell or menu script and they used the chsh command to change the shell to d3.</description>
      <pubDate>Fri, 19 Mar 2010 19:02:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average-amp-a-root-d3-process/m-p/4604090#M376125</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2010-03-19T19:02:24Z</dc:date>
    </item>
    <item>
      <title>Re: High load average &amp; a root d3 process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average-amp-a-root-d3-process/m-p/4604091#M376126</link>
      <description>This looks like a runaway login attempt where the name of the login shell is d3 (that's why there is a dash -d3 in the listing. Look at the password file:&lt;BR /&gt; &lt;BR /&gt;grep d3 /etc/passwd&lt;BR /&gt; &lt;BR /&gt;It is probably a mistake made by a user trying to create a new shell or menu script and they used the chsh command to change the shell to d3.&lt;BR /&gt;</description>
      <pubDate>Fri, 19 Mar 2010 19:02:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average-amp-a-root-d3-process/m-p/4604091#M376126</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2010-03-19T19:02:48Z</dc:date>
    </item>
    <item>
      <title>Re: High load average &amp; a root d3 process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average-amp-a-root-d3-process/m-p/4604092#M376127</link>
      <description>ps -ef|grep 3762, for an example, you need be sure th eprocess can be killed. this one is very old, find out what it is...maybe a reboot will clear them all.</description>
      <pubDate>Fri, 19 Mar 2010 19:05:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average-amp-a-root-d3-process/m-p/4604092#M376127</guid>
      <dc:creator>John Guster</dc:creator>
      <dc:date>2010-03-19T19:05:12Z</dc:date>
    </item>
    <item>
      <title>Re: High load average &amp; a root d3 process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average-amp-a-root-d3-process/m-p/4604093#M376128</link>
      <description>System is a trusted one, so looking at passwd gives me nothing. I found one user who has root access that may have accidentally done something, so killed their process but this D3 thing still remains. I guess I'll be doing a reboot on Sunday when I have to install patches anyhow.&lt;BR /&gt;</description>
      <pubDate>Fri, 19 Mar 2010 19:35:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average-amp-a-root-d3-process/m-p/4604093#M376128</guid>
      <dc:creator>SandiC</dc:creator>
      <dc:date>2010-03-19T19:35:15Z</dc:date>
    </item>
    <item>
      <title>Re: High load average &amp; a root d3 process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average-amp-a-root-d3-process/m-p/4604094#M376129</link>
      <description>No need to grep anything for ps PID numbers:&lt;BR /&gt; &lt;BR /&gt;ps -fp 1232&lt;BR /&gt; &lt;BR /&gt;You need to track down the parent process (1232). It may have disappeared but I also see registrar with a PPID of 1232. That is part of the EMS/diagnostics reporting system. A reboot will certainly fix this problem. &lt;BR /&gt; &lt;BR /&gt;Whether the system is Trusted, shadow or standard security, you can always read (grep) the passwd file:&lt;BR /&gt; &lt;BR /&gt;grep d3 /etc/passwd&lt;BR /&gt; &lt;BR /&gt;Now if nothing is showing then there is no user shell by that name and the mystery grows deeper. Possibly an option (-d3) was stored as a filename and the parent is trying to automatically start this file. However, the process d3_slave may indicate that this process is associated with something else. Look in the usual places:&lt;BR /&gt; &lt;BR /&gt;find / /usr /opt -xdev -type f | grep d3&lt;BR /&gt; &lt;BR /&gt;The parent directory should give some clue.</description>
      <pubDate>Fri, 19 Mar 2010 20:01:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average-amp-a-root-d3-process/m-p/4604094#M376129</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2010-03-19T20:01:55Z</dc:date>
    </item>
    <item>
      <title>Re: High load average &amp; a root d3 process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average-amp-a-root-d3-process/m-p/4604095#M376130</link>
      <description>&amp;gt; # ps -ef|grep 1232&lt;BR /&gt;&amp;gt; root 1232 1 0 Jan 24 ? 1:23 /usr/sbin/inetd&lt;BR /&gt; &lt;BR /&gt;Oops, I just spotted the first line. PID 1232 is inetd and it has been creating the -d3 processes. Look at /etc/inetd.conf to see if there is a line continuation problem where -d3 is not part of a daemon command line -- but should be.</description>
      <pubDate>Fri, 19 Mar 2010 20:52:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average-amp-a-root-d3-process/m-p/4604095#M376130</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2010-03-19T20:52:43Z</dc:date>
    </item>
    <item>
      <title>Re: High load average &amp; a root d3 process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average-amp-a-root-d3-process/m-p/4604096#M376131</link>
      <description>Thanks Bill!&lt;BR /&gt;&lt;BR /&gt;Here is a line from the inetd.conf file that may be the culprit:&lt;BR /&gt;&lt;BR /&gt;udssltelnet stream tcp nowait root /usr/ud/bin/udtelnetd -d3&lt;BR /&gt;&lt;BR /&gt;(However it does appear on a single line in the file.) This server hosts a unidata database and I believe the d3 is setting the log level to high; so I'm going to change it to 0,then restart inetd &amp;amp; see if that does it. IF not then I suspect that its something to do with hp services because this is part of what I see when I do the find / /usr/opt -xdev -type f | grep d3:&lt;BR /&gt;&lt;BR /&gt;/opt/hpservices/mqueue/ST00d3_STAT_HP_Services.mot&lt;BR /&gt;along with additional lines of ST01d3 through ST07d3.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 22 Mar 2010 17:45:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average-amp-a-root-d3-process/m-p/4604096#M376131</guid>
      <dc:creator>SandiC</dc:creator>
      <dc:date>2010-03-22T17:45:28Z</dc:date>
    </item>
  </channel>
</rss>

