SEO

#1 (**permalink**) 01-05-2008, 02:47 AM

I am using the liberrlog functions such as errlog_open and
errlog_find_next to process the AIX errlog. I have no trouble at all
accessing the errlog records, but I have no idea how to access the
text of the record.

AFAICT, the generic error message and information about how to use
el_details and other members of the errlog_entry_t struct is found in
the /var/adm/ras/errtmplt binary file. I can't find any API for
processing this file. The only documentation for this file is in the
man page for errupdate, which has its own file format that is
converted to the binary errtmplt format.

Can anyone point me in the right direction for taking an
errlog_entry_t from errlog_find_next and getting the generic error
message, and the specific error text?

#2 (**permalink**) 01-05-2008, 02:47 AM

Peter, liberrlog doesn't really give you the error text. I guess by the
"generic error message" you mean the error description, and the "specific
error text" would be the detail data. What you lack then is the
description, the detail data is in el_detail_data. To get the error
description you'll need to run errpt, perhaps using the popen() subroutine.

You could run "errpt -tJ<el_label>". You'll get a header followed by the
line containing the error description, (e.g.)

Id Label Type CL Description
B6048838 CORE_DUMP PERM S SOFTWARE PROGRAM ABNORMALLY TERMINATED

This shows the output from "errpt -tJCORE_DUMP". There is no API for
reading the templates.
--
--
Jim Shaffer
http://www.jjshaffer.net
jjs@jjshaffer.net
Web page name and AllInPlay nickname: Cyber Blink
home: (512)989-5701
work: (512)989-5537

"Peter Jones" <google@pmade.org> wrote in message
news:81958db4.0407140755.3cc3ac81@posting.google.c om...
> I am using the liberrlog functions such as errlog_open and
> errlog_find_next to process the AIX errlog. I have no trouble at all
> accessing the errlog records, but I have no idea how to access the
> text of the record.
>
> AFAICT, the generic error message and information about how to use
> el_details and other members of the errlog_entry_t struct is found in
> the /var/adm/ras/errtmplt binary file. I can't find any API for
> processing this file. The only documentation for this file is in the
> man page for errupdate, which has its own file format that is
> converted to the binary errtmplt format.
>
> Can anyone point me in the right direction for taking an
> errlog_entry_t from errlog_find_next and getting the generic error
> message, and the specific error text?

#3 (**permalink**) 01-05-2008, 02:48 AM

<jjs@jjshaffer.net> wrote in message news:<10fd2qso9h11104@corp.supernews.com>...
> Peter, liberrlog doesn't really give you the error text. I guess by the
> "generic error message" you mean the error description, and the "specific
> error text" would be the detail data. What you lack then is the
> description, the detail data is in el_detail_data.

Thanks Jim. The problem with el_detail_data, from what I can tell, is
that you have no idea with the format of that data is without the
template. The template will tell you what parts are ASCII, and what
parts are binary/hex.

I really hate to have to run errpt from within my code. Is there any
details on the format of the errtmplt file? If I knew the fields of
the binary records, and how they are laid out, I could parse the
errtmplt file on my own.

Thanks again.

#4 (**permalink**) 01-05-2008, 02:48 AM

Peter, no, there's no documentation on processing the errtmplt file.

--
--
Jim Shaffer
http://www.jjshaffer.net
jjs@jjshaffer.net
Web page name and AllInPlay nickname: Cyber Blink
home: (512)989-5701
work: (512)989-5537

"Peter Jones" <google@pmade.org> wrote in message
news:81958db4.0407151312.741b1f7b@posting.google.c om...
> <jjs@jjshaffer.net> wrote in message
news:<10fd2qso9h11104@corp.supernews.com>...
> > Peter, liberrlog doesn't really give you the error text. I guess by
the
> > "generic error message" you mean the error description, and the
"specific
> > error text" would be the detail data. What you lack then is the
> > description, the detail data is in el_detail_data.
>
> Thanks Jim. The problem with el_detail_data, from what I can tell, is
> that you have no idea with the format of that data is without the
> template. The template will tell you what parts are ASCII, and what
> parts are binary/hex.
>
> I really hate to have to run errpt from within my code. Is there any
> details on the format of the errtmplt file? If I knew the fields of
> the binary records, and how they are laid out, I could parse the
> errtmplt file on my own.
>
> Thanks again.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

liberrlog and errtmplt