Linux Troubleshooting 101-Log Files

Posted by JD 02/11/2013 at 15:12

Have you checked the system logs?

$ sudo egrep -i ‘error|warning’ /var/log/*log

will find issues in the logs.

Almost any issue will leave a trace in the system logs.
Start with that to see any issues.

Log files are usually protected for security reasons, hence the need to use sudo.

Of course, sometimes it isn’t a system problem, but an application issue, so the important log file(s) will be with the application or in /tmp/ somewhere. Not all applications provide logging by default, but many support increased logging levels through an application setting. Sometimes an option passed into the program will control verbosity.

$ program -v 

or
$ program -vvv 

enable and increases the amount of logging output by the program. For some programs using more v s means more verbosity.

For networking issues, check the logs on other devices, especially the router.

If the commands above are not understood, then you probably should ask for more individual help from someone knowledgeable who can be in the same room. Getting help like that is possible from your local LUG, Linux Users Group. Also check with your local university or college for a LUG.