Red Hat Insights: November 2016 archives

  • Don’t panic! Don’t let your kernel do it either.

    A system crash can be one of the most frustrating issues that administrators can encounter in their day to day work. They often strike without warning, require hard reboots, and can kill a process uncleanly, leaving various locked files in place that an admin must go back and manually clean up. These kind of interruptions can take a few minutes to a few hours to overcome. That’s time you could be spending engineering new solutions that change the world, or at the very least, drinking some...
    Posted 2016-11-11T17:54:37+00:00 - 0
  • The only thing worse than a crash is not knowing why it happened. Insights can make sure kdump is there for you.

    Recovery is by far the most important first step to take after a system goes down. However, after your systems have recovered, you'll want to perform some level of root cause analysis in order to understand why the crash happened and how to prevent future similar events. This type of analysis is impossible to perform without access to pre-crash system information. Several weeks ago we published a blog entitled Disaster Recovery, which outlined how many systems would be unable to properly...
    Posted 2016-11-04T19:46:23+00:00 - 0
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.