Messages in this thread | | | Date | Thu, 7 Jun 2007 09:57:44 -0500 | From | Matt Mackall <> | Subject | Re: Kernel 2.6.22-rc4 netconsole & syslogd bug |
| |
On Wed, Jun 06, 2007 at 06:00:10PM -0400, Justin Piszcz wrote: > 1. I use netconsole on almost all of my machines. > 2. When I reboot one of them, it sends the kernel messages to the console > logging server. > 3. However, whenever I reboot it spams the console and every xterm open > with the following: > > Message from syslogd@p34 at Wed Jun 6 17:43:10 2007 ... > p34 sdb3> > > Message from syslogd@p34 at Wed Jun 6 17:43:10 2007 ... > p34 sda3> > > Message from syslogd@p34 at Wed Jun 6 17:43:10 2007 ... > p34 sdb2> > > Message from syslogd@p34 at Wed Jun 6 17:43:10 2007 ... > p34 sda2> > > Message from syslogd@p34 at Wed Jun 6 17:43:10 2007 ... > p34 sdb1> > > Message from syslogd@p34 at Wed Jun 6 17:43:10 2007 ... > p34 sda1> > > I also tried: > > # Send p34 messages to their own file. > @192.168.0.1 /var/log/p34.log
Your syslogd is probably getting confused by messages of the form <foo> (and it rightly should be) and deciding they're maximal priority. You probably have a separate clause somewhere that directs all emergency messages to the console.
> Do I need to be running some sort of special netconsole server and send to > a different port to avoid this spam?
A lot of people simply run netcat.
-- 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 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/
| |