Login or Register to Ask a Question and Join Our Community


Linux

Netconsole help

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems Linux Netconsole help
# 1  
Old 10-27-2014
Netconsole help
Hello all,
I am trying to get netconsole to send syslog messages to a another server running syslogd. Both machines are slackware 14.1. The destination server has syslogd set to allow network/remote entries.

I have my home router set to use this server as a syslogger. That is working fine. I can send a test message to it via "logger -n dest_system test_message" from the source machine.

My source machine will not send any logging data to the dest syslogger though. I have tried configuring netconsole as a module, and as built in directly, along with options specified at boot up. No combination seems to do the trick. Right now I have netconsole directly included in kernel, not as module, with the below entry in my lilo.conf.

append = "netconsole=6666@192.168.1.12/eth0,514@192.168.1.10/4c:72:b9:43:1f:ee loglevel=7 panic=0"

Every how-to page and man page makes it sound like this should be a simple one-line config to get started. But no joy. I have tried omitting, and including source port/IP, and dest mac. I have also tried omitting loglevel and panic entries. I have tried different source ports. Not a single message is sent to the destination syslogger. There are no errors in the bootup. It seems to accept the boot time params.
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. Linux

netdump/netconsole module

I receive the error belong when attempting to load the netconsole module. Does anyone know how I can resolve this? I downloaded RPM from internal site, so it is trusted. >uname -a Linux indigo 2.6.9-34.ELsmp #1 SMP Fri Feb 24 16:56:28 EST 2006 x86_64 x86_64 x86_64 GNU/Linux > modprobe -a... (0 Replies)
Discussion started by: vada010
0 Replies
Login or Register to Ask a Question

LEARN ABOUT OSF1

syslog_evm.conf

syslog_evm.conf(4)					     Kernel Interfaces Manual						syslog_evm.conf(4)

NAME

       syslog_evm.conf - EVM syslog subscription configuration file

SYNOPSIS

       facility.priority

DESCRIPTION

       The  syslog_evm.conf file is a text file that specifies what syslog messages will be forwarded from the syslog daemon to the Event Manager,
       EVM,in the form of EVM events.  Those syslog messages are posted to the EVM daemon evmd by syslogd if the syslogd  forwarding  function	is
       turned on with the -e flag.  Events are posted with the EVM name of sys.unix.syslog.facility-name.

       This configuration file is read every time syslogd starts, or is restarted by a SIGHUP signal.  If the file does not exist, or if it exists
       but contains no subscription lines, no syslog messages will be posted to EVM.

       Each line in the file controls the forwarding of one syslog event.  Lines beginning with the # character are considered	comments  and  are
       ignored.  Only one subscription per line is permitted.  Mixing a subscription and a comment on the same line is not allowed.

       Each  line has the format facility.priority[+].	Specifies the part of the system that generated the message.  Legal values are the follow-
       ing: All messages.  Messages generated by the kernel.  Messages generated by user processes.  Messages generated by the mail system.   Mes-
       sages  generated  by  system  daemons.	Messages generated by the authorization system.  Messages generated internal to the syslog system.
       Messages generated by the line printer spooling system.	Messages generated by the system news command.	Messages generated by the UNIX	to
       UNIX  copy  system.   Messages  generated by the system clock daemon.  Messages generated by remote file systems.  Available for local use.
       Indicates the priority of the message.  If the priority is followed by a + character, events which are of the specified priority or  higher
       are forwarded; otherwise only events which exactly match the priority are forwarded.

	      The priority level must be one of the following: Forward messages of any priority.  Forward messages of emergency priority.  Forward
	      messages of alert priority.  Forward messages of critical priority.  Forward messages of error priority.	Forward messages of  warn-
	      ing priority.  Forward messages of notice priority.  Forward messages of information priority.  Forward messages of debug priority.

EXAMPLES

       This  example causes syslogd to forward events to EVM as follows: All messages of emergency priority are forwarded.  All messages generated
       in the kernel which have a priority of info or greater are forwarded.  All messages generated by users, by the mail  subsystem  or  by  the
       system daemons which have a priority of info or greater are forwarded.

       *.emerg kern.info+ user.notice+ mail.notice+ daemon.notice+

FILES

       Location  of the system logger configuration file.  Location of the EVM syslog subscription configuration file.	Location of the EVM logger
       configuration file.

SEE ALSO

       Commands: evmd(8), evmlogger(8), syslog(1), syslogd(8)

       Routines: syslog(3)

       Event Management: EVM(5)
       delim off

																syslog_evm.conf(4)