Skip to contentSkip to conversation

netconsole problem

DISCUSSION JaniD++ 3 participants 6 messages Feb 10, 2006 – Feb 13, 2006

lore
Share & tools
lore

JaniD++

author
#0 lore raw

Hello, list,

I have a little problem, with netconsole.
It does not work for me.

On the "client":

modprobe netconsole netconsole=@/,[email protected]/ dmesg:
netconsole: local port 6665
netconsole: interface eth0
netconsole: remote port 514
netconsole: remote IP 192.168.2.100
netconsole: remote ethernet address ff:ff:ff:ff:ff:ff
netconsole: local IP 192.168.2.50
netconsole: network logging started

(kernel: 2.6.15-rc5, and 2.6.16-rc1,2)

On the server:
]# netcat -u -l -v -s 192.168.2.100 -p 514 192.168.2.100: inverse host lookup failed: Unknown host listening on [192.168.2.100] 514 ...

And nothing comes.

The firewall is off on both system.
The ping comes from any direction.

If i try the remote and local syslog, it works well, two. And in this case, the netlog only displays what the syslog is sends.

What can be the problem?

Thanks,
Janos

#1 lore raw
Quoted 26 lines · JaniD++

Hello, list,

I have a little problem, with netconsole.
It does not work for me.

On the "client":

modprobe netconsole netconsole=@/,[email protected]/ dmesg:
netconsole: local port 6665
netconsole: interface eth0
netconsole: remote port 514
netconsole: remote IP 192.168.2.100
netconsole: remote ethernet address ff:ff:ff:ff:ff:ff
netconsole: local IP 192.168.2.50
netconsole: network logging started

(kernel: 2.6.15-rc5, and 2.6.16-rc1,2)

On the server:
]# netcat -u -l -v -s 192.168.2.100 -p 514 192.168.2.100: inverse host lookup failed: Unknown host listening on [192.168.2.100] 514 ...

And nothing comes.

Quoted 7 lines

The firewall is off on both system.
The ping comes from any direction.

If i try the remote and local syslog, it works well, two. And in this case, the netlog only displays what the syslog is sends.

What can be the problem?

Perhaps your console log level is set too low. Fedora for instance is very quiet by default.

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

----- Original Message -----
From: "Matt Mackall" <[email protected]>
To: "JaniD++" <[email protected]>
Cc: <[email protected]>
Sent: Sunday, February 12, 2006 6:46 PM
Subject: Re: netconsole problem

Quoted 30 lines · JaniD++
Quoted 29 lines

Hello, list,

I have a little problem, with netconsole.
It does not work for me.

On the "client":

modprobe netconsole netconsole=@/,[email protected]/ dmesg:
netconsole: local port 6665
netconsole: interface eth0
netconsole: remote port 514
netconsole: remote IP 192.168.2.100
netconsole: remote ethernet address ff:ff:ff:ff:ff:ff
netconsole: local IP 192.168.2.50
netconsole: network logging started

(kernel: 2.6.15-rc5, and 2.6.16-rc1,2)

On the server:
]# netcat -u -l -v -s 192.168.2.100 -p 514 192.168.2.100: inverse host lookup failed: Unknown host listening on [192.168.2.100] 514 ...

And nothing comes.

The firewall is off on both system.
The ping comes from any direction.

Quoted 7 lines
Quoted 4 lines

If i try the remote and local syslog, it works well, two. And in this case, the netlog only displays what the syslog is sends.

What can be the problem?

Perhaps your console log level is set too low. Fedora for instance is very quiet by default.

Sorry, i was not clear enough....
The system, what i want to debug is RedHat 9.0, with kernel 2.6.15, 2.6.16-* The syslog server is Fedora, and the syslog to syslog messages is works, but netconsole to syslog (and netconsole to netcat) is the problem, including the init-message!

At this time i try to receive with another redhat 9, but it looks like the netconsole did not working properly for me. :(

Thanks,
Janos

Quoted 8 lines
Signature · 7 lines
-- 
Mathematics is the supreme nostalgia of our time.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
#3 lore raw
Quoted 38 lines · JaniD++
Quoted 30 lines · JaniD++
Quoted 29 lines

Hello, list,

I have a little problem, with netconsole.
It does not work for me.

On the "client":

modprobe netconsole netconsole=@/,[email protected]/ dmesg:
netconsole: local port 6665
netconsole: interface eth0
netconsole: remote port 514
netconsole: remote IP 192.168.2.100
netconsole: remote ethernet address ff:ff:ff:ff:ff:ff
netconsole: local IP 192.168.2.50
netconsole: network logging started

(kernel: 2.6.15-rc5, and 2.6.16-rc1,2)

On the server:
]# netcat -u -l -v -s 192.168.2.100 -p 514 192.168.2.100: inverse host lookup failed: Unknown host listening on [192.168.2.100] 514 ...

And nothing comes.

The firewall is off on both system.
The ping comes from any direction.

Quoted 7 lines
Quoted 4 lines

If i try the remote and local syslog, it works well, two. And in this case, the netlog only displays what the syslog is sends.

What can be the problem?

Perhaps your console log level is set too low. Fedora for instance is very quiet by default.

Quoted 8 lines

Sorry, i was not clear enough....
The system, what i want to debug is RedHat 9.0, with kernel 2.6.15, 2.6.16-* The syslog server is Fedora, and the syslog to syslog messages is works, but netconsole to syslog (and netconsole to netcat) is the problem, including the init-message!

