Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751538AbWBMBQj (ORCPT ); Sun, 12 Feb 2006 20:16:39 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751539AbWBMBQj (ORCPT ); Sun, 12 Feb 2006 20:16:39 -0500 Received: from xenotime.net ([66.160.160.81]:50305 "HELO xenotime.net") by vger.kernel.org with SMTP id S1751537AbWBMBQi (ORCPT ); Sun, 12 Feb 2006 20:16:38 -0500 Date: Sun, 12 Feb 2006 17:17:23 -0800 From: "Randy.Dunlap" To: "JaniD++" Cc: mpm@selenic.com, linux-kernel@vger.kernel.org Subject: Re: netconsole problem Message-Id: <20060212171723.3c69b209.rdunlap@xenotime.net> In-Reply-To: <018701c6302d$ebf2fe70$9d00a8c0@dcccs> References: <00af01c62e4d$8de8c6c0$9d00a8c0@dcccs> <20060212174645.GA13703@waste.org> <017f01c63026$187a8150$9d00a8c0@dcccs> <20060212224340.GF10467@waste.org> <018701c6302d$ebf2fe70$9d00a8c0@dcccs> Organization: YPO4 X-Mailer: Sylpheed version 2.0.4 (GTK+ 2.8.3; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3185 Lines: 91 On Mon, 13 Feb 2006 00:42:00 +0100 JaniD++ wrote: > > ----- Original Message ----- > From: "Matt Mackall" > To: "JaniD++" > Cc: > Sent: Sunday, February 12, 2006 11:43 PM > Subject: Re: netconsole problem > > > > On Sun, Feb 12, 2006 at 11:45:52PM +0100, JaniD++ wrote: > > > > On Fri, Feb 10, 2006 at 03:23:23PM +0100, JaniD++ wrote: > > > > > Hello, list, > > > > > > > > > > I have a little problem, with netconsole. > > > > > It does not work for me. > > > > > > > > > > On the "client": > > > > > > > > > > modprobe netconsole netconsole=@/,514@192.168.2.100/ > > > > > 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? > > > > > > > > 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. :( > > > > 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/