- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: audisp: bad audit record body.
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
04-22-2004 03:39 AM
04-22-2004 03:39 AM
/usr/lbin/tsconvert -c
/usr/lbin/modprpw -V
/usr/bin/audevent -E
/usr/bin/audsys -n -c audnames -s 20000
I am getting the follwing error with audisp.
Anyone know why?
# audisp -e open /.secure/etc/audnames
audisp -e open /.secure/etc/audnames
All users are selected.
Selected the following events:
open
5120
All ttys are selected.
Selecting successful & failed events.
TIME PID E EVENT PPID AID RUID RGID EUID EGID TTY
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
audisp: bad audit record body.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-22-2004 02:36 PM
04-22-2004 02:36 PM
SolutionYour problem points to a patch needed.
. PHKL_28445 - HP-UX 11.00 audit subsystem cumulative patch
. PHKL_28446 - HP-UX 11.11 audit subsystem cumulative patch
symptoms:
audisp(1M) aborts with error message "bad audit record body" on certain audit trails.
regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2004 01:50 AM
04-23-2004 01:50 AM
Re: audisp: bad audit record body.
I also found out that you must run
trusted host also. Unless someone has
figured out how to run auditing without
trusted host turned on.
tsconvert -c
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2004 04:42 AM
04-23-2004 04:42 AM
Re: audisp: bad audit record body.
You're right - you must have a trusted system to run auditing. The audit id is stored within /tcb which is not present on a non-trusted system.
regards,
Darren.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-26-2004 09:26 AM
04-26-2004 09:26 AM
Re: audisp: bad audit record body.
I was using the wrong file, audnames, which
is a data file used by auditing.
I was also able to get auditing to work
without having to run the system in
trusted system mode and still use NIS.
ypcat passwd > /etc/passwd
tsconvert -c
modprpw -V
cpio files in /tcb to a temporary directory.
tsconvert -r
Take out nis passwd info from /etc/passwd and add +.
mkdir /tcb and cpio files from temporary
directory.
mkdir -p /.secure/etc
audsys -n -c /.secure/etc/audit1 -s 1000
audisp /.secure/etc/audit1
Works. And I can still rlogin in as root, etc...
If you add a new UNIX account you would
have to edit the /tcb files as needed though
unless you script something.
I will have to look into making the systems
real trusted systems with NIS+ but just don't
have the time right now and it would break
to many things.