cancel
Showing results for 
Search instead for 
Did you mean: 

audit_tool looping

dom kris
Frequent Advisor

audit_tool looping

Hi,

on some of our Tru64 v5.1B systems the audit_tool loops.
Basically, when activating audting, we trim the audit logs once a month. This is done by the following crontab entry:
"
0 12 1 * * /usr/lbin/auditlogtrim 1
"

This cmd seems to use audit_tool. However, on some of our systems the audit_tool goes into a loop and takes up all the cpu.
"
481967 root 62 0 3808K 696K run 400.4H 99.00% audit_tool"

As you can see, it has been running 400h with 99% cpu. The only thing that I can do is kill the process.

This is most annoying since we are going to enable auditing on all our Tru64 server and this problem might be a show stopper.

Does anybody have noticed the same problem?

With kind regards,

Kris
3 REPLIES
Ralf Puchner
Honored Contributor

Re: audit_tool looping

You can check with the kernel debugger or truss/trace which routine uses so much cpu time.

As I remember audit_tool runs a long time (several days) if the audit informations are very old/long. Workaround was to purge old audit informations.
Help() { FirstReadManual(urgently); Go_to_it;; }
Ann Majeske
Honored Contributor

Re: audit_tool looping

If you have a support contract I suggest that you open a problem report.
dom kris
Frequent Advisor

Re: audit_tool looping

Do solve the problem I just deleted the entry from the crontab. We keep 1 month of audit files on disk, the rest is purged (they are backuped).

Kd