09-09-2003
errpt
Hello World,
When I issue the errpt command
1581762B 0826133303 T H hdisk1 DISK OPERATION ERROR
C14C511C 0826133303 T H scsi0 ADAPTER ERROR
I found these two unusual errors, wat exactly do these mean ?
Im on an aix box.
Thanks
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
hi, i have an entry in errpt on aix... any help?
---------------------------------------------------------------------------
LABEL: AMQFFST3
IDENTIFIER: 8FED25B9
Date/Time: Fri Nov 15 07:20:05
Sequence Number: 2715
Machine Id: 000694DF4C00
Node Id: ... (1 Reply)
Discussion started by: yls177
1 Replies
2. AIX
Hi All,
I have multiple error on my AIX 53. How do I trim the report per date only?
Please help.
Thanks,
itik (3 Replies)
Discussion started by: itik
3 Replies
3. Shell Programming and Scripting
I am looking for a script out there that can email me when my AIX server throws and error that is picked up by errpt -a
Thanks
SeaCros (6 Replies)
Discussion started by: seacros
6 Replies
4. UNIX for Dummies Questions & Answers
When i use the errpt command, i just want to see the timestamp and description only. How do i filter this out.
errpt |awk '{print $2,$6}'
The above commnad works but the description field becomes truncated.
The result for the above command as below
TIMESTAMP DESCRIPTION
0524143109... (7 Replies)
Discussion started by: ienaris
7 Replies
5. AIX
Hello
I have this message from errpt command
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
BFE4C025 0803155809 P H sysplanar0 UNDETERMINED ERROR
BFE4C025 0802155509 P H sysplanar0 UNDETERMINED ERROR
BFE4C025 0801155209 P H sysplanar0 UNDETERMINED ERROR
BFE4C025 ... (6 Replies)
Discussion started by: lo-lp-kl
6 Replies
6. Emergency UNIX and Linux Support
The below is my code
in general according to AIX books
To display a detailed report of all errors logged in the past 24 hours, enter:
errpt -a -s mmddhhmmyy
where the mmddhhmmyy string equals the current month, day, hour, minute, and year, minus 24 hours.
I have tried the... (2 Replies)
Discussion started by: Sounddappan
2 Replies
7. AIX
I am getting this temporary error on my errpt:
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
0873CF9F 0623104510 T S pts/0 TTYHOG OVER-RUN
LABEL: TTY_TTYHOG
IDENTIFIER: 0873CF9F
Date/Time: Tue Jun 22 02:00:53 GMT+08:00 2010
Sequence Number: 76... (3 Replies)
Discussion started by: famasutika
3 Replies
8. AIX
my system get rebooted by its self after its came up i try to check the error log
P690/>errpt | more
Cannot open error message catalog /usr/lib/nls/msg/en_US/codepoint.cat.
The error report will still run, but it will not have explanatory messages
P690/>ls -lrt... (1 Reply)
Discussion started by: thecobra151
1 Replies
9. AIX
Hi Team,
I am getting the following error when I do an errpt. What do I need to do to fix it.
LABEL: LVM_SA_STALEPP
IDENTIFIER: EAA3D429
Date/Time: Sat 12 Jan 01:10:56 2013
Sequence Number: 880
Machine Id: 00C57B904C00
Node Id: spg-lplaw-01... (1 Reply)
Discussion started by: ranjithm
1 Replies
10. AIX
Hi,
just a short question:
Is a error label always equal to a error identifier?
So it does not matter if i search for an specific identifier (errpt -j) or a specific label (errpt -J)?
Regards
Ron (5 Replies)
Discussion started by: -=XrAy=-
5 Replies
LEARN ABOUT CENTOS
error::pass4
ERROR::PASS4(7stap) ERROR::PASS4(7stap)
NAME
error::pass4 - systemtap pass-4 errors
DESCRIPTION
Errors that occur during pass 4 (compilation) have generally only a few causes:
kernel or OS version changes
The systemtap runtime and embedded-C fragments in the tapset library are designed to be portable across a wide range of OS versions.
However, incompatibilities can occur when some OS changes occur, such as kernel modifications that change functions, types, or
macros referenced by systemtap. Upstream builds of systemtap are often quickly updated to include relevant fixes, so try getting or
making an updated build. If the issue persists, report the problem to the systemtap developers.
buggy embedded-C code
Embedded-C code in your own guru-mode script cannot be checked by systemtap, and is passed through verbatim to the compiler. Errors
in such snippets of code may be found during the pass-4 compiler invocation, though may be hard to identify by the compiler errors.
incompatible embedded-C code
The interface standards between systemtap-generated code and embedded-C code occasionally change. For example, before version 1.8,
arguments were passed using macros THIS->foo and THIS->__retvalue but from version 1.8 onward, using STAP_ARG_foo and STAP_RETVALUE.
Adjust your embedded-C code to current standards, or use the stap --compatible=VERSION option to make systemtap use a different one.
GATHERING MORE INFORMATION
It may be necessary to run systemtap with -k or -p3 to examine the generated C code. Increasing the verbosity of pass-4 with an option
such as --vp 0001 can also help pinpoint the problem.
SEE ALSO
stap(1),
error::reporting(7stap)
ERROR::PASS4(7stap)