- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: useracc failed
Operating System - HP-UX
1752273
Members
4544
Online
108786
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
тАО07-23-2009 07:19 PM
тАО07-23-2009 07:19 PM
useracc failed
Hi,
When i try to bring up WAS in HP-UX and do heavy transactions,core dump is getting formed with following error
sendsig: useracc failed. 0x9fffffffb977be00 0x00000000005000
Pid 25126 was killed due to failure in writing the signal context - possible stack overflow.
Kindly assist
When i try to bring up WAS in HP-UX and do heavy transactions,core dump is getting formed with following error
sendsig: useracc failed. 0x9fffffffb977be00 0x00000000005000
Pid 25126 was killed due to failure in writing the signal context - possible stack overflow.
Kindly assist
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-24-2009 01:45 AM
тАО07-24-2009 01:45 AM
Re: useracc failed
As it said, you either have a main stack or a thread stack overflow.
You need to get a stack trace (use gdb) to determine which.
You need to get a stack trace (use gdb) to determine which.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-24-2009 02:01 AM
тАО07-24-2009 02:01 AM
Re: useracc failed
This is the first time I am told to analyse core dump..I dont know much about this..can u pls elaborate on it
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-24-2009 02:35 AM
тАО07-24-2009 02:35 AM
Re: useracc failed
On the WDB page you can find this document:
Debugging core files using HP WDB
http://www.hp.com/go/wdb
Basically on the same system that caused the core dump:
$ file core
(Gives you the signal and up to 14 bytes of the basename of the executable.
$ gdb path-to/executable core
(gdb) bt
(gdb) q
If it is a main thread, you should see main at the bottom. If it is a thread, you should see some pthread on the bottom.
By taking the difference in the $sp register from the top and bottom frames, you can compute your current stack size.
Debugging core files using HP WDB
http://www.hp.com/go/wdb
Basically on the same system that caused the core dump:
$ file core
(Gives you the signal and up to 14 bytes of the basename of the executable.
$ gdb path-to/executable core
(gdb) bt
(gdb) q
If it is a main thread, you should see main at the bottom. If it is a thread, you should see some pthread on the bottom.
By taking the difference in the $sp register from the top and bottom frames, you can compute your current stack size.
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