- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Not Able to increase maxssiz_64bit value from ...
Operating System - HP-UX
1748142
Members
3681
Online
108758
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-04-2009 04:38 AM
тАО12-04-2009 04:38 AM
Re: Not Able to increase maxssiz_64bit value from 1GB to 4GB
>clearly say that there is a stack growth failure.
Which doesn't mean much since there are N causes of this. What it does mean is that it isn't maxdsiz as we originally guessed, so your application team is on the ball. :-)
>Pid 8276 received a SIGSEGV for stack growth failure.
>Possible causes: insufficient memory or swap space, or stack size exceeded maxssiz.
The message invokes a thesis which could also mean there is an application error.
I.e. a recursive stack overflow which will keep failing, no matter how much you increase it. Now your team can be behind the 8 ball. :-)
>How I can monitor stack growth usage of particular process?
>Memory fault(coredump)
Why bother? The corefile after the abort has a lot of what you need to see why it is failing. Use gdb to get a stack trace. If you see recursion, your job is done.
If not, you need to figure out who is the pig with large stack frames.
>JRF: This can point to either too low a maxdsiz.
Not hardly. Only the last two you mention, plus coding errors.
Which doesn't mean much since there are N causes of this. What it does mean is that it isn't maxdsiz as we originally guessed, so your application team is on the ball. :-)
>Pid 8276 received a SIGSEGV for stack growth failure.
>Possible causes: insufficient memory or swap space, or stack size exceeded maxssiz.
The message invokes a thesis which could also mean there is an application error.
I.e. a recursive stack overflow which will keep failing, no matter how much you increase it. Now your team can be behind the 8 ball. :-)
>How I can monitor stack growth usage of particular process?
>Memory fault(coredump)
Why bother? The corefile after the abort has a lot of what you need to see why it is failing. Use gdb to get a stack trace. If you see recursion, your job is done.
If not, you need to figure out who is the pig with large stack frames.
>JRF: This can point to either too low a maxdsiz.
Not hardly. Only the last two you mention, plus coding errors.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-04-2009 05:07 AM
тАО12-04-2009 05:07 AM
Re: Not Able to increase maxssiz_64bit value from 1GB to 4GB
Hi,
If i remember correctly , your application should have kernel parameter recommendation as a part of pre-install process , which might vary depending on versions.
did you verify the kernel parameters value set on your box are exactly as mentioned in pre install doc for you application ?
Javed
If i remember correctly , your application should have kernel parameter recommendation as a part of pre-install process , which might vary depending on versions.
did you verify the kernel parameters value set on your box are exactly as mentioned in pre install doc for you application ?
Javed
Never Give Up
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-06-2010 04:53 AM
тАО05-06-2010 04:53 AM
Re: Not Able to increase maxssiz_64bit value from 1GB to 4GB
the max limit is 1GB
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP