HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Syslog messages
Operating System - HP-UX
1830900
Members
3027
Online
110017
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
05-05-2008 12:47 PM
05-05-2008 12:47 PM
Syslog messages
I am getting the following error messages in syslog for some time, does any one has a clue about them?
May 5 14:34:28 HERA vmunix: DIAGNOSTIC SYSTEM WARNING:
May 5 14:34:28 HERA vmunix: The diagnostic logging facility is no longer rec
eiving excessive
May 5 14:34:28 HERA vmunix: errors from the I/O subsystem. 1 I/O error entr
ies were lost.
May 5 14:34:28 HERA vmunix: DIAGNOSTIC SYSTEM WARNING:
May 5 14:34:28 HERA vmunix: The diagnostic logging facility has started rece
iving excessive
May 5 14:34:28 HERA vmunix: errors from the I/O subsystem. I/O error entrie
s will be lost
May 5 14:34:28 HERA vmunix: until the cause of the excessive I/O logging is
corrected.
May 5 14:34:28 HERA vmunix: If the DEMLOG daemon is not active, use the DIAG
SYSTEM command
May 5 14:34:28 HERA vmunix: in SYSDIAG to start it.
May 5 14:34:28 HERA vmunix: If the DEMLOG daemon is active, use the LOGTOOL
utility in SYSDIAG
May 5 14:34:28 HERA vmunix: to determine which I/O subsystem is logging exce
ssive errors.
Can any one give me the clue, whats the real problem is and how to fix it?
May 5 14:34:28 HERA vmunix: DIAGNOSTIC SYSTEM WARNING:
May 5 14:34:28 HERA vmunix: The diagnostic logging facility is no longer rec
eiving excessive
May 5 14:34:28 HERA vmunix: errors from the I/O subsystem. 1 I/O error entr
ies were lost.
May 5 14:34:28 HERA vmunix: DIAGNOSTIC SYSTEM WARNING:
May 5 14:34:28 HERA vmunix: The diagnostic logging facility has started rece
iving excessive
May 5 14:34:28 HERA vmunix: errors from the I/O subsystem. I/O error entrie
s will be lost
May 5 14:34:28 HERA vmunix: until the cause of the excessive I/O logging is
corrected.
May 5 14:34:28 HERA vmunix: If the DEMLOG daemon is not active, use the DIAG
SYSTEM command
May 5 14:34:28 HERA vmunix: in SYSDIAG to start it.
May 5 14:34:28 HERA vmunix: If the DEMLOG daemon is active, use the LOGTOOL
utility in SYSDIAG
May 5 14:34:28 HERA vmunix: to determine which I/O subsystem is logging exce
ssive errors.
Can any one give me the clue, whats the real problem is and how to fix it?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-05-2008 05:41 PM
05-05-2008 05:41 PM
Re: Syslog messages
Hi
Seems that there is something wrong with system H/W. If the system is configured with EMS, you could check the EMC alerts.
Or use stm to verify which H/W creates those i/o error.
Best Regards,
Ramesh
Seems that there is something wrong with system H/W. If the system is configured with EMS, you could check the EMC alerts.
Or use stm to verify which H/W creates those i/o error.
Best Regards,
Ramesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-05-2008 06:20 PM
05-05-2008 06:20 PM
Re: Syslog messages
Ali,
It seems your have hardware warning.
How to use LOGTOOL (an example)
---------------------------------
How to decode Hardware errors logged on a 9000/S800 HPUX system.
Supported HP-UX revs = HPUX 8.0, 8.02, 8.06, 9.0, 9.02, 9.04.
o Log onto system as root
o Type "sysdiag"
# sysdiag
o At the DUI prompt type "logtool"
DUI> logtool
o At the LOGTOOL prompt type "status detail"
LOGTOOL> status detail
This will list the number of error logs on the system. Including
time stamp of the 1st log entry and # of records in each log. For
example:
Log File Rec #1 Rec #1 Total
Name Date Time #Records
========== ============ ======== ========
LOG0000 01/31/94 12:08 PM 18
LOG0004 02/24/94 07:04 AM 1024
LOG0005 02/24/94 07:05 AM 1024
LOG0006* 02/24/94 07:06 AM 352
o From the time stamp, determine the log in which log you are
interested.
o Display the contents of the log and redirect the output to a
UNIX file using the following command:
LOGTOOL> list log=xxxx;outfile=
where xxxx is the integer of the log file name and is
a standard HPUX file name. You can drop the leading zeroes from
the integer number. The outfile file should be limited to 8
alpha/numeric characters only.
An example of displaying the contents of LOG0004 is as follows:
LOGTOOL> list log=4;outfile=Log4
In the above example, the contents of LOG0004 will be
redirected to a file called "Log4". It will be automatically
placed under the /usr/diag/bin directory.
o Now, to view this log, exit out of LOGTOOL and DUI and cd to
the /usr/diag/bin directory. Then use MORE or VI to view the file.
A sample of the system error log report follows:
SYSTEM ERROR LOG REPORT
=======================
===============================================================
WED, FEB 03, 1993 11:30 PM /usr/adm/diag/LOG0000
SYSTEM
(PIN 0
I/O ERROR
PRODUCT NAME: PDEV: 52.0.0
LDEV: DEVICE CLASS: 15
I/O EVENT CLASS: Hardware LLIO STATUS: $E31F0414
RETRY SCHEME: Log Each Retry WILL RETRY: NO
I/O RESULT: I/O Failed RUN AUTODIAG: NO
RETRY COUNT: 0 MGR PORT NUM.: $7
TRANS. NUM.: $2B70B812 # HDWR BYTES: 22
HARDWARE STATUS:
1 2 3 4 5 6 7 8 9 10 11 12
== == == == == == == == == == == ==
1: 00 00 00 02 70 00 02 00 00 00 00 0B
13: 00 00 00 00 3A 00 00 00 00 00
You may see that LOGTOOL has further decoded the HARDWARE STATUS
WK
It seems your have hardware warning.
How to use LOGTOOL (an example)
---------------------------------
How to decode Hardware errors logged on a 9000/S800 HPUX system.
Supported HP-UX revs = HPUX 8.0, 8.02, 8.06, 9.0, 9.02, 9.04.
o Log onto system as root
o Type "sysdiag"
# sysdiag
o At the DUI prompt type "logtool"
DUI> logtool
o At the LOGTOOL prompt type "status detail"
LOGTOOL> status detail
This will list the number of error logs on the system. Including
time stamp of the 1st log entry and # of records in each log. For
example:
Log File Rec #1 Rec #1 Total
Name Date Time #Records
========== ============ ======== ========
LOG0000 01/31/94 12:08 PM 18
LOG0004 02/24/94 07:04 AM 1024
LOG0005 02/24/94 07:05 AM 1024
LOG0006* 02/24/94 07:06 AM 352
o From the time stamp, determine the log in which log you are
interested.
o Display the contents of the log and redirect the output to a
UNIX file using the following command:
LOGTOOL> list log=xxxx;outfile=
where xxxx is the integer of the log file name and
a standard HPUX file name. You can drop the leading zeroes from
the integer number. The outfile file should be limited to 8
alpha/numeric characters only.
An example of displaying the contents of LOG0004 is as follows:
LOGTOOL> list log=4;outfile=Log4
In the above example, the contents of LOG0004 will be
redirected to a file called "Log4". It will be automatically
placed under the /usr/diag/bin directory.
o Now, to view this log, exit out of LOGTOOL and DUI and cd to
the /usr/diag/bin directory. Then use MORE or VI to view the file.
A sample of the system error log report follows:
SYSTEM ERROR LOG REPORT
=======================
===============================================================
WED, FEB 03, 1993 11:30 PM /usr/adm/diag/LOG0000
SYSTEM
(PIN 0
I/O ERROR
PRODUCT NAME: PDEV: 52.0.0
LDEV: DEVICE CLASS: 15
I/O EVENT CLASS: Hardware LLIO STATUS: $E31F0414
RETRY SCHEME: Log Each Retry WILL RETRY: NO
I/O RESULT: I/O Failed RUN AUTODIAG: NO
RETRY COUNT: 0 MGR PORT NUM.: $7
TRANS. NUM.: $2B70B812 # HDWR BYTES: 22
HARDWARE STATUS:
1 2 3 4 5 6 7 8 9 10 11 12
== == == == == == == == == == == ==
1: 00 00 00 02 70 00 02 00 00 00 00 0B
13: 00 00 00 00 3A 00 00 00 00 00
You may see that LOGTOOL has further decoded the HARDWARE STATUS
WK
Problem never ends, you must know how to fix it
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