Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Netapp: toasters

EMS Events in syslog

 

 

Netapp toasters RSS feed   Index | Next | Previous | View Threaded


skendric at fhcrc

Jan 29, 2012, 6:58 AM

Post #1 of 3 (484 views)
Permalink
EMS Events in syslog

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 [at] teaparty
http://www.teaparty.net/mailman/listinfo/toasters


ncjones at us

Jan 29, 2012, 8:12 AM

Post #2 of 3 (451 views)
Permalink
Re: EMS Events in syslog [In reply to]

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 [at] fhcrc>
To:
"toasters [at] teaparty" <toasters [at] teaparty>
Date:
01/29/2012 10:07 AM
Subject:
EMS Events in syslog
Sent by:
toasters-bounces [at] teaparty



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 [at] teaparty
http://www.teaparty.net/mailman/listinfo/toasters


skendric at fhcrc

Jan 29, 2012, 8:51 AM

Post #3 of 3 (462 views)
Permalink
Re: EMS Events in syslog [In reply to]

Hi Neal,

Yep, that was a fumble. Still, my point remains, even after I
straighten out my typos:

0
0

Yet, in xxxx.ems.gz:

<LR d="10Jan2012 12:50:21" n="toaster-a" pn="toaster-b" t="1326228621"
id="1316410940/599716" p="3" s="C=1U" o="isp2400_asyncd_0" vf="" replay="1">
<scsi_cmd_abortedByHost_1
deviceType="Disk"
deviceName="0c.0L187"
ha_status="0x12"
cdb="0x2a:6fe6d95c:0124"/>
</LR>

<LR d="10Jan2012 12:58:55" n="toaster-b" pn="toaster-a" t="1326229135"
id="1316405680/420420" p="6" s="C=1T" o="isp2400_timeout_2" vf="">
<fci_device_quiesce_1
adapterName="0a"
deviceType="Disk"
deviceName="0a.0 (0x03000000)"
lun="178"
cdb="0x5f:0601"
retryCount="0"/>
</LR>

Or, if you prefer, the summarized version from the asup message itself:

scsi.cmd.abortedByHost:ERR 10Jan2012 12:52:36
37 0 0 0 0
fci.device.quiesce:INFO 10Jan2012 13:00:16
149 0 0 0 0

Many, I might venture to say 'most', of the EMS messages do, in fact,
show up in syslog ... but not all.

?

--sk

On 1/29/2012 8:12 AM, Neal Jones wrote:
>
> 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 [at] fhcrc>
> To: "toasters [at] teaparty" <toasters [at] teaparty>
> Date: 01/29/2012 10:07 AM
> Subject: EMS Events in syslog
> Sent by: toasters-bounces [at] teaparty
>
>
> ------------------------------------------------------------------------
>
>
>
> 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 [at] teaparty
> http://www.teaparty.net/mailman/listinfo/toasters
>
>
>

Netapp toasters RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.