<?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: system responding slow. in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/system-responding-slow/m-p/4482499#M362736</link>
    <description>putty in xterm emulation mode (default unless your server forces something else) works great for character based glance plus viewing.&lt;BR /&gt;&lt;BR /&gt;and glance is your best bet as the starting point. Once you discover the root cause of the slowness, i.e., disk bottle neck, network bottleneck, CPU or Memory exhaustion, you will be able to figure out the next steps.</description>
    <pubDate>Wed, 19 Aug 2009 14:35:49 GMT</pubDate>
    <dc:creator>Mel Burslan</dc:creator>
    <dc:date>2009-08-19T14:35:49Z</dc:date>
    <item>
      <title>system responding slow.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-responding-slow/m-p/4482496#M362733</link>
      <description>Hi Guys, one of my boxes is responding really slow... What command should i run and also if i am running glance then what terminal emulator i should use..&lt;BR /&gt;Thanks</description>
      <pubDate>Wed, 19 Aug 2009 14:22:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-responding-slow/m-p/4482496#M362733</guid>
      <dc:creator>khilari</dc:creator>
      <dc:date>2009-08-19T14:22:42Z</dc:date>
    </item>
    <item>
      <title>Re: system responding slow.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-responding-slow/m-p/4482497#M362734</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Look for memory leaks:&lt;BR /&gt;&lt;A href="http://www.hpux.ws/?p=8" target="_blank"&gt;http://www.hpux.ws/?p=8&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Performance check scripts:&lt;BR /&gt;&lt;A href="http://www.hpux.ws/?p=6" target="_blank"&gt;http://www.hpux.ws/?p=6&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;glance or gpm to see what processor is running.&lt;BR /&gt;&lt;BR /&gt;Terminal emulator is meaningless here.&lt;BR /&gt;&lt;BR /&gt;Use a Linux box perhaps.&lt;BR /&gt;&lt;BR /&gt;ssh -X hostname gpm&lt;BR /&gt;&lt;BR /&gt;OR use an X windows front end like Hummingbird or CRX&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 19 Aug 2009 14:28:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-responding-slow/m-p/4482497#M362734</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2009-08-19T14:28:59Z</dc:date>
    </item>
    <item>
      <title>Re: system responding slow.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-responding-slow/m-p/4482498#M362735</link>
      <description>Performance problems stem from one of four usual causes:  lack of cpu, lack of i/o, lack of network bandwidth, or lack of memory.  I would guess that cpu problems are probably number 1 and are pretty easy to spot using top or Glance.  For all the other issues, I turn to Glance.&lt;BR /&gt;&lt;BR /&gt;And Glance will run just fine in TUI mode, so your terminal emulation should not be an issue.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Wed, 19 Aug 2009 14:35:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-responding-slow/m-p/4482498#M362735</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2009-08-19T14:35:09Z</dc:date>
    </item>
    <item>
      <title>Re: system responding slow.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-responding-slow/m-p/4482499#M362736</link>
      <description>putty in xterm emulation mode (default unless your server forces something else) works great for character based glance plus viewing.&lt;BR /&gt;&lt;BR /&gt;and glance is your best bet as the starting point. Once you discover the root cause of the slowness, i.e., disk bottle neck, network bottleneck, CPU or Memory exhaustion, you will be able to figure out the next steps.</description>
      <pubDate>Wed, 19 Aug 2009 14:35:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-responding-slow/m-p/4482499#M362736</guid>
      <dc:creator>Mel Burslan</dc:creator>
      <dc:date>2009-08-19T14:35:49Z</dc:date>
    </item>
    <item>
      <title>Re: system responding slow.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-responding-slow/m-p/4482500#M362737</link>
      <description>Hi Khilari,&lt;BR /&gt;&lt;BR /&gt;Responding slow---&lt;BR /&gt;&lt;BR /&gt;Is it responding slow for every command?&lt;BR /&gt;Or is it slow for any specific files system/application.&lt;BR /&gt;&lt;BR /&gt;Try to narrow this.&lt;BR /&gt;&lt;BR /&gt;If it is entire system that is slow, try finding out where is bottleneck.&lt;BR /&gt;Use sar with different option to check disk, cpu bottlenecks.&lt;BR /&gt;&lt;BR /&gt;Use swapinfo to find if memory is an issue.&lt;BR /&gt;Use top to find if any application is using more than usual memory.&lt;BR /&gt;&lt;BR /&gt;If any application or accessing fs is slow, look at the disks involved.&lt;BR /&gt;&lt;BR /&gt;Redgs..&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 19 Aug 2009 15:03:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-responding-slow/m-p/4482500#M362737</guid>
      <dc:creator>R.K. #</dc:creator>
      <dc:date>2009-08-19T15:03:35Z</dc:date>
    </item>
    <item>
      <title>Re: system responding slow.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-responding-slow/m-p/4482501#M362738</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;system responding slow,&lt;BR /&gt;&lt;BR /&gt;Your check points&lt;BR /&gt;&lt;BR /&gt;1]If database is there, please check for number of active and inactive sessions.&lt;BR /&gt;&lt;BR /&gt;2]Memory/CPU checks&lt;BR /&gt;Using,&lt;BR /&gt;&lt;BR /&gt;#top- Check top resource taking process and whther these are running or not.&lt;BR /&gt;&lt;BR /&gt;#Glance -Will give u detailed output, you get the exact count of memory,cpu and swap utilisation.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;#vmstat -Check number of blocked process.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;swap devices/ shared memory segments&lt;BR /&gt;&lt;BR /&gt;Well some times processes completes but still dont release memory segmaents which can cause swap utilisation high ultimately slow response.&lt;BR /&gt;&lt;BR /&gt;So, check&lt;BR /&gt;&lt;BR /&gt;#ipcs -mob&lt;BR /&gt;&lt;BR /&gt;in this if you find NATTCH parameter value as "0" the process you can relase using&lt;BR /&gt;&lt;BR /&gt;#ipcrm -m &lt;ID&gt; (Be careful while running this command)&lt;BR /&gt;&lt;BR /&gt;3]disk utilisation,&lt;BR /&gt;Please check using perticular disk is casing more outage.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thease are some key checks u can go through.&lt;BR /&gt;&lt;BR /&gt;Rgds&lt;BR /&gt;&lt;BR /&gt;YMP&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/ID&gt;</description>
      <pubDate>Wed, 19 Aug 2009 22:48:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-responding-slow/m-p/4482501#M362738</guid>
      <dc:creator>Yogesh M Puranik</dc:creator>
      <dc:date>2009-08-19T22:48:33Z</dc:date>
    </item>
    <item>
      <title>Re: system responding slow.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-responding-slow/m-p/4482502#M362739</link>
      <description>Just use vt100 or any text based terminal and send this esteemed forum screen captures (ALT-PRTSCR) of your glance session using:&lt;BR /&gt;&lt;BR /&gt;glance&lt;BR /&gt;&lt;BR /&gt;glance -m (or hit m whilst in glance)&lt;BR /&gt;&lt;BR /&gt;glance -l (or hit l whilst in glance)&lt;BR /&gt;&lt;BR /&gt;glance -u (or hit u whilst in glance)&lt;BR /&gt;&lt;BR /&gt;and&lt;BR /&gt;&lt;BR /&gt;uptime.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 20 Aug 2009 20:27:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-responding-slow/m-p/4482502#M362739</guid>
      <dc:creator>Alzhy</dc:creator>
      <dc:date>2009-08-20T20:27:31Z</dc:date>
    </item>
    <item>
      <title>Re: system responding slow.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-responding-slow/m-p/4482503#M362740</link>
      <description>&amp;gt; what terminal emulator i should use&lt;BR /&gt; &lt;BR /&gt;HP or Wyse or DEC -- the emulator is important. What is critically important is to never lie to HP-UX about your emulator. That means that there must never be something like:&lt;BR /&gt; &lt;BR /&gt;TERM=vt100&lt;BR /&gt;export TERM&lt;BR /&gt; &lt;BR /&gt;in /etc/profile or $HOME/.profile. Instead, you replace every hardcoded TERM= line with the terminal identifier: ttytype. Use it like this:&lt;BR /&gt; &lt;BR /&gt;eval $(ttytype -s)&lt;BR /&gt; &lt;BR /&gt;To see what this command will do, just type: ttytype -s. Now truly dumb terminals like vt100 will have no navigation keys (like f1, f2, f3, etc) but a smart terminal such as Reflection for HP or QCterm will have the function keys enabled.</description>
      <pubDate>Thu, 20 Aug 2009 23:02:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-responding-slow/m-p/4482503#M362740</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2009-08-20T23:02:47Z</dc:date>
    </item>
  </channel>
</rss>

