Bug 144994 - audit errors
Summary: audit errors
Keywords:
Status: CLOSED DUPLICATE of bug 131860
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: audit
Version: 3.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Charlie Bennett
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-01-13 15:38 UTC by Matthew Galgoci
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:07:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Matthew Galgoci 2005-01-13 15:38:03 UTC
Description of problem:

On my RHEL3-U4 boxes, I am getting this error in syslog:

Jan 12 00:00:00 prod CROND[25872]: LAuS error - do_command.c:226 -
laus_attach: (19) laus_attach: No such device
Jan 12 00:01:01 prod CROND[25874]: LAuS error - do_command.c:226 -
laus_attach: (19) laus_attach: No such device
Jan 12 00:05:00 prod CROND[25876]: LAuS error - do_command.c:226 -
laus_attach: (19) laus_attach: No such device
Jan 12 00:10:00 prod CROND[25878]: LAuS error - do_command.c:226 -
laus_attach: (19) laus_attach: No such device
Jan 12 00:15:00 prod CROND[25882]: LAuS error - do_command.c:226 -
laus_attach: (19) laus_attach: No such device

repeat ad-nausea. I get logwatch reports full of this. What does it
mean and how can I make it stop?

This might be concidered a local DOS issue if the log spamming is not
at least rate limited.

Comment 1 Charlie Bennett 2005-01-13 16:57:57 UTC

*** This bug has been marked as a duplicate of 131860 ***

Comment 2 Red Hat Bugzilla 2006-02-21 19:07:55 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


Note You need to log in before you can comment on or make changes to this bug.