From: Matt Mackall <mpm@selenic.com>
To: Park Lee <parklee_sel@yahoo.com>
Cc: Paulo Marques <pmarques@grupopie.com>,
mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: Issue on netconsole vs. Linux kernel oops
Date: Thu, 16 Dec 2004 10:55:22 -0800 [thread overview]
Message-ID: <20041216185522.GI2767@waste.org> (raw)
In-Reply-To: <20041216184827.7357.qmail@web51501.mail.yahoo.com>
On Thu, Dec 16, 2004 at 10:48:27AM -0800, Park Lee wrote:
> Hi,
> I'd like to use netconsole to send local Linux
> kernel's final messages (i.e. oops) to remote machine
> when the kernel crashes.
> Now I can successfully use a built-in netconsole to
> send some loacl kernel messages to the remote machine.
> (the parameter I send to local kernel on kernel
> command line is
> "netconsole=@192.168.0.2/,514@192.168.0.1/", I run
> syslogd in remote machine). For example, When the
> local kernel is booting, it will send a message
> "192.168.0.2 audit(1103247021.091:0): initialized" to
> remote machine through netconsole, and the syslogd on
> remote machine will write the message to
> /var/log/messages on remote machine.
> What CONFUSE me most is that when the kernel
> crashes, there is NO message (oops) about the crash
> being wrote down by syslogd on remote machine to
> remote /var/log/messages file at all!!
> But in the mean time, We can see the outputs of
> tcpdump on the remote machine, they are some thing
> like the following:
>
> 01:36:56.692877 IP 192.168.0.2.6665 >
> 192.168.0.1.syslog: UDP, length 48
> 01:36:56.692930 IP 192.168.0.2.6665 >
> 192.168.0.1.syslog: UDP, length 29
> 01:36:56.692982 IP 192.168.0.2.6665 >
> 192.168.0.1.syslog: UDP, length 15
> 01:36:56.693034 IP 192.168.0.2.6665 >
> 192.168.0.1.syslog: UDP, length 9
> 01:36:56.693086 IP 192.168.0.2.6665 >
> 192.168.0.1.syslog: UDP, length 16
> 01:36:56.693121 IP 192.168.0.2.6665 >
> 192.168.0.1.syslog: UDP, length 16
> ... ...
>
> From these messages, we can see that the netconsole
> actually have sent the final messages (oops) to remote
> machine when the local kernel crashed. But there are
> no corresponding messages recorded by syslogd on
> remote machine to /var/log/messages.
>From your description, it sounds like syslogd is at fault. Try using
netcat on the remote machine.
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2004-12-16 18:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-16 14:35 What's the matter with build-in netconsole? Park Lee
2004-12-16 15:00 ` Paulo Marques
2004-12-16 18:48 ` Issue on netconsole vs. Linux kernel oops Park Lee
2004-12-16 18:55 ` Matt Mackall [this message]
2004-12-16 19:06 ` linux-os
2004-12-16 19:31 ` Park Lee
2004-12-16 18:44 ` What's the matter with build-in netconsole? Matt Mackall
2004-12-17 12:12 Issue on netconsole vs. Linux kernel oops Park Lee
2004-12-17 16:44 ` Matt Mackall
2004-12-17 17:03 ` Bill Rugolsky Jr.
2004-12-18 6:01 ` Park Lee
2004-12-18 7:41 ` Matt Mackall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041216185522.GI2767@waste.org \
--to=mpm@selenic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=parklee_sel@yahoo.com \
--cc=pmarques@grupopie.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.