- Paperback: 240 pages
- Publisher: Addison Wesley; 1 edition (13 Nov. 2012)
- Language: English
- ISBN-10: 0321832043
- ISBN-13: 978-0321832047
- Product Dimensions: 17.5 x 1.3 x 23.1 cm
- Average Customer Review: 5.0 out of 5 stars See all reviews (4 customer reviews)
Amazon Bestsellers Rank:
67,041 in Books (See Top 100 in Books)
- #1 in Books > Computers & Internet > Software & Graphics > Internet Applications > Web-server Software > UNIX & Linux
- #30 in Books > Computers & Internet > Software & Graphics > Internet Applications > Web-server Software > UNIX & Linux Operating Systems > Linux Distributions
- #773 in Books > Computers & Internet > Web Development > E-commerce > Web Administration
- See Complete Table of Contents
DevOps Troubleshooting: Linux Server Best Practices Paperback – 13 Nov 2012
|New from||Used from|
- Choose from over 13,000 locations across the UK
- Prime members get unlimited deliveries at no additional cost
- Find your preferred location and add it to your address book
- Dispatch to this address when you check out
Frequently Bought Together
Customers Who Bought This Item Also Bought
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your e-mail address or mobile phone number.
About the Author
Kyle Rankin, a senior systems administrator and DevOps engineer, is president of the North Bay Linux Users’ Group and is an award-winning columnist for Linux Journal. Rankin speaks frequently on open source software at SCALE, OSCON, Linux World Expo, Penguicon, and many Linux user groups. His other books include The Official Ubuntu Server Book; Knoppix Hacks, Second Edition; Knoppix Pocket Reference; and Linux Multimedia Hacks. He is also coauthor of Ubuntu Hacks.
Inside This Book(Learn More)
What Other Items Do Customers Buy After Viewing This Item?
Top Customer Reviews
I'm primarily a Java developer, and working as a contractor in small startup companies I often have to work across the entire stack from instance/OS administration right though to creation of web-based UIs. The term 'DevOps' is obviously getting a lot of attention in the computing/development press, and the type of companies I work for are increasingly expecting this to be a skill I should have (even if they don't know exactly what DevOps encompasses!).
I needed to improve my DevOps skills fast, and coming at this from a developer's point-of-view the primary skills I need to learn are the Ops-based System Administration (sysadmin) tasks - this book meets that requirement exactly. The book is small, but don't take this as a negative - it is highly focused, and contains a wealth of knowledge. I managed to devour the contents over a day, mainly by reading a chapter, taking a pause to experiment with my new-found knowledge and commands using a Linux-based box, and then dipping back into the book if I got stuck.
A particular use case that this book matches perfectly is the new wave of developers deploying to the Cloud. Over the past few years I am increasingly deploying a client's app to Cloud-based infrastructure such as AWS (EC2, RDS etc), and the rules of engagement are quite different here in comparison to when deploying to in-house boxes. I've lost count of the amount of time I've thrown away trying to figure out performance problems with Cloud apps - is the app poorly designed, or am I IO/Compute/network bound?Read more ›
Most Helpful Customer Reviews on Amazon.com (beta)
From reading DevOps Troubleshooting, I really enjoyed this focus on troubleshooting. Kyle Rankin touched on troubleshooting in the Ubuntu Server book for a chapter, covering many issues but really only so much can be written in a chapter. Glad to see that the demand for this topic lead to a whole book on the topic, especially since troubleshooting is really an art that so many, including myself, need practice on.
The book covers the basics in the beginning about the basics of troubleshooting, how to make smart choices in testing the problem. This will give you a good base of building on your troubleshooting skills, instead of using a shotgun approach to solving problems. Also covers managing communication between teams. If you have ever worked on a critical issue, you know how dreaded it can be to "join the voice bridge", all the while working on the problem.
The chapters cover the general checks of the Linux operating system from reading performance details, using basic tools like top to find why the system is slow. Other topics also covered are boot problems, disk space issues, tracking down problems between two hosts, dns, e-mail basics, web and SQL server basics, and hardware problems. Each chapter includes details on the basics of the technology, then briefing on the tools, then how to check or validate the service is working.
While it sounds like this is a general command guide book, or a summary of man pages, the author also includes details why to use this tool or another, plus describes the path of troubleshooting. Personally, with only a few years of Linux experience I felt that I knew most of the tools mentioned, but the book really helped me use the tools in a much more efficient manner. Also Kyle Rankin describes each tool in detail to get all of the most usable information. I'll admit, I never knew what "wa" stood for in top and now it will be my top values to check on a system.
One of the key points Kyle Rankin mentions in the book is the technology known the least will often be the most blamed problem. I agree 100% on this, and this book really gives no one the excuse to blame another team since they can rule out the issue themselves. Often I've seen DNS blamed endless times for random issues that no one else could explain.
Overall, I really recommend this book to Linux users in production roles where they need to streamline their troubleshooting steps. But this book is also highly recommended for general Linux users as everyone will run into strange issues either at work or home. Personally, I found this book to help my knowledge in the subjects covered and will be sending a recommendation to my team at work to read this. I'm sure that even the more experience users will find new information from the book or at the very least, this will be a good reference book to send new users instead of explaining troubleshooting themselves.
After reading this book, I did have some suggestions, if there was a 2nd edition. While the book focuses on Linux, more so on Debian than Red Hat, I would have liked to see some details on BSD. This is not an entire deal breaker, as BSD is less popular than Linux, and often the commands are not entirely the same. Another suggestion would be more real world examples of trouble shooting a problem. For example, a step by step time line of the problem, how it was reported, solved, and post mortem on what caused the issue. This might be a good read for people new to fast troubleshooting skills and want to understand which tool fits where in the steps.
Besides these minor suggestions, the book is excellent and I'm keeping the hard copy on my desk at work for reference.
While it covers a broad range of topics, the book itself is pretty short and doesn't go into much detail as I thought it would (those 240 pages go by very fast). I left it at our work library and it is a great reference when someone client is complaining about a random performance issue on their dedicated server that leaves us all puzzled.
Overall, this book is definitely worth reading at least once, but you will probably want/need it as a reference as well :)
DevOps Troubleshooting: Linux Server Best Practices starts with a discussion of best practices in troubleshooting. This lays a good foundation for the rest of the book and should be read right away. If you don't already know how to narrow down the location or source of a problem, how to communicate with others who may be affected or who can assist, or even where to start when a problem arises, the first chapter gives a solid plan to help you out. Most of the content of this chapter will seem obvious to people with experience, but they were not obvious to us when we started, and this information would have saved most of us a few headaches. Ideas like favoring quick, simple tests over slow and complex one, favoring past solutions that are known to work, and most importantly, understanding how the systems work before doing anything are vital. I like the advice about using the internet, but carefully, and resisting rebooting as a cure-all (because it doesn't help you find the cause of the problem).
The chapters that follow are each focused on a specific type of problem. They include discussions of tips, tricks, and tools for diagnosing, and fixing issues. There are chapters that cover server slowness due to CPU, RAM, and Disk I/O issues, boot problems, full or corrupt disk issues, network problems, DNS server issues, email problems, web server problems, and database problems. There is even a chapter on diagnosing common hardware problems.
Experienced Linux server gurus may pick up a trick or two, but it is those who are new to working with Linux servers who are most likely to benefit from this book, and benefit in significant ways. The book doesn't cover how to use Linux or how to set up your server, but it covers exactly what the title of the book says it will cover. For this reason, I consider this a perfect second Linux book for anyone who is relatively new to any aspect of DevOps with Linux.