- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- dmesg output not correct
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
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
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-17-2014 08:47 PM
09-17-2014 08:47 PM
dmesg output not correct
Hi expert !
below is the dmesg output from app server. but currently syslog not showing such error !!!
root@dcpapp01 [/]# dmesg
Sep 18 09:51
...
ntext - possible stack overflow.
Pid 28325 was killed due to failure in writing the signal context - possible stack overflow.
Pid 28356 was killed due to failure in writing the signal context - possible stack overflow.
Pid 28350 was killed due to failure in writing the signal context - possible stack overflow.
Pid 28353 was killed due to failure in writing the signal context - possible stack overflow.
Pid 28360 was killed due to failure in writing the signal context - possible stack overflow.
Pid 28363 was killed due to failure in writing the signal context - possible stack overflow.
Pid 28369 was killed due to failure in writing the signal context - possible stack overflow.
Pid 28430 was killed due to failure in writing the signal context - possible stack overflow.
Pid 28365 was killed due to failure in writing the signal context - possible stack overflow.
Pid 28428 was killed due to failure in writing the signal context - possible stack overflow.
Pid 28313 was killed due to failure in writing the signal context - possible stack overflow.
Pid 28438 was killed due to failure in writing the signal context - possible stack overflow.
Pid 28440 was killed due to failure in writing the signal
Regards,
Morshed.
- Tags:
- dmesg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-17-2014 10:21 PM
09-17-2014 10:21 PM
Re: dmesg output not correct
If you don't run "dmesg -" in a cron job, then the errors may be old, since none of them are timestamped.