<?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: diald process taking up 100% CPU in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/diald-process-taking-up-100-cpu/m-p/3620317#M816151</link>
    <description>I've downloaded the file and seem to be having problem unzipping the file. It doesn't unzip as a depot file?</description>
    <pubDate>Wed, 07 Sep 2005 02:01:21 GMT</pubDate>
    <dc:creator>Gilbert Eu_1</dc:creator>
    <dc:date>2005-09-07T02:01:21Z</dc:date>
    <item>
      <title>diald process taking up 100% CPU</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/diald-process-taking-up-100-cpu/m-p/3620313#M816147</link>
      <description>I am wondering why the diald process is taking up 100% CPU? Any ideas?&lt;BR /&gt;&lt;BR /&gt;CPU TTY    PID USERNAME PRI NI   SIZE    RES STATE    TIME %WCPU  %CPU COMMAND&lt;BR /&gt; 7   ?    1462 root     241 20 44752K    72K run   4347:09 100.07 99.89 diald&lt;BR /&gt;&lt;BR /&gt;I am running an old N4000 Server with 8 CPU's.</description>
      <pubDate>Wed, 07 Sep 2005 01:31:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/diald-process-taking-up-100-cpu/m-p/3620313#M816147</guid>
      <dc:creator>Gilbert Eu_1</dc:creator>
      <dc:date>2005-09-07T01:31:24Z</dc:date>
    </item>
    <item>
      <title>Re: diald process taking up 100% CPU</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/diald-process-taking-up-100-cpu/m-p/3620314#M816148</link>
      <description>Try and tusc the proccess:&lt;BR /&gt;&lt;BR /&gt;tusc -fp 1462 &lt;BR /&gt;&lt;BR /&gt;(&lt;A href="http://hpux.connect.org.uk/hppd/hpux/Sysadmin/tusc-7.7/)" target="_blank"&gt;http://hpux.connect.org.uk/hppd/hpux/Sysadmin/tusc-7.7/)&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Did you try to restart it?&lt;BR /&gt;&lt;BR /&gt;Alex.</description>
      <pubDate>Wed, 07 Sep 2005 01:45:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/diald-process-taking-up-100-cpu/m-p/3620314#M816148</guid>
      <dc:creator>Alex Lavrov.</dc:creator>
      <dc:date>2005-09-07T01:45:51Z</dc:date>
    </item>
    <item>
      <title>Re: diald process taking up 100% CPU</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/diald-process-taking-up-100-cpu/m-p/3620315#M816149</link>
      <description>No, I did not try to restart the process. I know restarting it would solve the problem but, why does this happen?&lt;BR /&gt;&lt;BR /&gt;By the way, what does tusc does?</description>
      <pubDate>Wed, 07 Sep 2005 01:48:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/diald-process-taking-up-100-cpu/m-p/3620315#M816149</guid>
      <dc:creator>Gilbert Eu_1</dc:creator>
      <dc:date>2005-09-07T01:48:11Z</dc:date>
    </item>
    <item>
      <title>Re: diald process taking up 100% CPU</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/diald-process-taking-up-100-cpu/m-p/3620316#M816150</link>
      <description>Tusc will show you what the process is doing right now. You can attach the output here and we'll try to figure out what is going on there.&lt;BR /&gt;&lt;BR /&gt;From looking on the line from top, I doubt that anyone can tell you something.</description>
      <pubDate>Wed, 07 Sep 2005 01:50:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/diald-process-taking-up-100-cpu/m-p/3620316#M816150</guid>
      <dc:creator>Alex Lavrov.</dc:creator>
      <dc:date>2005-09-07T01:50:46Z</dc:date>
    </item>
    <item>
      <title>Re: diald process taking up 100% CPU</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/diald-process-taking-up-100-cpu/m-p/3620317#M816151</link>
      <description>I've downloaded the file and seem to be having problem unzipping the file. It doesn't unzip as a depot file?</description>
      <pubDate>Wed, 07 Sep 2005 02:01:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/diald-process-taking-up-100-cpu/m-p/3620317#M816151</guid>
      <dc:creator>Gilbert Eu_1</dc:creator>
      <dc:date>2005-09-07T02:01:21Z</dc:date>
    </item>
    <item>
      <title>Re: diald process taking up 100% CPU</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/diald-process-taking-up-100-cpu/m-p/3620318#M816152</link>
      <description>gunzip xxx.depot.gz&lt;BR /&gt;swinstall -s /path_to/xxx.depot.gz \* @</description>
      <pubDate>Wed, 07 Sep 2005 02:04:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/diald-process-taking-up-100-cpu/m-p/3620318#M816152</guid>
      <dc:creator>Alex Lavrov.</dc:creator>
      <dc:date>2005-09-07T02:04:04Z</dc:date>
    </item>
    <item>
      <title>Re: diald process taking up 100% CPU</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/diald-process-taking-up-100-cpu/m-p/3620319#M816153</link>
      <description>[1462] read(8, 0x42b922e0, 8192) ................................................................................................................... = 0&lt;BR /&gt;&lt;BR /&gt;This line keeps repeating itself.</description>
      <pubDate>Wed, 07 Sep 2005 02:14:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/diald-process-taking-up-100-cpu/m-p/3620319#M816153</guid>
      <dc:creator>Gilbert Eu_1</dc:creator>
      <dc:date>2005-09-07T02:14:43Z</dc:date>
    </item>
    <item>
      <title>Re: diald process taking up 100% CPU</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/diald-process-taking-up-100-cpu/m-p/3620320#M816154</link>
      <description>Can you attache the whole output? Because in order to know what it tries to read, with read() syscall, I'll need to know what is file descriptor 8. It should be assigned with open() syscall earlier.&lt;BR /&gt;&lt;BR /&gt;Alex.</description>
      <pubDate>Wed, 07 Sep 2005 02:37:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/diald-process-taking-up-100-cpu/m-p/3620320#M816154</guid>
      <dc:creator>Alex Lavrov.</dc:creator>
      <dc:date>2005-09-07T02:37:15Z</dc:date>
    </item>
    <item>
      <title>Re: diald process taking up 100% CPU</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/diald-process-taking-up-100-cpu/m-p/3620321#M816155</link>
      <description>( Attached to process 1462 ("/opt/sanmgr/hostagent/sbin/diald") [32-bit] )&lt;BR /&gt;[1462] read(8, 0x42b922e0, 8192) ................................................................................................................... [running]&lt;BR /&gt;[1462] read(8, 0x42b922e0, 8192) ................................................................................................................... = 0&lt;BR /&gt;[1462] read(8, 0x42b922e0, 8192) ................................................................................................................... = 0&lt;BR /&gt;[1462] read(8, 0x42b922e0, 8192) ................................................................................................................... = 0&lt;BR /&gt;[1462] read(8, 0x42b922e0, 8192) ................................................................................................................... = 0&lt;BR /&gt;[1462] read(8, 0x42b922e0, 8192) ................................................................................................................... = 0&lt;BR /&gt;[1462] read(8, 0x42b922e0, 8192) ................................................................................................................... = 0&lt;BR /&gt;[1462] read(8, 0x42b922e0, 8192) ................................................................................................................... = 0&lt;BR /&gt;[1462] read(8, 0x42b922e0, 8192) ................................................................................................................... = 0&lt;BR /&gt;[1462] read(8, 0x42b922e0, 8192) ................................................................................................................... = 0&lt;BR /&gt;[1462] read(8, 0x42b922e0, 8192) ................................................................................................................... = 0&lt;BR /&gt;[1462] read(8, 0x42b922e0, 8192) ................................................................................................................... = 0&lt;BR /&gt;[1462] read(8, 0x42b922e0, 8192) ................................................................................................................... = 0&lt;BR /&gt;[1462] read(8, 0x42b922e0, 8192) ................................................................................................................... = 0&lt;BR /&gt;[1462] read(8, 0x42b922e0, 8192) ................................................................................................................... = 0&lt;BR /&gt;[1462] read(8, 0x42b922e0, 8192) ................................................................................................................... = 0&lt;BR /&gt;[1462] read(8, 0x42b922e0, 8192) ................................................................................................................... = 0&lt;BR /&gt;[1462] read(8, 0x42b922e0, 8192) ................................................................................................................... = 0&lt;BR /&gt;[1462] read(8, 0x42b922e0, 8192) ................................................................................................................... = 0&lt;BR /&gt;[1462] read(8, 0x42b922e0, 8192) ................................................................................................................... = 0&lt;BR /&gt;[1462] read(8, 0x42b922e0, 8192) ................................................................................................................... = 0&lt;BR /&gt;[1462] read(8, 0x42b922e0, 8192) ................................................................................................................... = 0&lt;BR /&gt;[1462] read(8, 0x42b922e0, 8192) ................................................................................................................... = 0&lt;BR /&gt;[1462] read(8, 0x42b922e0, 8192) ................................................................................................................... = 0&lt;BR /&gt;[1462] read(8, 0x42b922e0, 8192) ................................................................................................................... = 0&lt;BR /&gt;[1462] read(8, 0x42b922e0, 8192) ................................................................................................................... = 0&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I output it to a file and it reached 12 MB is mere 2 seconds. I had to interrupt it from running any further.</description>
      <pubDate>Wed, 07 Sep 2005 02:40:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/diald-process-taking-up-100-cpu/m-p/3620321#M816155</guid>
      <dc:creator>Gilbert Eu_1</dc:creator>
      <dc:date>2005-09-07T02:40:59Z</dc:date>
    </item>
    <item>
      <title>Re: diald process taking up 100% CPU</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/diald-process-taking-up-100-cpu/m-p/3620322#M816156</link>
      <description>It seems that it tries to read from some files, but it fails ... Probably file does not exist or no permissions or the file is corupted.&lt;BR /&gt;&lt;BR /&gt;I'm not sure if it's possible to find what file is it only be the file descriptor.&lt;BR /&gt;&lt;BR /&gt;You can kill diald and start it like this:&lt;BR /&gt;&lt;BR /&gt;tusc -fn &lt;COMMAND&gt; &amp;gt; /tmp/tusc.out&lt;BR /&gt;&lt;BR /&gt;And then look for "open" syscalls and see what files are opened and what FD they have. Maybe this will help to find what brings the process to the infinite loop.&lt;BR /&gt;&lt;BR /&gt;Alex.&lt;/COMMAND&gt;</description>
      <pubDate>Wed, 07 Sep 2005 03:07:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/diald-process-taking-up-100-cpu/m-p/3620322#M816156</guid>
      <dc:creator>Alex Lavrov.</dc:creator>
      <dc:date>2005-09-07T03:07:19Z</dc:date>
    </item>
    <item>
      <title>Re: diald process taking up 100% CPU</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/diald-process-taking-up-100-cpu/m-p/3620323#M816157</link>
      <description>I did what you suggested and restarted the process. I looked through the output and did not find anything unusual.&lt;BR /&gt;&lt;BR /&gt;Anyway, thanks for your helpful information. I've also attached the output.</description>
      <pubDate>Wed, 07 Sep 2005 03:18:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/diald-process-taking-up-100-cpu/m-p/3620323#M816157</guid>
      <dc:creator>Gilbert Eu_1</dc:creator>
      <dc:date>2005-09-07T03:18:45Z</dc:date>
    </item>
    <item>
      <title>Re: diald process taking up 100% CPU</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/diald-process-taking-up-100-cpu/m-p/3620324#M816158</link>
      <description>Well, because obviously it's some bug, so at the start everything seems OK. You can leave it this way and when it will hang again and consume 100% CPU, you'll be able to know what file it's trying to read.&lt;BR /&gt;&lt;BR /&gt;Ofcourse pay attention so the log file will not fill out your filesystem. And if it happens not long after you start it, you can give it a shot, if it happens after days, weeks etc, than I think it's not worth it and just contact the program authors.</description>
      <pubDate>Wed, 07 Sep 2005 03:25:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/diald-process-taking-up-100-cpu/m-p/3620324#M816158</guid>
      <dc:creator>Alex Lavrov.</dc:creator>
      <dc:date>2005-09-07T03:25:55Z</dc:date>
    </item>
    <item>
      <title>Re: diald process taking up 100% CPU</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/diald-process-taking-up-100-cpu/m-p/3620325#M816159</link>
      <description>I've seen this very same behavior before.  Just kill it and restart.  In calling HP on it, they gave the above advice, and said (way back then) that a bugfix was coming out for it.  It's been a long time since it has recurred, so I figure that our regular patch schedule must have caught it with a fix.  I used to see it pretty much monthly, but we've not seen it do this for a over a year now.</description>
      <pubDate>Wed, 07 Sep 2005 07:51:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/diald-process-taking-up-100-cpu/m-p/3620325#M816159</guid>
      <dc:creator>TwoProc</dc:creator>
      <dc:date>2005-09-07T07:51:51Z</dc:date>
    </item>
  </channel>
</rss>

