How to read log files
in [Debian]
|
Prev: Flash click problem
Next: (no subject)
From: Javier Barroso on 29 Mar 2010 15:10 On Mon, Mar 29, 2010 at 5:29 PM, Celejar <celejar(a)gmail.com> wrote: > On Mon, 29 Mar 2010 13:38:14 +0200 > Javier Barroso <javibarroso(a)gmail.com> wrote: > >> On Mon, Mar 29, 2010 at 9:06 AM, Dotan Cohen <dotancohen(a)gmail.com> wrote: >> >> Why don't you just post what you've got? You will most probably find >> >> someone who can explain not only where the problem is but how to read >> >> it, too. >> >> >> > >> > In the general sense my intention was to learn and not lazy-web the >> > list. But you are right, attached is /var/log/messages. >> >> My 2 cents: read and understand log messages when you are in trouble, >> if system is working well, you don't need understand these logs. > > I think that, on the contrary, it's very important to get familiar with > the system's logs under normal conditions. This way, when you do have > a problem, you'll know what's normal and what are the important lines. That is correct too, logs he sent was kernel logs. kernel logs are "generally" difficult to understand (they are hardware related) and in normal conditions they won't tell you nothing important until you want "play" with the system deeper However, application logs are easier to understand (I think) and it is good reading it like you said Regards, -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/81c921f31003291204mba09425r13402b283081496e(a)mail.gmail.com
From: Dotan Cohen on 30 Mar 2010 16:20 > Mar 28 09:14:19 sfd kernel: [ Â Â 0.000000] Linux version > 2.6.31-20-generic (buildd(a)palmer) (gcc version 4.4.1 (Ubuntu > 4.4.1-4ubuntu8) ) #58-Ubuntu SMP Fri Mar 12 05:23:09 UTC 2010 (Ubuntu > 2.6.31-20.58-generic) > > Doesn't look like Debian to me... > Ubuntu is a Debian derivative, Jordan. I think that the name is an ancient African word for "Debian for noobies". -- Dotan Cohen http://bido.com http://what-is-what.com -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/880dece01003301317n6f8ce942rae1850aff7e32fb4(a)mail.gmail.com
From: Dotan Cohen on 30 Mar 2010 16:30 > My 2 cents: read and understand log messages when you are in trouble, > if system is working well, you don't need understand these logs. > But in that case I would not be able to identify the faulty lines in the log. I need to know what a healthy log looks like, to diagnose a sick one. > google and source code are your friend if you want to understand a > message which you don't understand > At this point I would be googling all the messages, so if there is a fine manual which documents the messages in /var/log/messages then that would be great. -- Dotan Cohen http://bido.com http://what-is-what.com -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/880dece01003301319p2b776abao907b97509333526a(a)mail.gmail.com
From: Camaleón on 30 Mar 2010 16:40 On Tue, 30 Mar 2010 23:20:59 +0300, Dotan Cohen wrote: >> I cannot see any "panic" or "kernel oops" in that log. >> >> What is the exact behaviour are you seeing? >> >> > The machine is locking up and the keyboard leds flash. When the machine locks, try to access it via ssh. >> I think you should be a little more verbose so people can understand >> the big picture and make any suggestion. >> >> > I was asking in the general sense because my intention is to learn, not > to have someone do the legwork for me! Yours was a very "broad" question, nothing that can be answered with "yes or no" or "go here, read and you're done" ;-) Understanding the bottoms of a kernel oops or panic is something only kernel devels or people with high knowledge of C can achieve. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/pan.2010.03.30.20.28.34(a)gmail.com
From: Wayne on 30 Mar 2010 16:50
Dotan Cohen wrote: >> My 2 cents: read and understand log messages when you are in trouble, >> if system is working well, you don't need understand these logs. >> > > But in that case I would not be able to identify the faulty lines in > the log. I need to know what a healthy log looks like, to diagnose a > sick one. > If you are not having a problem right now, look at the logs now. If you are having a problem, look at the logs. It does not take a Rocket Scientist to spot a problem. > >> google and source code are your friend if you want to understand a >> message which you don't understand >> > > At this point I would be googling all the messages, so if there is a > fine manual which documents the messages in /var/log/messages then > that would be great. > You spend more time giving excuses then necessary. Look in the log of interest until you see something that looks like it might be different then the other entries, then Google it. If, and only if, google doesn't give you an answer you can't understand, use this list. As a last resort buy a book on linux that covers the subject you want answered. Ok, ready for more excuses...... Wayne -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/4BB26294.3050602(a)gmail.com |