Stuart,
It looks like you left the "i" or of "fci"; didn't you intend to enter "grep -e fci.device syslog"?
Cheers,
Neal Jones
From: Stuart Kendrick <skendric@fhcrc.org> To: "toasters@teaparty.net" <toasters@teaparty.net> Date: 01/29/2012 10:07 AM Subject: EMS Events in syslog Sent by: toasters-bounces@teaparty.net
Some EMS Events show up in syslog:
cf.fm.takeoverComplete:WARN 10Jan2012 12:58:22
cf.fsm.releasingReservations:INFO 10Jan2012 12:58:24
loghost> grep -e cf.fm.takeoverComplete -e cf.fsm.releasingReservations
syslog
Jan 10 12:58:22 toaster-b-svif1 [toaster-b (takeover):
cf.fm.takeoverComplete:warning]: Cluster monitor: takeover completed
Jan 10 12:58:24 toaster-b-svif1 [toaster-b (takeover):
cf.fsm.releasingReservations:info]: Cluster monitor: Releasing disk
reservations in preparation for giveback
But others do not:
fci.device.timeout:ERR 10Jan2012 12:52:36
fci.device.quiesce:INFO 10Jan2012 13:00:16
loghost> grep -e fc.device syslog
loghost>
syslog.conf:
*.info /etc/messages
*.info @loghost.company.com
In fact, examining my toaster logs for the last two years:
loghost> ls 20*
toaster-logs-from-2010.txt
toaster-logs-from-2011.txt
loghost> grep cf.fm.takeover toaster-logs-from* | wc -l
70
loghost> grep fc.device toaster-logs-from-* | wc -l
0
loghost>
How do I persuade EMS to send /everything/ to syslog?
--sk
Stuart Kendrick
FHCRC
_______________________________________________
Toasters mailing list
Toasters@teaparty.net
http://www.teaparty.net/mailman/listinfo/toasters