Web Hosting Reviews & Ratings

September 30, 2011

Common Linux Server Errors And How To Iron Them Out

We’ve all been there: It’s a nice day, and your servers are running like digital champions. Then, out of nowhere, your Linux distribution throws you a curveball error straight from left field. Before you let the incident wreck your day, though, you should know that most Linux server problems are common enough to be routine, and a quick fix isn’t hard to find.

With that in mind, we’ve compiled a short list of the most common Linux server errors, as well as our speedy remedies for each. If you don’t find what you’re looking for here, remember that Google knows all: A quick search could save you hours of do-it-yourself headache in the long run. Now that you’re informed, check below and keep an open ear, Neo! Your Server Matrix is depending on you.

1.  Command Not Found Error: This is by far the most common error we encounter—within our own servers, even—and we hear a lot about it from other users, as well. In essence, this error is returned when you’ve created a digital boo-boo. If you’ve not spelled a command correctly in the terminal, it won’t run. To correct this, check the exact syntax of the command again. Likewise, if you haven’t installed the application you’re trying to reach, it won’t happen: Same thing goes if you’re trying to access a script in the wrong directory. More than likely, if you get this error, what’s at the core of your problem is a classic ID10T problem.

2.  Permission Denied: We’ll be upfront about this—we hate this error message more than any other. This is because, more often than not, the issue involves chmod settings, in which a file’s permissions have accidentally been set to 0, making them un-editable even for the root user. To correct this, simply run the appropriate chmod command to fix the file in question. If the error persists, next ensure you are in fact the root user, or have entered the necessary root command.

3.  No Route To Host: If you achieve this error message, then you’ve more or less lost the tubing to your server. We’re talking about SSH, but it’s possible for this error to occur in other communication areas, as well. In essence, you’ve lost connection with your server, and your system now has no idea where to pipe your shell commands. To correct the issue, try running traceroute with your fingers crossed and your eyes open.

Tags: linux,  script,  system,  server,  linux server,  servers,  SSH,  Google,  traceroute,  IT,  syntax,  root access,  file permissions,  permission settings,  root directory,  Linux distribution,  server connection,  distribution of Linux