At this time i try to receive with another redhat 9, but it looks like the netconsole did not working properly for me. :(

Netconsole logging level is based off the _console log level_, which defaults to quiet on recent Redhat releases. If it doesn't show up on the console, netconsole doesn't see it either.

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

----- Original Message -----
From: "Matt Mackall" <[email protected]>
To: "JaniD++" <[email protected]>
Cc: <[email protected]>
Sent: Sunday, February 12, 2006 11:43 PM
Subject: Re: netconsole problem

Quoted 34 lines · JaniD++
Quoted 33 lines
Quoted 33 lines · JaniD++
Quoted 32 lines

Hello, list,

I have a little problem, with netconsole.
It does not work for me.

On the "client":

modprobe netconsole netconsole=@/,[email protected]/ dmesg:
netconsole: local port 6665
netconsole: interface eth0
netconsole: remote port 514
netconsole: remote IP 192.168.2.100
netconsole: remote ethernet address ff:ff:ff:ff:ff:ff
netconsole: local IP 192.168.2.50
netconsole: network logging started

(kernel: 2.6.15-rc5, and 2.6.16-rc1,2)

On the server:
]# netcat -u -l -v -s 192.168.2.100 -p 514 192.168.2.100: inverse host lookup failed: Unknown host listening on [192.168.2.100] 514 ...

And nothing comes.

The firewall is off on both system.
The ping comes from any direction.

If i try the remote and local syslog, it works well, two. And in this case, the netlog only displays what the syslog is sends.

Quoted 7 lines
Quoted 7 lines
Quoted 4 lines
Quoted 1 line

What can be the problem?

Perhaps your console log level is set too low. Fedora for instance is very quiet by default.

Sorry, i was not clear enough....
The system, what i want to debug is RedHat 9.0, with kernel 2.6.15,

2.6.16-*

Quoted 1 line
Quoted 1 line

The syslog server is Fedora, and the syslog to syslog messages is works,

but

Quoted 1 line
Quoted 1 line

netconsole to syslog (and netconsole to netcat) is the problem,

including

Quoted 3 lines
Quoted 3 lines

the init-message!

At this time i try to receive with another redhat 9, but it looks like

the

Quoted 5 lines
Quoted 1 line

netconsole did not working properly for me. :(

Netconsole logging level is based off the _console log level_, which defaults to quiet on recent Redhat releases. If it doesn't show up on the console, netconsole doesn't see it either.

The netconsole had worked for me some months ago, but i have made some changes on the system... (some software, more hardware)
OK, i will see it.
Where can i get/set this loglevel?

Thanks,
Janos

Quoted 3 lines
Signature · 2 lines
-- 
Mathematics is the supreme nostalgia of our time.
#5 lore raw
Quoted 61 lines · On Mon, 13 Feb 2006 00:42:00 +0100 JaniD++ wrote:

----- Original Message -----
From: "Matt Mackall" <[email protected]>
To: "JaniD++" <[email protected]>
Cc: <[email protected]>
Sent: Sunday, February 12, 2006 11:43 PM
Subject: Re: netconsole problem

Quoted 34 lines · JaniD++
Quoted 33 lines
Quoted 33 lines · JaniD++
Quoted 32 lines

Hello, list,

I have a little problem, with netconsole.
It does not work for me.

On the "client":

modprobe netconsole netconsole=@/,[email protected]/ dmesg:
netconsole: local port 6665
netconsole: interface eth0
netconsole: remote port 514
netconsole: remote IP 192.168.2.100
netconsole: remote ethernet address ff:ff:ff:ff:ff:ff
netconsole: local IP 192.168.2.50
netconsole: network logging started

(kernel: 2.6.15-rc5, and 2.6.16-rc1,2)

On the server:
]# netcat -u -l -v -s 192.168.2.100 -p 514 192.168.2.100: inverse host lookup failed: Unknown host listening on [192.168.2.100] 514 ...

And nothing comes.

The firewall is off on both system.
The ping comes from any direction.

If i try the remote and local syslog, it works well, two. And in this case, the netlog only displays what the syslog is sends.

Quoted 7 lines
Quoted 7 lines
Quoted 4 lines
Quoted 1 line

What can be the problem?

Perhaps your console log level is set too low. Fedora for instance is very quiet by default.

Sorry, i was not clear enough....
The system, what i want to debug is RedHat 9.0, with kernel 2.6.15,

2.6.16-*

Quoted 1 line
Quoted 1 line

The syslog server is Fedora, and the syslog to syslog messages is works,

but

Quoted 1 line
Quoted 1 line

netconsole to syslog (and netconsole to netcat) is the problem,

including

Quoted 3 lines
Quoted 3 lines

the init-message!

At this time i try to receive with another redhat 9, but it looks like

the

Quoted 2 lines
Quoted 1 line

netconsole did not working properly for me. :(

Quoted 8 lines
Quoted 3 lines

Netconsole logging level is based off the _console log level_, which defaults to quiet on recent Redhat releases. If it doesn't show up on the console, netconsole doesn't see it either.

The netconsole had worked for me some months ago, but i have made some changes on the system... (some software, more hardware)
OK, i will see it.
Where can i get/set this loglevel?

via Magic Sysrq + number (e.g., alt-sysrq-9)
or via (as root) "echo 9 > /proc/sysrq-trigger"
or via (as root) "echo 9 4 1 7 > /proc/sys/kernel/printk" (first "cat /proc/sys/kernel/printk" and increase the first value).

For the first one, you need a kernel that has
CONFIG_MAGIC_SYSRQ=y
and also has /proc/sys/kernel/sysrq = 1
(echo 1 > /proc/sys/kernel/sysrq # to enable it)

---
~Randy