HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Forward Progress Log events aren't registered in e...
Operating System - HP-UX
1833734
Members
2741
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-18-2010 05:03 AM
01-18-2010 05:03 AM
Forward Progress Log events aren't registered in event.log
Hi,
I've seen that my Forward Progress Log events aren't registered in event.log
There are many events pointing to Single Bit Errors in a DIMM which don't appear in event.log
/etc/rc.config.d#/etc/opt/resmon/lbin/monconfig
============================================================================
=================== Event Monitoring Service ===================
=================== Monitoring Request Manager ===================
============================================================================
EVENT MONITORING IS CURRENTLY ENABLED.
EMS Version : A.04.20.31.04
STM Version : D.06.00
============================================================================
============== Monitoring Request Manager Main Menu ==============
============================================================================
Note: Monitoring requests let you specify the events for monitors
to report and the notification methods to use.
Select:
(S)how monitoring requests configured via monconfig
(C)heck detailed monitoring status
(L)ist descriptions of available monitors
(A)dd a monitoring request
(D)elete a monitoring request
(M)odify an existing monitoring request
(E)nable Monitoring
(K)ill (disable) monitoring
(H)elp
(Q)uit
Enter selection: [s]
/etc/rc.config.d#ps -ef | grep stm
root 3794 1 0 Oct 9 ? 253:04 /usr/sbin/stm/uut/bin/sys/diagmond
root 7730 1 0 Oct 9 ? 24:56 /usr/sbin/stm/uut/bin/tools/monitor/memory_ia64
root 6048 1 0 Oct 9 ? 102:11 /usr/sbin/stm/uut/bin/tools/monitor/disk_em
sfmdb 3426 1 0 Oct 9 ? 2:24 /opt/psb/db/pgsql/bin/postmaster -i -D /var/opt/psb/db/pgsql
root 5180 1 0 Oct 9 ? 13:47 /usr/sbin/stm/uut/bin/tools/monitor/cmc_em
root 5895 1 0 Oct 9 ? 24:22 /usr/sbin/stm/uut/bin/tools/monitor/cpe_em
root 5243 1 50 Oct 9 ? 204:15 /usr/sbin/stm/uut/bin/tools/monitor/dm_ql_adapter
root 7653 1 0 Oct 9 ? 29:22 /usr/sbin/stm/uut/bin/tools/monitor/fpl_em
root 8348 1 0 Oct 9 ? 1:30 /usr/sbin/stm/uut/bin/tools/monitor/sysstat_em
root 7984 1 0 Oct 9 ? 36:46 /usr/sbin/stm/uut/bin/tools/monitor/ia64_corehw
root 25324 1 0 Jan 16 ? 0:00 /usr/sbin/stm/uut/bin/tools/monitor/msamon_sas
root 27725 1 0 12:08:12 ? 0:00 /usr/sbin/stm/uut/bin/tools/monitor/dm_raid_adapter
root 27026 1 0 12:07:56 ? 0:00 /usr/sbin/stm/uut/bin/tools/monitor/dm_sas_adapter
root 25163 1 0 Jan 16 ? 0:00 /usr/sbin/stm/uut/bin/tools/monitor/msamon
root 665 11051 0 12:09:01 pts/4 0:00 grep stm
/etc/rc.config.d#/opt/resmon/bin/set_fixed -l
/storage/status/disks/default/64000_0xfa00_0x0 UP TRUE
/storage/status/disks/default/64000_0xfa00_0x1 UP TRUE
/adapters/status/ql_adapter/0_0_4_0_0_0_0 UP TRUE
/adapters/status/ql_adapter/0_0_4_0_0_0_1 UP TRUE
/adapters/status/ql_adapter/0_0_5_0_0_0_0 UP TRUE
/adapters/status/ql_adapter/0_0_5_0_0_0_1 UP TRUE
/adapters/status/ql_adapter/0_0_13_0_0_0_0 UP TRUE
/adapters/status/ql_adapter/0_0_13_0_0_0_1 UP TRUE
/adapters/status/ql_adapter/0_0_14_0_0_0_0 UP TRUE
/adapters/status/ql_adapter/0_0_14_0_0_0_1 UP TRUE
/adapters/status/ql_adapter/4_0_4_0_0_0_0 UP TRUE
/adapters/status/ql_adapter/4_0_4_0_0_0_1 UP TRUE
/adapters/status/ql_adapter/4_0_5_0_0_0_0 UP TRUE
/adapters/status/ql_adapter/4_0_5_0_0_0_1 UP TRUE
/adapters/status/ql_adapter/4_0_13_0_0_0_0 UP TRUE
/adapters/status/ql_adapter/4_0_13_0_0_0_1 UP TRUE
/adapters/status/ql_adapter/4_0_14_0_0_0_0 UP TRUE
/adapters/status/ql_adapter/4_0_14_0_0_0_1 UP TRUE
The EMS version is the lastest available and also for STM.
Is it a normal situation? I think this events should be registered in event.log
Regards,
I've seen that my Forward Progress Log events aren't registered in event.log
There are many events pointing to Single Bit Errors in a DIMM which don't appear in event.log
/etc/rc.config.d#/etc/opt/resmon/lbin/monconfig
============================================================================
=================== Event Monitoring Service ===================
=================== Monitoring Request Manager ===================
============================================================================
EVENT MONITORING IS CURRENTLY ENABLED.
EMS Version : A.04.20.31.04
STM Version : D.06.00
============================================================================
============== Monitoring Request Manager Main Menu ==============
============================================================================
Note: Monitoring requests let you specify the events for monitors
to report and the notification methods to use.
Select:
(S)how monitoring requests configured via monconfig
(C)heck detailed monitoring status
(L)ist descriptions of available monitors
(A)dd a monitoring request
(D)elete a monitoring request
(M)odify an existing monitoring request
(E)nable Monitoring
(K)ill (disable) monitoring
(H)elp
(Q)uit
Enter selection: [s]
/etc/rc.config.d#ps -ef | grep stm
root 3794 1 0 Oct 9 ? 253:04 /usr/sbin/stm/uut/bin/sys/diagmond
root 7730 1 0 Oct 9 ? 24:56 /usr/sbin/stm/uut/bin/tools/monitor/memory_ia64
root 6048 1 0 Oct 9 ? 102:11 /usr/sbin/stm/uut/bin/tools/monitor/disk_em
sfmdb 3426 1 0 Oct 9 ? 2:24 /opt/psb/db/pgsql/bin/postmaster -i -D /var/opt/psb/db/pgsql
root 5180 1 0 Oct 9 ? 13:47 /usr/sbin/stm/uut/bin/tools/monitor/cmc_em
root 5895 1 0 Oct 9 ? 24:22 /usr/sbin/stm/uut/bin/tools/monitor/cpe_em
root 5243 1 50 Oct 9 ? 204:15 /usr/sbin/stm/uut/bin/tools/monitor/dm_ql_adapter
root 7653 1 0 Oct 9 ? 29:22 /usr/sbin/stm/uut/bin/tools/monitor/fpl_em
root 8348 1 0 Oct 9 ? 1:30 /usr/sbin/stm/uut/bin/tools/monitor/sysstat_em
root 7984 1 0 Oct 9 ? 36:46 /usr/sbin/stm/uut/bin/tools/monitor/ia64_corehw
root 25324 1 0 Jan 16 ? 0:00 /usr/sbin/stm/uut/bin/tools/monitor/msamon_sas
root 27725 1 0 12:08:12 ? 0:00 /usr/sbin/stm/uut/bin/tools/monitor/dm_raid_adapter
root 27026 1 0 12:07:56 ? 0:00 /usr/sbin/stm/uut/bin/tools/monitor/dm_sas_adapter
root 25163 1 0 Jan 16 ? 0:00 /usr/sbin/stm/uut/bin/tools/monitor/msamon
root 665 11051 0 12:09:01 pts/4 0:00 grep stm
/etc/rc.config.d#/opt/resmon/bin/set_fixed -l
/storage/status/disks/default/64000_0xfa00_0x0 UP TRUE
/storage/status/disks/default/64000_0xfa00_0x1 UP TRUE
/adapters/status/ql_adapter/0_0_4_0_0_0_0 UP TRUE
/adapters/status/ql_adapter/0_0_4_0_0_0_1 UP TRUE
/adapters/status/ql_adapter/0_0_5_0_0_0_0 UP TRUE
/adapters/status/ql_adapter/0_0_5_0_0_0_1 UP TRUE
/adapters/status/ql_adapter/0_0_13_0_0_0_0 UP TRUE
/adapters/status/ql_adapter/0_0_13_0_0_0_1 UP TRUE
/adapters/status/ql_adapter/0_0_14_0_0_0_0 UP TRUE
/adapters/status/ql_adapter/0_0_14_0_0_0_1 UP TRUE
/adapters/status/ql_adapter/4_0_4_0_0_0_0 UP TRUE
/adapters/status/ql_adapter/4_0_4_0_0_0_1 UP TRUE
/adapters/status/ql_adapter/4_0_5_0_0_0_0 UP TRUE
/adapters/status/ql_adapter/4_0_5_0_0_0_1 UP TRUE
/adapters/status/ql_adapter/4_0_13_0_0_0_0 UP TRUE
/adapters/status/ql_adapter/4_0_13_0_0_0_1 UP TRUE
/adapters/status/ql_adapter/4_0_14_0_0_0_0 UP TRUE
/adapters/status/ql_adapter/4_0_14_0_0_0_1 UP TRUE
The EMS version is the lastest available and also for STM.
Is it a normal situation? I think this events should be registered in event.log
Regards,
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP