From: Javier Barroso on
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.

google and source code are your friend if you want to understand a
message which you don't understand

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/81c921f31003290438u5c365d39w4a5a0d8cd2bf25cf(a)mail.gmail.com
From: Camaleón on
On Mon, 29 Mar 2010 10:06:46 +0300, Dotan Cohen 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.

I cannot see any "panic" or "kernel oops" in that log.

What is the exact behaviour are you seeing?

I think you should be a little more verbose so people can understand the
big picture and make any suggestion.

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.29.11.47.16(a)gmail.com
From: Jordan Metzmeier on
On Mon, Mar 29, 2010 at 9:50 AM, ceduardo
<carlos.eduardo.virgen(a)gmail.com> wrote:
> 2010/3/28 Dotan Cohen <dotancohen(a)gmail.com>:
>> Is there a good resource for learning to read log files such as the
>> kernel log, messages, dmesg, and such? I have been googling but found
>> nothing really comprehensive yet understandable for a newbie. Where
>> should I start?
>>
>> Thanks!
>>
> You can use "tail" console-command, you can do this:
> tail -f /var/log/messages
> And this one show you step by step the log line.
>> --
>> Dotan Cohen
>>

We are still supporting this guy, even though it appears he is not
running Debian?

--
Jordan Metzmeier


--
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/50e5edd51003290654q7f580276n965123b93b38d91f(a)mail.gmail.com
From: ceduardo on
2010/3/28 Dotan Cohen <dotancohen(a)gmail.com>:
> Is there a good resource for learning to read log files such as the
> kernel log, messages, dmesg, and such? I have been googling but found
> nothing really comprehensive yet understandable for a newbie. Where
> should I start?
>
> Thanks!
>
You can use "tail" console-command, you can do this:
tail -f /var/log/messages
And this one show you step by step the log line.
> --
> 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/880dece01003280911p5718199fna6c24b90071ad685(a)mail.gmail.com
>
>



--
ceduardo


--
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/c068e3701003290650x7ae3333y5ae15e7688fc4402(a)mail.gmail.com
From: Jari Fredriksson on
On 28.3.2010 19:11, Dotan Cohen wrote:
> Is there a good resource for learning to read log files such as the
> kernel log, messages, dmesg, and such? I have been googling but found
> nothing really comprehensive yet understandable for a newbie. Where
> should I start?
>

As has been said, Google is maybe the best answer here. I doubt there is
any comprehensive tutorial, because (while the log file has some -
logger dependent - format), the messages themselves are not standardized.

Each and every application (including Linux kernel) has it's own
messages, and if Googling the message (with the app name added to the
query) does not help; there is always the source code *horror*.

Indeed, while I try to use Debian packaged applications, I remember
having downloaded the source code and tried to understand what the code
is trying to do. While this may sound horrendous, it is IMHO still miles
better than what we have in Windows. Windows log messages are usually
totally bizarre, and there is in most cases not anything in Google, nor
source code available.

Understanding log files is - while not art - sometimes hard labor.
Google, mailing lists, Usenet, those are good to have. Often some one
else has seen the same message, and internet remembers. It has quite
good memory, and it does not pay much to ask.

If you still insist, and want to be the über authority and master of all
log messages, feel free to begin your journey. Such a master most
certainly will get paid as a system admin, and enjoy great salary!

--
http://www.iki.fi/jarif/

If you laid all of our laws end to end, there would be no end.
-- Mark Twain

First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5 6 7 8 9 10
Prev: Flash click problem
Next: (no subject)