<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: SCSI disk error should send an e-mail to root in Operating System - Tru64 Unix</title>
    <link>https://community.hpe.com/t5/operating-system-tru64-unix/scsi-disk-error-should-send-an-e-mail-to-root/m-p/4500604#M19306</link>
    <description>Sorry, there is still an open question.&lt;BR /&gt;&lt;BR /&gt;How could I change the EVM configuration and set the default priority of event sys.unix.binlog.hw.scsi to 600 instead of 400 (default value)?&lt;BR /&gt;&lt;BR /&gt;    I want to receive an e-mail to the root account anytime a SCSI disk error happens.&lt;BR /&gt;&lt;BR /&gt;Note that SCSI I/O errors are currently logged with priority 400. The standard /etc/evmlogger.conf only sends an error mail to root if the priority is at least 600.&lt;BR /&gt;&lt;BR /&gt;Thanks to look into this?&lt;BR /&gt;&lt;BR /&gt;I have been reading the Tru64 UNIX Troubleshooting book by Martin Moore &amp;amp; Steven Hancock, but I do not find a solution (ISBN 1-55558-274-5 from Digital Press).</description>
    <pubDate>Tue, 29 Sep 2009 05:27:21 GMT</pubDate>
    <dc:creator>Geert Van Pamel</dc:creator>
    <dc:date>2009-09-29T05:27:21Z</dc:date>
    <item>
      <title>SCSI disk error should send an e-mail to root</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/scsi-disk-error-should-send-an-e-mail-to-root/m-p/4500603#M19305</link>
      <description>My system generated a nonrecoverable SCSI read error last night.&lt;BR /&gt;&lt;BR /&gt;I would have expected that root should have received an error mail from the event logging subsystem?&lt;BR /&gt;&lt;BR /&gt;The SCSI read error has been only logged with priority 400. The standard /etc/evmlogger.conf only sends an error mail to root if the priority is at least 600.&lt;BR /&gt;&lt;BR /&gt;I would have expected that a non recoverable SCSI read error would have been logged with at least priority 600.&lt;BR /&gt;&lt;BR /&gt;Is there any possibility to change the priority of event sys.unix.binlog.hw.scsi?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;evmget -f "[ since 2009:09:20:03:00:00 ] &amp;amp; [ before 2009:09:20:04:00:00 ]" |evmsort |evmshow -d |pg&lt;BR /&gt;&lt;BR /&gt;======================= Binary Error Log event =======================&lt;BR /&gt;EVM event name: sys.unix.binlog.hw.scsi&lt;BR /&gt;&lt;BR /&gt;    Binary error log events are posted through the binlogd daemon, and&lt;BR /&gt;    stored in the binary error log file, /var/adm/binary.errlog.  This&lt;BR /&gt;    event is used to report all SCSI device errors, including disk,&lt;BR /&gt;    tape, HSZ raid events and adapter errors.&lt;BR /&gt;&lt;BR /&gt;    Action: Use Compaq Analyze or DECevent to read and analyze the&lt;BR /&gt;    system error log to determine if a SCSI device may need to be&lt;BR /&gt;    replaced.&lt;BR /&gt;&lt;BR /&gt;Formatted Message:&lt;BR /&gt;    SCSI event&lt;BR /&gt;&lt;BR /&gt;Event Data Items:&lt;BR /&gt;    Event Name        : sys.unix.binlog.hw.scsi&lt;BR /&gt;    Priority          : 400&lt;BR /&gt;    Timestamp         : 20-Sep-2009 03:42:55&lt;BR /&gt;    Host Name         : hbsitcca&lt;BR /&gt;    Format            : SCSI event&lt;BR /&gt;    Reference         : cat:evmexp.cat:300&lt;BR /&gt;&lt;BR /&gt;Variable Items:&lt;BR /&gt;    subid_class (INT32) = 199&lt;BR /&gt;    subid_num (INT32) = 0&lt;BR /&gt;    subid_unit_num (INT32) = 24&lt;BR /&gt;    subid_type (INT32) = 0&lt;BR /&gt;    binlog_event (OPAQUE) = [OPAQUE VALUE: 1144 bytes]&lt;BR /&gt;&lt;BR /&gt;============================ Translation =============================&lt;BR /&gt;Sequence number of error: -499735687&lt;BR /&gt;Time of error entry: 20-Sep-2009 03:42:55&lt;BR /&gt;Host name: hbsitcca&lt;BR /&gt;&lt;BR /&gt;SCSI CAM ERROR PACKET&lt;BR /&gt;SCSI device class: DISK&lt;BR /&gt;Bus Number: 0&lt;BR /&gt;Target number: 3 &lt;BR /&gt;Lun Number: 0&lt;BR /&gt;&lt;BR /&gt;Name of routine that logged the event: cdisk_check_sense&lt;BR /&gt;Event information:  Medium Error at block number: 44165980&lt;BR /&gt;Hardware detected event: Hard Error Detected&lt;BR /&gt;Event information: Hardware ID = 74&lt;BR /&gt;Device Name: COMPAQ  BD036659CC      3B00&lt;BR /&gt;Event information: Active CCB at time of error&lt;BR /&gt;Event information: CCB request completed with an error&lt;BR /&gt;&lt;BR /&gt;                ############### Entry End ###############&lt;BR /&gt;&lt;BR /&gt;Event information: Error, exception, or abnormal condition&lt;BR /&gt;Event information: MEDIUM ERROR - Nonrecoverable medium error&lt;BR /&gt;&lt;BR /&gt;                ############### Entry End ###############&lt;BR /&gt;</description>
      <pubDate>Sun, 20 Sep 2009 19:47:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/scsi-disk-error-should-send-an-e-mail-to-root/m-p/4500603#M19305</guid>
      <dc:creator>Geert Van Pamel</dc:creator>
      <dc:date>2009-09-20T19:47:06Z</dc:date>
    </item>
    <item>
      <title>Re: SCSI disk error should send an e-mail to root</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/scsi-disk-error-should-send-an-e-mail-to-root/m-p/4500604#M19306</link>
      <description>Sorry, there is still an open question.&lt;BR /&gt;&lt;BR /&gt;How could I change the EVM configuration and set the default priority of event sys.unix.binlog.hw.scsi to 600 instead of 400 (default value)?&lt;BR /&gt;&lt;BR /&gt;    I want to receive an e-mail to the root account anytime a SCSI disk error happens.&lt;BR /&gt;&lt;BR /&gt;Note that SCSI I/O errors are currently logged with priority 400. The standard /etc/evmlogger.conf only sends an error mail to root if the priority is at least 600.&lt;BR /&gt;&lt;BR /&gt;Thanks to look into this?&lt;BR /&gt;&lt;BR /&gt;I have been reading the Tru64 UNIX Troubleshooting book by Martin Moore &amp;amp; Steven Hancock, but I do not find a solution (ISBN 1-55558-274-5 from Digital Press).</description>
      <pubDate>Tue, 29 Sep 2009 05:27:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/scsi-disk-error-should-send-an-e-mail-to-root/m-p/4500604#M19306</guid>
      <dc:creator>Geert Van Pamel</dc:creator>
      <dc:date>2009-09-29T05:27:21Z</dc:date>
    </item>
    <item>
      <title>Re: SCSI disk error should send an e-mail to root</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/scsi-disk-error-should-send-an-e-mail-to-root/m-p/4500605#M19307</link>
      <description>I know nothing about evm, but I happened to run across this looking for another issue. So I may be way off base here, so apologies in advance if this is not what you're looking for.&lt;BR /&gt;&lt;BR /&gt;Why not change the filter to mail events with a lower priority in evmlogger.conf?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;    filter    "[prio &amp;gt;= 600] &amp;amp; ![name @SYS_VP@.syslog.mail]"&lt;BR /&gt;&lt;BR /&gt;or maybe write a secondary evmlogger.conf file with specific filtering?&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.tru64unix.compaq.com/docs/best_practices/EVM_BP/TITLE.HTM" target="_blank"&gt;http://www.tru64unix.compaq.com/docs/best_practices/EVM_BP/TITLE.HTM&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;from the evmlogger.conf man page:&lt;BR /&gt;&lt;BR /&gt;This example initiates an instance of the evmlogger command with the fol-&lt;BR /&gt;  lowing configuration:&lt;BR /&gt;&lt;BR /&gt;   1.  Binary events are written to a file in the /var/evm/evmlog directory&lt;BR /&gt;       named evmlog.xxx where xxx is the current year, month, and day -- for&lt;BR /&gt;       example, /var/evm/evmlog/evmlog.19981217. An alternate log path is&lt;BR /&gt;       specified in case of write failures to the primary path.&lt;BR /&gt;&lt;BR /&gt;   2.  A new generation of the log is started automatically if the size&lt;BR /&gt;       exceeds 256 Kbytes.&lt;BR /&gt;&lt;BR /&gt;   3.  All events with a priority of at least 200 are selected for logging.&lt;BR /&gt;&lt;BR /&gt;   4.  Duplicate events are suppressed.&lt;BR /&gt;&lt;BR /&gt;   5.  Events with a priority of at least 600 are displayed on the system&lt;BR /&gt;       console as formatted events, showing the timestamp, the priority and&lt;BR /&gt;       the event's message.&lt;BR /&gt;&lt;BR /&gt;   6.  Events with a priority of at least 600 are also mailed to root.&lt;BR /&gt;&lt;BR /&gt;   7.  A maximum of 20 events will be queued for forwarding to root when an&lt;BR /&gt;       instance of the forwarding command is already running.&lt;BR /&gt;&lt;BR /&gt;       eventlog&lt;BR /&gt;       {&lt;BR /&gt;           name        evmlog&lt;BR /&gt;           logfile     /var/evm/evmlog/evmlog.dated&lt;BR /&gt;           type        binary&lt;BR /&gt;           maxsize     256  # Kbytes&lt;BR /&gt;&lt;BR /&gt;           alternate  /altlogs/evmlog/evmlog.dated&lt;BR /&gt;&lt;BR /&gt;           # Log all events with priority &amp;gt;= 200:&lt;BR /&gt;           filter      "[prio &amp;gt;= 200]"&lt;BR /&gt;&lt;BR /&gt;           # Suppress logging of duplicate events:&lt;BR /&gt;           suppress&lt;BR /&gt;           {   filter      "[name *]"&lt;BR /&gt;               period      30  # minutes&lt;BR /&gt;               threshold   3   # No. of instances before suppression&lt;BR /&gt;           }&lt;BR /&gt;&lt;BR /&gt;       }&lt;BR /&gt;&lt;BR /&gt;       # Log high-priority events to the system console:&lt;BR /&gt;       eventlog {&lt;BR /&gt;           name                console_log&lt;BR /&gt;           logfile             /dev/console&lt;BR /&gt;           filter              "[prio &amp;gt;= 600]"&lt;BR /&gt;           type                formatted&lt;BR /&gt;           show_template       "@timestamp [@priority] @@"&lt;BR /&gt;       }&lt;BR /&gt;&lt;BR /&gt;       # Forward details of high-priority events to root:&lt;BR /&gt;       forward {&lt;BR /&gt;           name      priority_alert&lt;BR /&gt;           # Don't forward mail events through mail (see note above):&lt;BR /&gt;           filter    "[prio &amp;gt;= 600] &amp;amp; ![name @SYS_VP@.syslog.mail]"&lt;BR /&gt;&lt;BR /&gt;           suppress&lt;BR /&gt;           {   filter      "[name *]"&lt;BR /&gt;               period      120  # minutes&lt;BR /&gt;               threshold   1    # No. of duplicates before suppression&lt;BR /&gt;           }&lt;BR /&gt;&lt;BR /&gt;           # This evmshow command writes a subject line as the first line of&lt;BR /&gt;           # output, followed by a detailed display of the contents of the&lt;BR /&gt;           # event.  The resulting message is distributed by mail(1).&lt;BR /&gt;&lt;BR /&gt;           command   "evmshow -d -t 'Subject: EVM ALERT [@priority]: @@' \&lt;BR /&gt;                                | mail root"&lt;BR /&gt;       }&lt;BR /&gt;&lt;BR /&gt;FILES&lt;BR /&gt;&lt;BR /&gt;  /etc/evmlogger.conf&lt;BR /&gt;      Location of the EVM logger configuration file.&lt;BR /&gt;&lt;BR /&gt;  /var/evm/adm/config/logger&lt;BR /&gt;      Default location of the secondary EVM logger configuration files.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;&lt;BR /&gt;Rgds,&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 29 Sep 2009 21:27:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/scsi-disk-error-should-send-an-e-mail-to-root/m-p/4500605#M19307</guid>
      <dc:creator>cnb</dc:creator>
      <dc:date>2009-09-29T21:27:02Z</dc:date>
    </item>
    <item>
      <title>Re: SCSI disk error should send an e-mail to root</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/scsi-disk-error-should-send-an-e-mail-to-root/m-p/4500606#M19308</link>
      <description>I found another example file:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.tru64unix.compaq.com/docs/best_practices/BP_EVM_CELL/TITLE.HTM" target="_blank"&gt;http://www.tru64unix.compaq.com/docs/best_practices/BP_EVM_CELL/TITLE.HTM&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Rgds,&lt;BR /&gt;</description>
      <pubDate>Tue, 29 Sep 2009 21:52:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/scsi-disk-error-should-send-an-e-mail-to-root/m-p/4500606#M19308</guid>
      <dc:creator>cnb</dc:creator>
      <dc:date>2009-09-29T21:52:13Z</dc:date>
    </item>
    <item>
      <title>Re: SCSI disk error should send an e-mail to root</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/scsi-disk-error-should-send-an-e-mail-to-root/m-p/4500607#M19309</link>
      <description>I did not change the standard /etc/evmlogger.conf file.&lt;BR /&gt;&lt;BR /&gt;Rather I added another "local" independent conf file.&lt;BR /&gt;&lt;BR /&gt;cd /var/evm/adm/config/logger&lt;BR /&gt;&lt;BR /&gt;vi sysman.conf&lt;BR /&gt;&lt;BR /&gt;# Forward details of high-priority events to root:&lt;BR /&gt;forward {&lt;BR /&gt;    name      sysman_forward&lt;BR /&gt;&lt;BR /&gt;    # Don't forward mail events through mail (see note above).&lt;BR /&gt;    filter    "[prio &amp;gt;= 400] &amp;amp; ![name @SYS_VP@.syslog.mail]"&lt;BR /&gt;&lt;BR /&gt;    suppress&lt;BR /&gt;    {   filter      "[name *]"&lt;BR /&gt;        period      120  # minutes&lt;BR /&gt;        threshold   1    # No. of duplicates before suppression&lt;BR /&gt;    }&lt;BR /&gt;&lt;BR /&gt;    # This evmshow command writes a subject line as the first line of&lt;BR /&gt;    # output, followed by a detailed display of the contents of the event.&lt;BR /&gt;    # The resulting message is distributed by mail(1).&lt;BR /&gt;    command   "evmshow -d -t 'Subject: @host_name [@priority] @timestamp @@' | mail sysman"&lt;BR /&gt;&lt;BR /&gt;    # Limit the number of events that can be queued for this command:&lt;BR /&gt;    maxqueue        100&lt;BR /&gt;}&lt;BR /&gt;&lt;BR /&gt;evmreload -l&lt;BR /&gt;&lt;BR /&gt;evmpost -p 400 -a "test message to mobile"&lt;BR /&gt;&lt;BR /&gt;It forwards an alarm message via e-mail to an alias sysman. In my case, this sends an SMS message to my mobile.&lt;BR /&gt;&lt;BR /&gt;The command "mail sysman" could be replaced by any command forwarding an alert message using any possible network protocol.&lt;BR /&gt;&lt;BR /&gt;TCP is a wonderful swiss knife tool! Still alive and kicking after 35 years!&lt;BR /&gt;&lt;BR /&gt;Thanks to all of you!</description>
      <pubDate>Wed, 30 Sep 2009 20:14:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/scsi-disk-error-should-send-an-e-mail-to-root/m-p/4500607#M19309</guid>
      <dc:creator>Geert Van Pamel</dc:creator>
      <dc:date>2009-09-30T20:14:06Z</dc:date>
    </item>
  </channel>
</rss>

