<?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: kernel tunable parameter file in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/kernel-tunable-parameter-maxrsessiz-exceeded/m-p/5287193#M474850</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I need to extract all the kernel tunables in a text file. Which file contains the list of all the tunables and their assigned values?&lt;/P&gt;&lt;P&gt;Kindly assist.&lt;/P&gt;</description>
    <pubDate>Mon, 01 Aug 2011 06:16:30 GMT</pubDate>
    <dc:creator>henrymanda</dc:creator>
    <dc:date>2011-08-01T06:16:30Z</dc:date>
    <item>
      <title>kernel tunable parameter maxrsessiz exceeded</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/kernel-tunable-parameter-maxrsessiz-exceeded/m-p/4765845#M389491</link>
      <description>hello,&lt;BR /&gt;we have big problems at a HPUX 11.31 server with a ORACLE application ( ORACLE application server).&lt;BR /&gt;&lt;BR /&gt;When we stopped the process(es), we got following error:&lt;BR /&gt;&lt;BR /&gt;Pid 18791 received a SIGSEGV for stack growth failure.&lt;BR /&gt;Possible causes: insufficient memory or swap space,&lt;BR /&gt;or stack size exceeded maxrsessiz&lt;BR /&gt;or stack size limit is set too small.&lt;BR /&gt;&lt;BR /&gt;i have never heard before of kernel tunable parameter maxrsessiz/maxrsessiz_64bit.&lt;BR /&gt;&lt;BR /&gt;actual we have the default values ( in attachment).&lt;BR /&gt;&lt;BR /&gt;what should be the new value of maxrsessiz  ?&lt;BR /&gt;how can i see the actual maxrsessiz value of a process (PID) ?&lt;BR /&gt;&lt;BR /&gt;description of maxrsessiz :&lt;BR /&gt;&lt;BR /&gt; maxrsessiz(5) -- maximum size (in bytes) of the RSE&lt;BR /&gt;&lt;BR /&gt;Itanium-based systems utilize a per-process register stack in main memory (for more information see the Intel IA-64 Architecture Software Developer's Manual, Volume 2, Chapter 6). This stack moves registers between the physical registers and main memory and is maintained by the Register Stack Engine (RSE). maxrsessiz determines the size of this stack. Who is Expected to Change This Tunable?</description>
      <pubDate>Wed, 16 Mar 2011 07:42:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/kernel-tunable-parameter-maxrsessiz-exceeded/m-p/4765845#M389491</guid>
      <dc:creator>Billa-User</dc:creator>
      <dc:date>2011-03-16T07:42:55Z</dc:date>
    </item>
    <item>
      <title>Re: kernel tunable parameter maxrsessiz exceeded</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/kernel-tunable-parameter-maxrsessiz-exceeded/m-p/4765846#M389492</link>
      <description>Since this is not some locally written program with unusual features (very large stack sizes are often bad programming style), I would look at swapinfo -tam. While you may have plenty of RAM, over a period of time, your system may have deactivated many idle programs and rolled them out to swap. If they remain idle, there is nothing to bring them back and eventually swap space can be exhausted.</description>
      <pubDate>Wed, 16 Mar 2011 10:26:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/kernel-tunable-parameter-maxrsessiz-exceeded/m-p/4765846#M389492</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2011-03-16T10:26:29Z</dc:date>
    </item>
    <item>
      <title>Re: kernel tunable parameter maxrsessiz exceeded</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/kernel-tunable-parameter-maxrsessiz-exceeded/m-p/4765847#M389493</link>
      <description>Since this is not some locally written program with unusual features (very large stack sizes are often bad programming style), I would look at swapinfo -tam. While you may have plenty of RAM, over a period of time, your system may have deactivated many idle programs and rolled them out to swap. If they remain idle, there is nothing to bring them back and eventually swap space can be exhausted.</description>
      <pubDate>Wed, 16 Mar 2011 10:26:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/kernel-tunable-parameter-maxrsessiz-exceeded/m-p/4765847#M389493</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2011-03-16T10:26:30Z</dc:date>
    </item>
    <item>
      <title>Re: kernel tunable parameter maxrsessiz exceeded</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/kernel-tunable-parameter-maxrsessiz-exceeded/m-p/4765848#M389494</link>
      <description>we also think about a problem of threads ?&lt;BR /&gt;&lt;BR /&gt;we increase max_thread_proc , old percentage was about 50 % ?&lt;BR /&gt;&lt;BR /&gt;we embedding know how from the LINUX department.&lt;BR /&gt;&lt;BR /&gt;what is the similar command on HP-UX ?&lt;BR /&gt;&lt;BR /&gt;LINUX: Get info about threads&lt;BR /&gt;&lt;BR /&gt;Type the following command:&lt;BR /&gt;# ps -eLf&lt;BR /&gt;# ps axms&lt;BR /&gt;&lt;BR /&gt;regards</description>
      <pubDate>Wed, 16 Mar 2011 11:41:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/kernel-tunable-parameter-maxrsessiz-exceeded/m-p/4765848#M389494</guid>
      <dc:creator>Billa-User</dc:creator>
      <dc:date>2011-03-16T11:41:01Z</dc:date>
    </item>
    <item>
      <title>Re: kernel tunable parameter maxrsessiz exceeded</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/kernel-tunable-parameter-maxrsessiz-exceeded/m-p/4765849#M389495</link>
      <description>try kcusage command</description>
      <pubDate>Wed, 16 Mar 2011 16:33:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/kernel-tunable-parameter-maxrsessiz-exceeded/m-p/4765849#M389495</guid>
      <dc:creator>Uday_S_Ankolekar</dc:creator>
      <dc:date>2011-03-16T16:33:10Z</dc:date>
    </item>
    <item>
      <title>Re: kernel tunable parameter maxrsessiz exceeded</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/kernel-tunable-parameter-maxrsessiz-exceeded/m-p/4765850#M389496</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;kcalarm can help you set up email based alarms.&lt;BR /&gt;&lt;BR /&gt;You can set the percentage of total parameter being set as an alarm point to allow yourself to be proactive.&lt;BR /&gt;&lt;BR /&gt;man kcalarm&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 16 Mar 2011 17:28:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/kernel-tunable-parameter-maxrsessiz-exceeded/m-p/4765850#M389496</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2011-03-16T17:28:35Z</dc:date>
    </item>
    <item>
      <title>Re: kernel tunable parameter maxrsessiz exceeded</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/kernel-tunable-parameter-maxrsessiz-exceeded/m-p/4765851#M389497</link>
      <description>&amp;gt;Pid 18791 received a SIGSEGV for stack growth failure.&lt;BR /&gt;&amp;gt;or stack size exceeded maxrsessiz&lt;BR /&gt;&amp;gt;I have never heard before of kernel tunable parameter maxrsessiz&lt;BR /&gt;&lt;BR /&gt;Hmm, I didn't know that maxrsessiz was specific to the message.  In most cases 8 Mb is good enough for the RSE stack.  I've only seen a few cases where you have so much recursion that you need to increase the stack to 16 Mb.  And two of them were in the aCC6 compiler.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;what should be the new value of maxrsessiz?&lt;BR /&gt;&amp;gt;how can I see the actual maxrsessiz value of a process?&lt;BR /&gt;&lt;BR /&gt;Try 16 Mb.  To see the actual value, it would help if you have a core file.  Or be able to debug it with gdb.&lt;BR /&gt;But the actual value would be maxrsessiz of course.  :-)&lt;BR /&gt;Or did you want to see the current RSE stack usage of a PID that hasn't aborted yet?&lt;BR /&gt;&lt;BR /&gt;&amp;gt;we also think about a problem of threads?&lt;BR /&gt;&lt;BR /&gt;No, with threads you will probably just get a signal 11 when it hits the guard page.  But there is a RSE stack for threads that is typically trivial in size, compared to 8 Mb.</description>
      <pubDate>Wed, 16 Mar 2011 17:59:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/kernel-tunable-parameter-maxrsessiz-exceeded/m-p/4765851#M389497</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2011-03-16T17:59:06Z</dc:date>
    </item>
    <item>
      <title>Re: kernel tunable parameter file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/kernel-tunable-parameter-maxrsessiz-exceeded/m-p/5287193#M474850</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I need to extract all the kernel tunables in a text file. Which file contains the list of all the tunables and their assigned values?&lt;/P&gt;&lt;P&gt;Kindly assist.&lt;/P&gt;</description>
      <pubDate>Mon, 01 Aug 2011 06:16:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/kernel-tunable-parameter-maxrsessiz-exceeded/m-p/5287193#M474850</guid>
      <dc:creator>henrymanda</dc:creator>
      <dc:date>2011-08-01T06:16:30Z</dc:date>
    </item>
    <item>
      <title>Re: kernel tunable parameter file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/kernel-tunable-parameter-maxrsessiz-exceeded/m-p/5287287#M474853</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;#kctune &amp;gt; filename&lt;/P&gt;&lt;P&gt;#kcmodule &amp;gt; filename&lt;/P&gt;</description>
      <pubDate>Mon, 01 Aug 2011 08:02:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/kernel-tunable-parameter-maxrsessiz-exceeded/m-p/5287287#M474853</guid>
      <dc:creator>Hiren N Dave</dc:creator>
      <dc:date>2011-08-01T08:02:13Z</dc:date>
    </item>
  </channel>
</rss>

