<?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 Forward Progress Log events aren't registered in event.log in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/forward-progress-log-events-aren-t-registered-in-event-log/m-p/4566024#M372181</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I've seen that my Forward Progress Log events aren't registered in event.log&lt;BR /&gt;&lt;BR /&gt;There are many events pointing to Single Bit Errors in a DIMM which don't appear in event.log&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;/etc/rc.config.d#/etc/opt/resmon/lbin/monconfig&lt;BR /&gt; &lt;BR /&gt;============================================================================&lt;BR /&gt;===================       Event Monitoring Service       ===================&lt;BR /&gt;===================      Monitoring Request Manager      ===================&lt;BR /&gt;============================================================================&lt;BR /&gt;  EVENT MONITORING IS CURRENTLY ENABLED.&lt;BR /&gt;  EMS Version : A.04.20.31.04&lt;BR /&gt;  STM Version : D.06.00&lt;BR /&gt;============================================================================&lt;BR /&gt;==============      Monitoring Request Manager Main Menu      ==============&lt;BR /&gt;============================================================================&lt;BR /&gt;Note: Monitoring requests let you specify the events for monitors&lt;BR /&gt;      to report and the notification methods to use.&lt;BR /&gt;Select:&lt;BR /&gt;   (S)how monitoring requests configured via monconfig&lt;BR /&gt;   (C)heck detailed monitoring status&lt;BR /&gt;   (L)ist descriptions of available monitors&lt;BR /&gt;   (A)dd a monitoring request&lt;BR /&gt;   (D)elete a monitoring request&lt;BR /&gt;   (M)odify an existing monitoring request&lt;BR /&gt;   (E)nable Monitoring&lt;BR /&gt;   (K)ill (disable) monitoring&lt;BR /&gt;   (H)elp&lt;BR /&gt;   (Q)uit&lt;BR /&gt;   Enter selection: [s]&lt;BR /&gt; &lt;BR /&gt;/etc/rc.config.d#ps -ef | grep stm&lt;BR /&gt;    root  3794     1  0  Oct  9  ?        253:04 /usr/sbin/stm/uut/bin/sys/diagmond&lt;BR /&gt;    root  7730     1  0  Oct  9  ?        24:56 /usr/sbin/stm/uut/bin/tools/monitor/memory_ia64&lt;BR /&gt;    root  6048     1  0  Oct  9  ?        102:11 /usr/sbin/stm/uut/bin/tools/monitor/disk_em&lt;BR /&gt;   sfmdb  3426     1  0  Oct  9  ?         2:24 /opt/psb/db/pgsql/bin/postmaster -i -D /var/opt/psb/db/pgsql&lt;BR /&gt;    root  5180     1  0  Oct  9  ?        13:47 /usr/sbin/stm/uut/bin/tools/monitor/cmc_em&lt;BR /&gt;    root  5895     1  0  Oct  9  ?        24:22 /usr/sbin/stm/uut/bin/tools/monitor/cpe_em&lt;BR /&gt;    root  5243     1 50  Oct  9  ?        204:15 /usr/sbin/stm/uut/bin/tools/monitor/dm_ql_adapter&lt;BR /&gt;    root  7653     1  0  Oct  9  ?        29:22 /usr/sbin/stm/uut/bin/tools/monitor/fpl_em&lt;BR /&gt;    root  8348     1  0  Oct  9  ?         1:30 /usr/sbin/stm/uut/bin/tools/monitor/sysstat_em&lt;BR /&gt;    root  7984     1  0  Oct  9  ?        36:46 /usr/sbin/stm/uut/bin/tools/monitor/ia64_corehw&lt;BR /&gt;    root 25324     1  0  Jan 16  ?         0:00 /usr/sbin/stm/uut/bin/tools/monitor/msamon_sas&lt;BR /&gt;    root 27725     1  0 12:08:12 ?         0:00 /usr/sbin/stm/uut/bin/tools/monitor/dm_raid_adapter&lt;BR /&gt;    root 27026     1  0 12:07:56 ?         0:00 /usr/sbin/stm/uut/bin/tools/monitor/dm_sas_adapter&lt;BR /&gt;    root 25163     1  0  Jan 16  ?         0:00 /usr/sbin/stm/uut/bin/tools/monitor/msamon&lt;BR /&gt;    root   665 11051  0 12:09:01 pts/4     0:00 grep stm&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;/etc/rc.config.d#/opt/resmon/bin/set_fixed -l&lt;BR /&gt;&lt;BR /&gt;/storage/status/disks/default/64000_0xfa00_0x0                         UP  TRUE&lt;BR /&gt;/storage/status/disks/default/64000_0xfa00_0x1                         UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/0_0_4_0_0_0_0                              UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/0_0_4_0_0_0_1                              UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/0_0_5_0_0_0_0                              UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/0_0_5_0_0_0_1                              UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/0_0_13_0_0_0_0                             UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/0_0_13_0_0_0_1                             UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/0_0_14_0_0_0_0                             UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/0_0_14_0_0_0_1                             UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/4_0_4_0_0_0_0                              UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/4_0_4_0_0_0_1                              UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/4_0_5_0_0_0_0                              UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/4_0_5_0_0_0_1                              UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/4_0_13_0_0_0_0                             UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/4_0_13_0_0_0_1                             UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/4_0_14_0_0_0_0                             UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/4_0_14_0_0_0_1                             UP  TRUE&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;The EMS version is the lastest available and also for STM.&lt;BR /&gt;&lt;BR /&gt;Is it a normal situation? I think this events should be registered in event.log&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,</description>
    <pubDate>Mon, 18 Jan 2010 13:03:21 GMT</pubDate>
    <dc:creator>knight_runner</dc:creator>
    <dc:date>2010-01-18T13:03:21Z</dc:date>
    <item>
      <title>Forward Progress Log events aren't registered in event.log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/forward-progress-log-events-aren-t-registered-in-event-log/m-p/4566024#M372181</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I've seen that my Forward Progress Log events aren't registered in event.log&lt;BR /&gt;&lt;BR /&gt;There are many events pointing to Single Bit Errors in a DIMM which don't appear in event.log&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;/etc/rc.config.d#/etc/opt/resmon/lbin/monconfig&lt;BR /&gt; &lt;BR /&gt;============================================================================&lt;BR /&gt;===================       Event Monitoring Service       ===================&lt;BR /&gt;===================      Monitoring Request Manager      ===================&lt;BR /&gt;============================================================================&lt;BR /&gt;  EVENT MONITORING IS CURRENTLY ENABLED.&lt;BR /&gt;  EMS Version : A.04.20.31.04&lt;BR /&gt;  STM Version : D.06.00&lt;BR /&gt;============================================================================&lt;BR /&gt;==============      Monitoring Request Manager Main Menu      ==============&lt;BR /&gt;============================================================================&lt;BR /&gt;Note: Monitoring requests let you specify the events for monitors&lt;BR /&gt;      to report and the notification methods to use.&lt;BR /&gt;Select:&lt;BR /&gt;   (S)how monitoring requests configured via monconfig&lt;BR /&gt;   (C)heck detailed monitoring status&lt;BR /&gt;   (L)ist descriptions of available monitors&lt;BR /&gt;   (A)dd a monitoring request&lt;BR /&gt;   (D)elete a monitoring request&lt;BR /&gt;   (M)odify an existing monitoring request&lt;BR /&gt;   (E)nable Monitoring&lt;BR /&gt;   (K)ill (disable) monitoring&lt;BR /&gt;   (H)elp&lt;BR /&gt;   (Q)uit&lt;BR /&gt;   Enter selection: [s]&lt;BR /&gt; &lt;BR /&gt;/etc/rc.config.d#ps -ef | grep stm&lt;BR /&gt;    root  3794     1  0  Oct  9  ?        253:04 /usr/sbin/stm/uut/bin/sys/diagmond&lt;BR /&gt;    root  7730     1  0  Oct  9  ?        24:56 /usr/sbin/stm/uut/bin/tools/monitor/memory_ia64&lt;BR /&gt;    root  6048     1  0  Oct  9  ?        102:11 /usr/sbin/stm/uut/bin/tools/monitor/disk_em&lt;BR /&gt;   sfmdb  3426     1  0  Oct  9  ?         2:24 /opt/psb/db/pgsql/bin/postmaster -i -D /var/opt/psb/db/pgsql&lt;BR /&gt;    root  5180     1  0  Oct  9  ?        13:47 /usr/sbin/stm/uut/bin/tools/monitor/cmc_em&lt;BR /&gt;    root  5895     1  0  Oct  9  ?        24:22 /usr/sbin/stm/uut/bin/tools/monitor/cpe_em&lt;BR /&gt;    root  5243     1 50  Oct  9  ?        204:15 /usr/sbin/stm/uut/bin/tools/monitor/dm_ql_adapter&lt;BR /&gt;    root  7653     1  0  Oct  9  ?        29:22 /usr/sbin/stm/uut/bin/tools/monitor/fpl_em&lt;BR /&gt;    root  8348     1  0  Oct  9  ?         1:30 /usr/sbin/stm/uut/bin/tools/monitor/sysstat_em&lt;BR /&gt;    root  7984     1  0  Oct  9  ?        36:46 /usr/sbin/stm/uut/bin/tools/monitor/ia64_corehw&lt;BR /&gt;    root 25324     1  0  Jan 16  ?         0:00 /usr/sbin/stm/uut/bin/tools/monitor/msamon_sas&lt;BR /&gt;    root 27725     1  0 12:08:12 ?         0:00 /usr/sbin/stm/uut/bin/tools/monitor/dm_raid_adapter&lt;BR /&gt;    root 27026     1  0 12:07:56 ?         0:00 /usr/sbin/stm/uut/bin/tools/monitor/dm_sas_adapter&lt;BR /&gt;    root 25163     1  0  Jan 16  ?         0:00 /usr/sbin/stm/uut/bin/tools/monitor/msamon&lt;BR /&gt;    root   665 11051  0 12:09:01 pts/4     0:00 grep stm&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;/etc/rc.config.d#/opt/resmon/bin/set_fixed -l&lt;BR /&gt;&lt;BR /&gt;/storage/status/disks/default/64000_0xfa00_0x0                         UP  TRUE&lt;BR /&gt;/storage/status/disks/default/64000_0xfa00_0x1                         UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/0_0_4_0_0_0_0                              UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/0_0_4_0_0_0_1                              UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/0_0_5_0_0_0_0                              UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/0_0_5_0_0_0_1                              UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/0_0_13_0_0_0_0                             UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/0_0_13_0_0_0_1                             UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/0_0_14_0_0_0_0                             UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/0_0_14_0_0_0_1                             UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/4_0_4_0_0_0_0                              UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/4_0_4_0_0_0_1                              UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/4_0_5_0_0_0_0                              UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/4_0_5_0_0_0_1                              UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/4_0_13_0_0_0_0                             UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/4_0_13_0_0_0_1                             UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/4_0_14_0_0_0_0                             UP  TRUE&lt;BR /&gt;/adapters/status/ql_adapter/4_0_14_0_0_0_1                             UP  TRUE&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;The EMS version is the lastest available and also for STM.&lt;BR /&gt;&lt;BR /&gt;Is it a normal situation? I think this events should be registered in event.log&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,</description>
      <pubDate>Mon, 18 Jan 2010 13:03:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/forward-progress-log-events-aren-t-registered-in-event-log/m-p/4566024#M372181</guid>
      <dc:creator>knight_runner</dc:creator>
      <dc:date>2010-01-18T13:03:21Z</dc:date>
    </item>
  </channel>
</rss>

