They may be system administrators, website maintainers, or may just use MySQL for personal uses. Being such a valuable service, it has to have a log file dedicated. All success, failure, or debug messages are logged here. This directory contains the logs of the Apache server on the system. System and command-line integrated E-mail services were widely used until a few years ago. Clear by the name itself, mail. Now we can finally get to a significant point, which is reading those logs.
There are various ways in which you can, and in which you would need to read the logs. For example, if you want just to see the ending part of the log file to know about the most recent activity , you can use the tail command. The command only prints the last 10 lines of a file. On the other hand, if you want to navigate through the whole file and search for things, you can use the infamous less command. You can use the Up and Down keys to navigate through the file.
The searched term should be highlighted. There are several graphical programs to help the users read the log files on a system. Today, we shall take a look at glogg. The official website describes it as a combination of the less and grep commands. You can open glogg, and then open a log file using the button provided on the top left to open up a log file. This makes it easier to open up the log file.
The command looks like:. The log is shown in the major window. There is a search box on the bottom, in which you can search whatever term that you are looking for.
There is also a frequency bar on the right, which shows how frequently the searched term shows up in the log file. You can find additional help for the installation here. This means that new versions of a log file are created regularly, as the log files have certain storage limits or time-based constraints.
If you issue the command:. These are just older versions of the same file. The conditions for log rotations can be configured. But boot. Most of the stuff interesting for diagnostics is in kern. For custom Nemo actions, useful scripts for the Cinnamon desktop, and Cinnamox themes visit my Github pages. Code: Select all inxi -Fxz. If I have helped you solve a problem, please add [ SOLVED] t o your first post title , it helps other users looking for help, and keeps the forum clean.
Regards, Deepak Mint Post by deepakdeshp » Thu Apr 04, am There is a mention of F and xz in your statement though. Post by vineyridge » Thu Apr 04, pm Here are the error messages from Code: Select all dmesg grep error. Sense: Unrecovered read error - auto reallocate failed [ 3. At the end of this article we will outline the way to see the logs via GUI. These are known to be the rotated log files.
Indeed, Logrotate, which is a default system utility, handles automatically this rotation as well as the compression of log files.
You may be interested to read our articles about compression tools on Linux such as Tar and Gzip. For those acquainted with the nano editor, you can run the command below in order to edit a log file,. You will be prompted to Save in case you made changes, but in most cases you do not change the log file. You can find a complete guide about nano in our article on how to use nano.
To look at the content of a file, you can use the less command, which displays one screen at a time:. In order to see the first 10 lines of a log file, you could use the head command as follows:. You can add the -n option to see some other number of lines , for instance, to see the first four lines of the file boot. Now to view the last 10 lines of the log file, use the command tail as shown below:. To see this in action, run the command below using your specific log file :.
Since log files can grow to large sizes, the grep command can help you strip out the content of interest. The snapshot above shows the lines in the file kern. In case the returned result spans many pages, you can pipe it out to the command less as follows :.
In order to display the content of log files using a simple, easy to use, graphical tool, open up the Log File Viewer utility from your Dash :.
Once you click on the Log file Viewer shortcut, you would need to press the install button if it is not installed in your computer. Once this is done, hit the Launch button and you are all set. By default, the Log File Viewer, as shown above in the snapshot, shows a number of logs, including your package manager log file dpkg. You will be able to display the logs in a separate window in case a new log event is inserted, it will show up automatically in this window.
If you want to view other log files, for instance, a specific application log file, you can just click on the the File menu :. Then select Open, to open the log file from its location. It will show up alongside the standard log files and will be automatically updated and monitored much like the other logs. As mentioned earlier in this article, you can display a message manually in the log file syslog by issuing the command :.
Premise: My final goal is to understand why the autostart sequence is broken probably due to certain packages' autostart fail. Debian 8 itself boots normally but autostart features doesn't work properly.
If you use systemd as your init system, you may need to use systemctl to debug boot problems. You can still obtain a lot of information on the boot process with the command dmesg. But if you use fbautostart , as I suppose, your problem should appear during the start of the window manager. As fbautostart is relatively trivial the best way, is probably to start by commenting everything, then commenting out, i.
I have found it to be most helpful in fixing errant packages that systemd starts or attempts to start. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Where do I find boot log in Debian 8 to debug autostart issues?
Ask Question. Asked 5 years, 11 months ago.
0コメント