Skip to contentSkip to conversation

What's the matter with build-in netconsole?

DISCUSSION Park Lee 4 participants 7 messages Dec 16, 2004

lore
Share & tools
lore

Park Lee

author
#0 lore raw

Hi,
I try to use netconsole to keep Linux kernel oops to
another machine. I've compiled netconsole into the kernel (i.e. select CONFIG_NETCONSOLE=y, when run 'make menuconfig').
After that, I put
"netconsole=@/,[email protected]/00:02:3F:03:D2:59" (which is described in /usr/src/linux/Documentation/networking/netconsole.txt) to the kernel command line as provided by grub and rerun my machine with the new compiled kernel.
But then, when the system is booting, it shows the
following message:

... ...
Uncompressing Linux... Ok, booting the kernel. audit(1103234064.4294965842:0): initialized
netconsole: eth0 doesn't exist, aborting.
... ...

Then, What's the matter with the build-in
netconsole? Have I misconfiged the netconsole? and How to really run build-in netconsole?

Thank you.

=====
Best Regards,
Park Lee

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

#1 lore raw
Quoted 9 lines · Park Lee

[...]
But then, when the system is booting, it shows the
following message:

... ...
Uncompressing Linux... Ok, booting the kernel.
audit(1103234064.4294965842:0): initialized
netconsole: eth0 doesn't exist, aborting.
... ...

Just a shot in the dark here... maybe your compiling your network driver as a module and netconsole can not use it because it is not loaded soon enough.

If this is the case you should compile your network driver builtin.

Signature · 4 lines
Paulo Marques - www.grupopie.com

"A journey of a thousand miles begins with a single step."
Lao-tzu, The Way of Lao-tzu
author
#2 lore raw

Issue on netconsole vs. Linux kernel oops

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 "[email protected]/,[email protected]/", 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.

Then, Where are these messages go? Do they disappear
themselves?
Is this a fault in netconsole or in syslogd, or Am I
miss to configure something obvious? Would you please give me some hints on solving this problem?

Thank you very much.

=====
Best Regards,
Park Lee

__________________________________
Do you Yahoo!?
Jazz up your holiday email with celebrity designs. Learn more.
http://celebrity.mail.yahoo.com

#3 lore raw

Re: Issue on netconsole vs. Linux kernel oops

Quoted 37 lines · Park Lee

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 "[email protected]/,[email protected]/", 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
... ...

Quoted 7 lines

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.

Signature · 1 line
Mathematics is the supreme nostalgia of our time.
#4 lore raw

Re: Issue on netconsole vs. Linux kernel oops

Quoted 38 lines · Matt Mackall
Quoted 37 lines · Park Lee

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 "[email protected]/,[email protected]/", 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
... ...

Quoted 11 lines
Quoted 7 lines

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.

Signature · 1 line
Mathematics is the supreme nostalgia of our time.

Depends upon the vendor of your installation, but some require loghost to be defined in /etc/hosts as the same as localhost and /etc/nsswitch.conf configured to actually look at that.

Cheers,
Dick Johnson
Penguin : Linux version 2.6.9 on an i686 machine (5537.79 BogoMips).
Notice : All mail here is now cached for review by Dictator Bush.
98.36% of all statistics are fiction.

author
#5 lore raw

Re: Issue on netconsole vs. Linux kernel oops

Quoted 5 lines · Dick Johnson

Depends upon the vendor of your installation, but some require loghost to be defined in /etc/hosts as the same as localhost and /etc/nsswitch.conf configured to actually look at that.

Now, I'm using Fedora Core 2. Would you please tell us Is there any limitation of it?

Thank you.

=====
Best Regards,
Park Lee

__________________________________
Do you Yahoo!?
Yahoo! Mail - Find what you need with new enhanced search.
http://info.mail.yahoo.com/mail_250

#6 lore raw
In reply to Park Lee
Quoted 9 lines · Park Lee

Hi,
I try to use netconsole to keep Linux kernel oops to
another machine. I've compiled netconsole into the kernel (i.e. select CONFIG_NETCONSOLE=y, when run 'make menuconfig').
After that, I put
"netconsole=@/,[email protected]/00:02:3F:03:D2:59" (which is described in /usr/src/linux/Documentation/networking/netconsole.txt)

You have to configure a source IP address for built-in netconsole, as interfaces normally don't have addresses assigned to them until init.

Quoted 11 lines

to the kernel command line as provided by grub and rerun my machine with the new compiled kernel.
But then, when the system is booting, it shows the
following message:

... ...
Uncompressing Linux... Ok, booting the kernel. audit(1103234064.4294965842:0): initialized
netconsole: eth0 doesn't exist, aborting.
... ...

Quoted 3 lines

Then, What's the matter with the build-in
netconsole? Have I misconfiged the netconsole? and How to really run build-in netconsole?

Is your network driver built in? Is it eth0 (you let netconsole use the default)? Is it initialized before netconsole? Please send your _entire_ dmesg.

Signature · 1 line
Mathematics is the supreme nostalgia of our time.