Hello everyone!
I am new baby in Linux & need some troubleshooting commands as I am preparing for my AWS Interview & Linux is main part which attracts lots of questions.Hope to get some good responses.

Happy to give you some answers, as soon as you ask questions. We can help with specific things, but 'troubleshooting commands' is FAR too vague and broad for anyone to even guess at. And add to that, an interviewer can as ANYTHING they want, and accept ANY answer they want. No way to know, except for you to actually know the subject of the job you're interviewing for. If you have the skill and qualifications, you should be all set.

If not, there is nothing here that will do you any good, to be honest. Because even IF we knew the questions they were going to ask, and gave you all the answers...you would not be able to actually do the job after you're hired, would you? Take an honest look at your skills and compare them against the job listing...the worst thing you can do is to get a job you're not qualified for.

1 members found this post helpful.

I would rather say, there is no such thing "troubleshooting commands". There are commands available on linux and they can be used to develop something, calculate something, executing/drawing/whatever and also for troubleshooting.

1 members found this post helpful.

Hi,

Welcome to LQ!

Troubleshooting can be considered an art. You first need to identify the problem and that can be done using logs in '/var/log' or even 'dmesg' to hopefully indicate the issue. If diagnosing a network issue/problem I would likely use the commands; ifconfig, iwconfig and route to certify the setup is correct. You can use 'man command' to get useful information. Your techniques for such issues will be derived from experience to allow you to form proper procedures. If for example you are using wired inet then I would check to make sure the driver is correct for the device from 'lspci' information. If that is correct then I would ping from command line a known location using the proper information. If you get errors then I would then ping the IP of the named location, if that checks OK then my suspicions would be faults with the 'nameserver'. Check to be sure the 'nameserver' is functional with proper IP. If not then check the routing table by using 'route -n' command.

But you must be aware that most issues are from a previous operating hardware can turn out to be a hardware fault. If so then proper hardware diagnostics can be performed on the device in question. These diagnostics are generally provided by the device manufacture.

I use some of the following to aid in diagnosis; Remember that experience will always help you to form a diagnosis. By learning to ID the problem then break things down to the problem area to scope into a point to start testing. Thus allowing the repair either by tweaking or replacing the faulty hardware.