>> >>>> "Ulrich Windl" <ulrich.wi...@rz.uni-regensburg.de> schrieb am
>> >>>> 28.07.2010
> um
16:46 in Nachricht <4c505ef5020000a10000e...@gwsmtp1.uni-regensburg.de>
> :
>>> Sean S <sstra...@gmail.com> schrieb am 28.07.2010 um 16:34 in
> > Nachricht
> <f711789b-c411-4459-afbe-fe1a50fe2...@w12g2000yqj.googlegroups.
> > com>:
> How did you get those other kernel messages? If you can just get the
> > > iscsid log info that is sent after lines like this
> >
> > I'm able to issue the "dmesg" command after the drive is lost and
> > still retrieve some logging info. Unfortunately, what I sent was all
> > that I can get. If the drive ever successfully reconnects then I can
> > get to /var/log/messages and see the info you are looking for. I've
> > only ever had a successful reconnect when intentionally causing a
> > disconnect (i.e. pulling the ethernet cable and then reconnecting
> > it).
> >
> > I don't know much about unix logging, but maybe there is a way to send
> > more of the logging messages to "dmesg" as that doesn't appear to need
> > disk access to be read.
>
> dmesg just print the kernel message buffer (/proc/kmsg), while syslog can
> capture messages from applications as well.
>
> I have a sample for a syslog-ng configuration file:
Samples for "sources" are missing, sorry:
source s_intern { internal(); };
source s_dev_log { unix-stream("/dev/log"); };
source s_kernel { file("/proc/kmsg"); };
>
> destination d_tty_root { usertty("root"); };
> destination d_console { file("/dev/ttyS0"); };
> destination d_messages { file("/var/log/messages"); };
>
> filter f_error {
> level(alert .. err) and not match('S15.modem: initchat failed.');
> };
> filter f_kernel { level(alert .. err); };
> filter f_auth { facility(auth, authpriv) and level(alert .. info); };
> filter f_debug { level(alert .. debug); };
>
> # send criticals messages to logged root user and /var/log/messages
> log {
> source(s_intern);
> source(s_dev_log);
> source(s_kernel);
> filter(f_error);
> destination(d_tty_root);
> destination(d_messages);
> };
>
> # save auth-related messages
> log {
> source(s_dev_log);
> source(s_kernel);
> filter(f_auth);
> destination(d_messages);
> };
>
> ### Just to get you started. The older syslog is less powerful, but easier
> to configure.
>
> Maybe this is interesting for you:
>
> # 6) To send message to remote syslogd server :
> # destination d_udp { udp("<remote IP address>" port(514)); };
> # Example to send syslogs to syslogd located at 10.0.0.1 :
> # destination d_udp1 { udp("10.0.0.1" port(514)); };
>
> Maybe this helps a bit.
>
> Regards,
> Ulrich
>
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To post to this group, send email to open-is...@googlegroups.com.
To unsubscribe from this group, send email to
open-iscsi+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/open-iscsi?hl=en.
