It's a rare occasion that your Linux data center servers will go rogue on you. It does, however, happen. Why? Because nothing is perfect, and when a machine is connected to a network, you never know when something could go awry. When that frightening inevitability does occur, you'll be glad to know you have all the tools necessary to resolve the issue.

Server virtualization best practices and tips on what not to do

Quantum computing: Seven truths you need to know

Any admin worth their weight in bitcoin will start by turning to is logs. Within those wondrous words you will find the keys to many a misbehaving kingdom. For most services (Apache, MySQL, etc.) there are individual logs that can key you into connection, authentication, security, and many more issues. But what happens when the system you need to look into is the server platform itself? When there are hardware issues, what log file do you check?

Read more: certified linux administrator salary

The first place I look is a special command that offers a host of information about various device drivers that are loaded during boot. The information presented via this command can go a long way toward helping you understand what's going on with your Linux system. That command is dmesg. I've been using this tool to troubleshoot Linux servers and desktops for decades. It's time you start making use of this handy command

Hide Comments | Add Comment