- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- SIGSEV for stack growth failure: libc problem?
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
08-04-2003 07:29 AM
08-04-2003 07:29 AM
Customer is facing to a problem running a batch program (not changed since last year) on a hp-ux 11.00 box.
The error is:
"Pid 5133 received a SIGSEGV for stack growth failure.
Possible causes: insufficient memory or swap space, or stack size exceeded maxssiz."
Value of maxssiz is "8388608".
Memory & swap usage is absolutely under control.
I found that this error could be generated by problems on /usr/lib/libc.2 library, libc patches currently installed are:
PHCO_18102
PHCO_18227
PHCO_18228
PHCO_18229
PHCO_19491
PHCO_20493
PHCO_22314
PHCO_23092
PHCO_23706
PHCO_24148
PHSS_16849
PHSS_19956
I know that there more recent libc patches have been released (PHCO_28425 for istances), but such update require a more consistent patch management (due to various dependencies) that customer can not face as quick as they need a solution...
Has anybody seen this problem ?
Simone
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2003 07:31 AM
08-04-2003 07:31 AM
Re: SIGSEV for stack growth failure: libc problem?
You might have other kernel tuning issues that need to be dealt with.
kmtune output would be useful too.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2003 07:39 AM
08-04-2003 07:39 AM
Re: SIGSEV for stack growth failure: libc problem?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2003 07:50 AM
08-04-2003 07:50 AM
Solution- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2003 06:48 PM
08-04-2003 06:48 PM
Re: SIGSEV for stack growth failure: libc problem?
Do you see mmap error in syslog and the Oracle log file? Something like this maybe:
/usr/lib/dld.sl: Call to mmap() failed - TEXT
/usr/lib/dld.sl: Not enough space
??
Rgds,
Tan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2003 06:26 AM
08-05-2003 06:26 AM
Re: SIGSEV for stack growth failure: libc problem?
Thanks a lot for your answers.
Customer agreed in push up maxssiz and maxdsiz as suggested and now the batch is running fine.
Grazie!
Simone