Bug 144994

Summary:	audit errors
Product:	Red Hat Enterprise Linux 3	Reporter:	Matthew Galgoci <mgalgoci>
Component:	audit	Assignee:	Charlie Bennett <ccb>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.0	CC:	mjc
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-02-21 19:07:55 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.