HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- linux server was hung and causing a web service ou...
Operating System - Linux
1826269
Members
3780
Online
109692
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
Forums
Discussions
Discussions
Discussions
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
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
04-12-2011 01:29 AM
04-12-2011 01:29 AM
linux server was hung and causing a web service outage
Our linux server was hung and causing a web service outage. I have to investigate as to why the server got hung and respond back with findings. Anyone can assist me how to start?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2011 02:55 AM
04-12-2011 02:55 AM
Re: linux server was hung and causing a web service outage
Find out what exactly was done to restore the server to working condition: was only the web service restarted, or was the entire server rebooted? If the server was rebooted, was there an error message on the server's console before the reboot? What did it say?
Practically all Linux servers will produce logs to /var/log directory: read them.
The web service application may produce yet another set of logs in an application-specific location: those logs may be informative too.
You should familiarize yourself with normal startup/shutdown messages of your Linux distribution, and of your web service application.
If the application logs just stop without the normal shutdown messages, the application may have crashed, or someone may have forcibly stopped it using the "kill -KILL" or "kill -9" commands.
If the OS log just end without the normal shutdown messages, and then resume with the normal startup messages, the entire system has crashed/hung: if the cause is hardware-related and your server has hardware diagnostic log functionality, the hardware diagnostics might reveal something useful.
If there are no clues at all, there are a number of things you can do to get more information if the crash/hang happens again.
- For application-level problems, you can enable core dumps. Add "ulimit -c unlimited" to a suitable location to enable core dumps and teach your operators to try "kill -QUIT" or "kill -ABRT" to force a hanging application to produce a core dump before restarting it. The core dump may be a very large file, but a developer armed with a debugger can use the core dump to find out exactly what the program was doing when it was hung or when it crashed.
- For system-level problems, most modern Linux distributions designed for server use include some type of crash dump functionality. It is typically not enabled by default: read the documentation of your distribution to find out how to enable it and what its requirements are. If your server is hanging, you may need a way to send a hardware-level NMI signal to force the crash dump: read your hardware documentation to see if your server has a button that can be used to send a NMI signal.
- If you suspect there's a hardware-level problem, pay attention to the boot-up messages of the server, and use the hardware diagnostic programs provided by your server manufacturer.
MK
Practically all Linux servers will produce logs to /var/log directory: read them.
The web service application may produce yet another set of logs in an application-specific location: those logs may be informative too.
You should familiarize yourself with normal startup/shutdown messages of your Linux distribution, and of your web service application.
If the application logs just stop without the normal shutdown messages, the application may have crashed, or someone may have forcibly stopped it using the "kill -KILL" or "kill -9" commands.
If the OS log just end without the normal shutdown messages, and then resume with the normal startup messages, the entire system has crashed/hung: if the cause is hardware-related and your server has hardware diagnostic log functionality, the hardware diagnostics might reveal something useful.
If there are no clues at all, there are a number of things you can do to get more information if the crash/hang happens again.
- For application-level problems, you can enable core dumps. Add "ulimit -c unlimited" to a suitable location to enable core dumps and teach your operators to try "kill -QUIT" or "kill -ABRT" to force a hanging application to produce a core dump before restarting it. The core dump may be a very large file, but a developer armed with a debugger can use the core dump to find out exactly what the program was doing when it was hung or when it crashed.
- For system-level problems, most modern Linux distributions designed for server use include some type of crash dump functionality. It is typically not enabled by default: read the documentation of your distribution to find out how to enable it and what its requirements are. If your server is hanging, you may need a way to send a hardware-level NMI signal to force the crash dump: read your hardware documentation to see if your server has a button that can be used to send a NMI signal.
- If you suspect there's a hardware-level problem, pay attention to the boot-up messages of the server, and use the hardware diagnostic programs provided by your server manufacturer.
MK
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2011 03:02 AM
04-12-2011 03:02 AM
Re: linux server was hung and causing a web service outage
I'm very new in linux..from the log that given to me..user complaint that they unable to ping to the server and rebooted was performed by our engineer..i have check CPU,memory and swap utilization..everything under threshold..
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.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP