home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.vms
- Path: sparky!uunet!psgrain!hippo!sunvax!hcc
- From: hcc@sunvax.sun.ac.za
- Subject: Audit server file corruption
- Message-ID: <1992Nov23.154109.1@sunvax.sun.ac.za>
- Lines: 44
- Sender: news@hippo.ru.ac.za
- Organization: University of Stellenbosch
- Date: Mon, 23 Nov 1992 13:41:09 GMT
-
- Good day all netters
-
- We're experiencing a problem with our audit servers.
-
- Our environment:
- 5 VAXen clustered over CI, two HSC50s, one system disk, running VMS V5.5-1
- 1 x VAX 780
- 2 x VAX 8650
- 1 x VAX 6320
- 1 x VAX 6510
- SECURITY_AUDIT.AUDIT$JOURNAL file in SYS$MANAGER shared by AUDIT_SERVER
- processes on each node of the cluster.
-
- AUDIT_SERVER is started up by default by VMS, also stopped by VMS with
- system shutdown.
-
- In our SYSTARTUP_V5.COM, we do a
- $ set audit/disable=acl
- when the command procesure starts, and a
- $ set audit/enable=acl
- when the command procedure completes. This is to limit security messages,
- since SYSTARTUP_V5.COM accesses many sensitive files on which we have
- security ACEs.
-
- We have experienced corruption of the SECURITY_AUDIT.AUDIT$JOURNAL file
- a few times in the last months, and have finally linked the last corruption
- with one of our VAXen crashing (the VAX 780). The records are valid in the
- SECURITY_AUDIT.AUDIT$JOURNAL file right upto the time the SYSINIT record was
- made in the ACCOUNTNG.DAT file (on rebooting of the VAX 780 after the crash).
- It would appear as if the SECURITY_AUDIT.AUDIT$JOURNAL file was corrupted
- when the crashed system rejoined the cluster.
-
- What is really going on? Is this a known bug? Are we overlooking something
- by disabling and enabling the ACL alarms?
-
- We'd appreciate any info, pointers, hints and/or ideas and will summarize to
- the net if there is any interest.
-
- Thanks in advance
-
- J.A.Nel
- HCC
-
- HCC@SUNVAX.SUN.AC.ZA
-