<?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 scope and glance - resource allocation issue in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/scope-and-glance-resource-allocation-issue/m-p/6826629#M603541</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;There is a strange problem where I want to check resource utilization with glance but it directly creates a core file and OVO SCOPE process isn't running on the server although I have stopped and started it several times. It gives a bad allocation message where there is enough memory&amp;amp;swap space and parameter usage seems fine (i checked the forum and encountered&amp;nbsp;&lt;A href="http://community.hpe.com/t5/Languages-and-Scripting/aCC-runtime-error/m-p/4287919/highlight/true#M43448)" target="_blank"&gt;http://community.hpe.com/t5/Languages-and-Scripting/aCC-runtime-error/m-p/4287919/highlight/true#M43448)&lt;/A&gt; Could it be a known bug or anything you would suggest to investigate in core file?&lt;/P&gt;&lt;P&gt;status.scope output&lt;/P&gt;&lt;P&gt;**** /opt/perf/bin/scopeux : 01/22/16 10:42:50 ****&lt;BR /&gt;scopeux/HP-UX 11.13.007 COLLECTOR BEGIN.&lt;BR /&gt;aCC runtime: Uncaught exception of type "std::bad_alloc".&lt;BR /&gt;aCC runtime: what(): bad allocation exception thrown (0xffffff30 bytes)&lt;BR /&gt;server02:/var/opt/perf#&lt;BR /&gt;server02:/var/opt/perf#&lt;BR /&gt;server02:/var/opt/perf#swapinfo -tam&lt;BR /&gt;Mb Mb Mb PCT START/ Mb&lt;BR /&gt;TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME&lt;BR /&gt;dev 4096 0 4096 0% 0 - 1 /dev/vg00/lvol2&lt;BR /&gt;dev 49152 0 49152 0% 0 - 1 /dev/vg00/lvswap01&lt;BR /&gt;reserve - 53248 -53248&lt;BR /&gt;memory 466899 171697 295202 37%&lt;BR /&gt;total 520147 224945 295202 43% - 0 -&lt;BR /&gt;server02:/var/opt/perf#&lt;BR /&gt;server02:/var/opt/perf#kcusage maxdsiz&lt;BR /&gt;Tunable Usage / Setting&lt;BR /&gt;=============================================&lt;BR /&gt;maxdsiz 638255104 / 1073741824&lt;BR /&gt;server02:/var/opt/perf#kcusage maxdsiz_64bit&lt;BR /&gt;Tunable Usage / Setting&lt;BR /&gt;=============================================&lt;BR /&gt;maxdsiz_64bit 1187708928 / 2147483648&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 25 Jan 2016 09:23:35 GMT</pubDate>
    <dc:creator>royalliege</dc:creator>
    <dc:date>2016-01-25T09:23:35Z</dc:date>
    <item>
      <title>scope and glance - resource allocation issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/scope-and-glance-resource-allocation-issue/m-p/6826629#M603541</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;There is a strange problem where I want to check resource utilization with glance but it directly creates a core file and OVO SCOPE process isn't running on the server although I have stopped and started it several times. It gives a bad allocation message where there is enough memory&amp;amp;swap space and parameter usage seems fine (i checked the forum and encountered&amp;nbsp;&lt;A href="http://community.hpe.com/t5/Languages-and-Scripting/aCC-runtime-error/m-p/4287919/highlight/true#M43448)" target="_blank"&gt;http://community.hpe.com/t5/Languages-and-Scripting/aCC-runtime-error/m-p/4287919/highlight/true#M43448)&lt;/A&gt; Could it be a known bug or anything you would suggest to investigate in core file?&lt;/P&gt;&lt;P&gt;status.scope output&lt;/P&gt;&lt;P&gt;**** /opt/perf/bin/scopeux : 01/22/16 10:42:50 ****&lt;BR /&gt;scopeux/HP-UX 11.13.007 COLLECTOR BEGIN.&lt;BR /&gt;aCC runtime: Uncaught exception of type "std::bad_alloc".&lt;BR /&gt;aCC runtime: what(): bad allocation exception thrown (0xffffff30 bytes)&lt;BR /&gt;server02:/var/opt/perf#&lt;BR /&gt;server02:/var/opt/perf#&lt;BR /&gt;server02:/var/opt/perf#swapinfo -tam&lt;BR /&gt;Mb Mb Mb PCT START/ Mb&lt;BR /&gt;TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME&lt;BR /&gt;dev 4096 0 4096 0% 0 - 1 /dev/vg00/lvol2&lt;BR /&gt;dev 49152 0 49152 0% 0 - 1 /dev/vg00/lvswap01&lt;BR /&gt;reserve - 53248 -53248&lt;BR /&gt;memory 466899 171697 295202 37%&lt;BR /&gt;total 520147 224945 295202 43% - 0 -&lt;BR /&gt;server02:/var/opt/perf#&lt;BR /&gt;server02:/var/opt/perf#kcusage maxdsiz&lt;BR /&gt;Tunable Usage / Setting&lt;BR /&gt;=============================================&lt;BR /&gt;maxdsiz 638255104 / 1073741824&lt;BR /&gt;server02:/var/opt/perf#kcusage maxdsiz_64bit&lt;BR /&gt;Tunable Usage / Setting&lt;BR /&gt;=============================================&lt;BR /&gt;maxdsiz_64bit 1187708928 / 2147483648&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 25 Jan 2016 09:23:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/scope-and-glance-resource-allocation-issue/m-p/6826629#M603541</guid>
      <dc:creator>royalliege</dc:creator>
      <dc:date>2016-01-25T09:23:35Z</dc:date>
    </item>
    <item>
      <title>Re: scope and glance - resource allocation issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/scope-and-glance-resource-allocation-issue/m-p/6826645#M603542</link>
      <description>&lt;P&gt;&amp;gt;It gives a bad allocation message where there is enough memory &amp;amp; swap space and parameter usage seems fine&lt;/P&gt;&lt;P&gt;aCC runtime: Uncaught exception of type "std::bad_alloc".&lt;BR /&gt;aCC runtime: what(): bad allocation exception thrown (0xffffff30 bytes)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What is the value of maxdsiz_64bit?&amp;nbsp; You need to grow by 4 Gb.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;BR /&gt;maxdsiz_64bit XXXX / 2147483648&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is less than half the needed size.&amp;nbsp; (The proper command is kctune(1m)).&lt;/P&gt;</description>
      <pubDate>Mon, 25 Jan 2016 11:03:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/scope-and-glance-resource-allocation-issue/m-p/6826645#M603542</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2016-01-25T11:03:48Z</dc:date>
    </item>
    <item>
      <title>Re: scope and glance - resource allocation issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/scope-and-glance-resource-allocation-issue/m-p/6826666#M603543</link>
      <description>&lt;P&gt;I also have other HPUX 11.31 servers running glance with that setting of maxdsiz_64bit. How did you understand that it is less than required?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Mon, 25 Jan 2016 12:44:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/scope-and-glance-resource-allocation-issue/m-p/6826666#M603543</guid>
      <dc:creator>royalliege</dc:creator>
      <dc:date>2016-01-25T12:44:12Z</dc:date>
    </item>
    <item>
      <title>Re: scope and glance - resource allocation issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/scope-and-glance-resource-allocation-issue/m-p/6826677#M603544</link>
      <description>&lt;P&gt;**** /opt/perf/bin/scopeux : 01/25/16 15:39:07 ****&lt;BR /&gt;scopeux/HP-UX 11.13.007 COLLECTOR BEGIN.&lt;/P&gt;&lt;P&gt;So it started again; after&amp;nbsp;killing midaemon process. mwa stop; mwa start action apparently didn't kill midaemon process. That was the solution, the cause is still unknown. It still may&amp;nbsp;occur.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Jan 2016 13:45:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/scope-and-glance-resource-allocation-issue/m-p/6826677#M603544</guid>
      <dc:creator>royalliege</dc:creator>
      <dc:date>2016-01-25T13:45:17Z</dc:date>
    </item>
    <item>
      <title>Re: scope and glance - resource allocation issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/scope-and-glance-resource-allocation-issue/m-p/6826763#M603545</link>
      <description>&lt;P&gt;&amp;gt;How did you understand that it is less than required?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Because it failed?&amp;nbsp; :-)&amp;nbsp; Because (0xffffff30 bytes) is near 4 GB.&lt;/P&gt;&lt;P&gt;Of course I don't know why it needs so much.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Jan 2016 18:30:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/scope-and-glance-resource-allocation-issue/m-p/6826763#M603545</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2016-01-25T18:30:44Z</dc:date>
    </item>
    <item>
      <title>Re: scope and glance - resource allocation issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/scope-and-glance-resource-allocation-issue/m-p/6827078#M603546</link>
      <description>&lt;P&gt;&amp;gt;Because (0xffffff30 bytes) is near 4 GB.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hmm, since scopeux is a 32 bit app, 0xffffff30 is really a negative number so likely to be a software bug.&lt;/P&gt;</description>
      <pubDate>Tue, 26 Jan 2016 17:32:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/scope-and-glance-resource-allocation-issue/m-p/6827078#M603546</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2016-01-26T17:32:47Z</dc:date>
    </item>
  </channel>
</rss>

