- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- possible stack overflow?
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
Discussions
Discussions
Discussions
Forums
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
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
тАО09-30-2010 08:23 AM
тАО09-30-2010 08:23 AM
Had an issue with a server (snippet from the syslog is attached). Is there a way to determine what caused this issue? Basically locked the system up.
System is an HP Integrity rx2620. 1 processor
Sep 28 19:10:02 fgexsh41 vmunix: Deferred swap reservation failure pid: 22658
Sep 28 19:10:02 fgexsh41 vmunix:
Sep 28 19:10:02 fgexsh41 vmunix: Pid 22658 was killed due to failure in writing the signal context- possible stack overflow.
Sep 28 19:10:02 fgexsh41 vmunix: Deferred swap reservation failure pid: 22658
Sep 28 19:22:33 fgexsh41 vmunix: Warning: Ignoring setuid/setgid bit on "/h/EC/progs/debx_env_launch" as the system tunable "secure_sid_scripts" is s
et.
Sep 28 19:27:17 fgexsh41 vmunix: Deferred swap reservation failure pid: 23914
Sep 28 19:27:17 fgexsh41 vmunix:
Sep 28 19:27:17 fgexsh41 vmunix: Pid 23914 was killed due to failure in writing the signal context- possible stack overflow.
Sep 28 19:27:17 fgexsh41 vmunix: Deferred swap reservation failure pid: 23914
Sep 28 19:33:34 fgexsh41 above message repeats 2 times
Sep 28 19:38:00 fgexsh41 syslog: clnt_dg_create: out of memory
Sep 28 19:51:28 fgexsh41 vmunix: Deferred swap reservation failure pid: 26610
Sep 28 19:51:28 fgexsh41 vmunix:
Sep 28 19:51:28 fgexsh41 vmunix: Pid 26610 was killed due to failure in writing the signal context- possible stack overflow.
Sep 28 19:51:28 fgexsh41 vmunix: Deferred swap reservation failure pid: 26610
Sep 28 19:59:39 fgexsh41 vmunix: Deferred swap reservation failure pid: 27676
Sep 28 20:04:44 fgexsh41 vmunix: Warning: Ignoring setuid/setgid bit on "/h/EC/progs/debx_env_launch" as the system tunable "secure_sid_scripts" is s
et.
Sep 28 20:04:45 fgexsh41 vmunix: Deferred swap reservation failure pid: 27864
Solved! Go to Solution.
- Tags:
- stack overflow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-30-2010 08:29 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-30-2010 08:34 AM
тАО09-30-2010 08:34 AM
Re: possible stack overflow?
Mb Mb Mb PCT START/ Mb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 4096 856 3240 21% 0 - 1 /dev/vg00/lvol2
reserve - 1961 -1961
memory 2028 1509 519 74%
total 6124 4326 1798 71% - 0 -
#
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-01-2010 01:39 AM - edited тАО07-08-2016 11:04 PM
тАО10-01-2010 01:39 AM - edited тАО07-08-2016 11:04 PM
Re: possible stack overflow?
You could have a recursive stack overflow due to coding mistakes.
But all of the other errors makes it look like you are out of swap when it happens.
Add more memory or swap.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-01-2010 11:23 PM
тАО10-01-2010 11:23 PM
Re: possible stack overflow?
If not obvious, I should have said: Add more memory or swap.