[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | MAILBUS - Message Router and its Gateways |
| Notice: | Kit Copy Utility - 100.1, Problems - 5.*, Kit Support - 103.1 |
| Moderator: | FORTY2::YUILLE |
|
| Created: | Thu Jun 11 1992 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3209 |
| Total number of notes: | 7125 |
3170.0. "RECOVER DDS fail to create config and database files" by GIDDAY::LEH () Mon Feb 17 1997 06:18
MR V3.3-313 on VMS 6.2 running DECnet IV
Failure to do RECOVER DDS on node BRIGGS, a MicroVAX 3900, as part of the
cluster CBTEST, comprising of
BRIGGS VMS V6.2 MEMBER
HAWKER VMS V6.2 MEMBER
where HAWKER is an Alpha.
This was the fresh installation of MR on the VAX, where remote MR will be used
on the Alpha to eventually support IOS 3.2
Ob BRIGGS, logicals
"MR$NODE" = "BRIGGS::"022=""
"OA$A1_CLUSTER_NODE" = "BRIGGS"
"OA$PRIMARY_NODE" = "BRIGGS"
"PRINTER_NODE" = "HAWKER"
"SHUTDOWN$INFORM_NODES" = "BRIGGS"
"SYS$CLUSTER_NODE" = "CBTEST::"
"SYS$DECDTM_NODE_ADDRESS" = "1128"
"SYS$DECDTM_NODE_NAME" = "BRIGGS"
"SYS$NODE" = "BRIGGS::"
"SYS_NODE_LIST" = "HAWKER"
are set, and its NCP had Alias incoming disabled
Have tried the basic config, DEFAULT on this node; but consistently failed
with
%MB-E-DDSERR, error during MBMAN set configuration
%MB-E-MBC$RECERR, Problem during configuration database recovery phase for DDS
where DDS config file and its database files weren't created
MB$DDSCVP passed file checking stage, but failed afterwards
.........
Starting the MBMAN utility
Starting the Directory Service
%DDS-W-NOMSG, Message number 01458090
-SYSTEM-F-LINKEXIT, network partner exited
%MB-E-DDSERR, DDS request failed
-DDS-E-NOMSG, Message number 01458042
%MB-E-CVPERR, the DDS V3.3-313 CVP FAILED.
Shutting down Directory Service
%MB-E-DDSERR, DDS request failed
-DDS-E-NOMSG, Message number 01458072
Shutting MRMAN and MBMAN
...........
Herewith the stored config:
MBC> show dds
%MB-I-MBC$CURSETS, Current settings for configuration parameters
File: DSA1000:[MB$.MB.MB$WORK]MB$CNFDB_.DAT
on 17-FEB-1996 17:05
Device for the Directory Service: DSA1000:
Alarm level of free blocks for the Directory Service : 20000
Directory Service master node : BRIGGS
Directory Service node number for this node : 1128
Directory Service enabled
and the Recovery stage with Security ON
MBC> reco dds
%MB-I-MBC$RECOVER, Recovering configuration database
%MB-I-MBC$RECPHASE, Beginning recovery phase for DDS
%MB-I-CHKDDSREL, checking if DDS relocated to different location ...
%MB-I-CREDDSCNF, creating configuration file for DDS ...
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:10.34 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object access
Event time: 17-FEB-1996 16:33:10.32
PID: 20401837
Process name: _RTA2:
Username: FIELD
Process owner: [FIELD]
Terminal name: RTA2:
Object class name: FILE
Directory name: _DSA1000:[MB$.MB]MB$WORK.DIR;1
Directory ID: (393,933,0)
Directory entry: MB$TXNDB_.DAT;5
Access requested: EXECUTE
Sequence key: 00124B64
Status: %SYSTEM-S-NORMAL, normal successful completion
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:10.38 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object access
Event time: 17-FEB-1996 16:33:10.35
PID: 20401837
Process name: _RTA2:
Username: FIELD
Process owner: [FIELD]
Terminal name: RTA2:
Object class name: FILE
File name: _DSA1000:[MB$.MB.MB$WORK]MB$TXNDB_.DAT;5
File ID: (1045,492,0)
Access requested: READ,WRITE
Privileges used: SYSPRV,GRPPRV
Deaccess key: 83C616C0
Sequence key: 00124B64
Status: %SYSTEM-S-NORMAL, normal successful completion
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:10.82 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object deaccess
Event time: 17-FEB-1996 16:33:10.81
PID: 20401837
Object class name: FILE
Deaccess key: 83C616C0
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:10.94 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object access
Event time: 17-FEB-1996 16:33:10.92
PID: 20401837
Process name: _RTA2:
Username: FIELD
Process owner: [FIELD]
Terminal name: RTA2:
Object class name: FILE
Directory name: _DSA1000:[SYS0]SYSMAINT.DIR;1
Directory ID: (685,1,0)
Directory entry: RESET.;0
Access requested: EXECUTE
Sequence key: 00124B77
Status: %SYSTEM-S-NORMAL, normal successful completion
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:10.99 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object access
Event time: 17-FEB-1996 16:33:10.97
PID: 20401837
Process name: _RTA2:
Username: FIELD
Process owner: [FIELD]
Terminal name: RTA2:
Object class name: FILE
Directory name: _DSA1000:[VMS$COMMON]SYSMAINT.DIR;1
Directory ID: (2956,2,0)
Directory entry: RESET.;0
Access requested: EXECUTE
Sequence key: 00124B7A
Status: %SYSTEM-S-NORMAL, normal successful completion
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:11.05 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object access
Event time: 17-FEB-1996 16:33:11.03
PID: 20401837
Process name: _RTA2:
Username: FIELD
Process owner: [FIELD]
Terminal name: RTA2:
Object class name: FILE
Directory name: _DSA1000:[SYS0]SYSMAINT.DIR;1
Directory ID: (685,1,0)
Directory entry: MB$MBC_BRIGGS_BCKERR.TMP;0
Access requested: EXECUTE
Sequence key: 00124B7D
Status: %SYSTEM-S-NORMAL, normal successful completion
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:11.10 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object access
Event time: 17-FEB-1996 16:33:11.08
PID: 20401837
Process name: _RTA2:
Username: FIELD
Process owner: [FIELD]
Terminal name: RTA2:
Object class name: FILE
Directory name: _DSA1000:[VMS$COMMON]SYSMAINT.DIR;1
Directory ID: (2956,2,0)
Directory entry: MB$MBC_BRIGGS_BCKERR.TMP;0
Access requested: EXECUTE
Sequence key: 00124B80
Status: %SYSTEM-S-NORMAL, normal successful completion
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:11.20 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object access
Event time: 17-FEB-1996 16:33:11.18
PID: 20401837
Process name: _RTA2:
Username: FIELD
Process owner: [FIELD]
Terminal name: RTA2:
Object class name: FILE
Directory name: _DSA1000:[SYS0]SYSMAINT.DIR;1
Directory ID: (685,1,0)
Directory entry: RESET.;0
Access requested: EXECUTE
Sequence key: 00124B85
Status: %SYSTEM-S-NORMAL, normal successful completion
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:11.25 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object access
Event time: 17-FEB-1996 16:33:11.23
PID: 20401837
Process name: _RTA2:
Username: FIELD
Process owner: [FIELD]
Terminal name: RTA2:
Object class name: FILE
Directory name: _DSA1000:[VMS$COMMON]SYSMAINT.DIR;1
Directory ID: (2956,2,0)
Directory entry: RESET.;0
Access requested: EXECUTE
Sequence key: 00124B88
Status: %SYSTEM-S-NORMAL, normal successful completion
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:11.31 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object access
Event time: 17-FEB-1996 16:33:11.29
PID: 20401837
Process name: _RTA2:
Username: FIELD
Process owner: [FIELD]
Terminal name: RTA2:
Object class name: FILE
Directory name: _DSA1000:[MB$.MB]MB$SCRATCH.DIR;1
Directory ID: (429,458,0)
Directory entry: MB$MBC_BRIGGS_DDSCNF.TMP;1
Access requested: EXECUTE
Sequence key: 00124B8B
Status: %SYSTEM-S-NORMAL, normal successful completion
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:11.36 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object access
Event information: known file access request ($OPEN)
Event time: 17-FEB-1996 16:33:11.34
PID: 20401837
Process name: _RTA2:
Username: FIELD
Process owner: [FIELD]
Terminal name: RTA2:
Object class name: FILE
Object name: DSA1000:[SYS0.SYSCOMMON.][SYSEXE]DELETE.EXE;
Access requested: READ
Status: %SYSTEM-S-NORMAL, normal successful completion
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:11.41 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object access
Event information: known file access request ($OPEN)
Event time: 17-FEB-1996 16:33:11.39
PID: 20401837
Process name: _RTA2:
Username: FIELD
Process owner: [FIELD]
Terminal name: RTA2:
Object class name: FILE
Object name: DSA1000:[SYS0.SYSCOMMON.][SYSLIB]LIBRTL.EXE;
Access requested: READ
Status: %SYSTEM-S-NORMAL, normal successful completion
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:11.50 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object access
Event time: 17-FEB-1996 16:33:11.45
PID: 20401837
Process name: _RTA2:
Username: FIELD
Process owner: [FIELD]
Terminal name: RTA2:
Image name: DSA1000:[SYS0.SYSCOMMON.][SYSEXE]DELETE.EXE
Object class name: FILE
File name: _DSA1000:[MB$.MB]MB$SCRATCH.DIR;1
File ID: (429,458,0)
Access requested: READ
Deaccess key: 83C5D100
Sequence key: 00124B95
Status: %SYSTEM-S-NORMAL, normal successful completion
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:11.56 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object deaccess
Event time: 17-FEB-1996 16:33:11.55
PID: 20401837
Object class name: FILE
Deaccess key: 83C5D100
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:11.61 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object access
Event time: 17-FEB-1996 16:33:11.58
PID: 20401837
Process name: _RTA2:
Username: FIELD
Process owner: [FIELD]
Terminal name: RTA2:
Image name: DSA1000:[SYS0.SYSCOMMON.][SYSEXE]DELETE.EXE
Object class name: FILE
File name: _DSA1000:[MB$.MB]MB$SCRATCH.DIR;1
File ID: (429,458,0)
Access requested: READ
Deaccess key: 83C5D100
Sequence key: 00124B9D
Status: %SYSTEM-S-NORMAL, normal successful completion
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:11.64 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object deaccess
Event time: 17-FEB-1996 16:33:11.63
PID: 20401837
Object class name: FILE
Deaccess key: 83C5D100
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:11.83 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object access
Event time: 17-FEB-1996 16:33:11.80
PID: 20401837
Process name: _RTA2:
Username: FIELD
Process owner: [FIELD]
Terminal name: RTA2:
Image name: DSA1000:[SYS0.SYSCOMMON.][SYSEXE]DELETE.EXE
Object class name: FILE
Directory name: _DSA1000:[MB$.MB]MB$SCRATCH.DIR;1
Directory ID: (429,458,0)
Directory entry: MB$MBC_BRIGGS_DDSCNF.TMP;1
Access requested: READ,WRITE
Privileges used: SYSPRV,GRPPRV
Sequence key: 00124BA4
Status: %SYSTEM-S-NORMAL, normal successful completion
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:11.86 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object deletion
Event time: 17-FEB-1996 16:33:11.84
PID: 20401837
Process name: _RTA2:
Username: FIELD
Process owner: [FIELD]
Terminal name: RTA2:
Image name: DSA1000:[SYS0.SYSCOMMON.][SYSEXE]DELETE.EXE
Object class name: FILE
File name:
_DSA1000:[MB$.MB.MB$SCRATCH]MB$MBC_BRIGGS_DDSCNF.TMP;1
File ID: (23,1806,0)
Access requested: DELETE
Privileges used: SYSPRV,GRPPRV
Deaccess key: 83C5EA00
Sequence key: 00124BA4
Status: %SYSTEM-S-NORMAL, normal successful completion
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:11.97 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object access
Event time: 17-FEB-1996 16:33:11.95
PID: 20401837
Process name: _RTA2:
Username: FIELD
Process owner: [FIELD]
Terminal name: RTA2:
Object class name: FILE
Directory name: _DSA1000:[000000]SYS0.DIR;1
Directory ID: (680,1,0)
Directory entry: SYSEXE.DIR;1
Access requested: EXECUTE
Sequence key: 00124BB0
Status: %SYSTEM-S-NORMAL, normal successful completion
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:12.02 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object access
Event time: 17-FEB-1996 16:33:12.00
PID: 20401837
Process name: _RTA2:
Username: FIELD
Process owner: [FIELD]
Terminal name: RTA2:
Object class name: FILE
Directory name: _DSA1000:[SYS0]SYSEXE.DIR;1
Directory ID: (681,1,0)
Directory entry: CREATE.EXE;0
Access requested: EXECUTE
Sequence key: 00124BB3
Status: %SYSTEM-S-NORMAL, normal successful completion
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:12.08 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object access
Event time: 17-FEB-1996 16:33:12.06
PID: 20401837
Process name: _RTA2:
Username: FIELD
Process owner: [FIELD]
Terminal name: RTA2:
Object class name: FILE
Directory name: _DSA1000:[VMS$COMMON]SYSEXE.DIR;1
Directory ID: (2952,4,0)
Directory entry: CREATE.EXE;1
Access requested: EXECUTE
Sequence key: 00124BB9
Status: %SYSTEM-S-NORMAL, normal successful completion
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:12.12 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object access
Event time: 17-FEB-1996 16:33:12.09
PID: 20401837
Process name: _RTA2:
Username: FIELD
Process owner: [FIELD]
Terminal name: RTA2:
Object class name: FILE
File name: _DSA1000:[VMS$COMMON.SYSEXE]CREATE.EXE;1
File ID: (990,51,0)
Access requested: READ,EXECUTE
Deaccess key: 83DFE4C0
Sequence key: 00124BB9
Status: %SYSTEM-S-NORMAL, normal successful completion
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:12.16 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object access
Event information: known file access request ($OPEN)
Event time: 17-FEB-1996 16:33:12.14
PID: 20401837
Process name: _RTA2:
Username: FIELD
Process owner: [FIELD]
Terminal name: RTA2:
Object class name: FILE
Object name: DSA1000:[SYS0.SYSCOMMON.][SYSLIB]LIBRTL.EXE;
Access requested: READ
Status: %SYSTEM-S-NORMAL, normal successful completion
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:12.35 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object access
Event time: 17-FEB-1996 16:33:12.32
PID: 20401837
Process name: _RTA2:
Username: FIELD
Process owner: [FIELD]
Terminal name: RTA2:
Image name: DSA1000:[SYS0.SYSCOMMON.][SYSEXE]CREATE.EXE;1
Object class name: FILE
Directory name: _DSA1000:[MB$.MB]MB$SCRATCH.DIR;1
Directory ID: (429,458,0)
Directory entry: MB$MBC_BRIGGS_DDSCNF.TMP;1
Access requested: READ,WRITE
Privileges used: SYSPRV,GRPPRV
Sequence key: 00124BC4
Status: %SYSTEM-S-NORMAL, normal successful completion
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:12.38 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object creation
Event time: 17-FEB-1996 16:33:12.36
PID: 20401837
Process name: _RTA2:
Username: FIELD
Process owner: [FIELD]
Terminal name: RTA2:
Image name: DSA1000:[SYS0.SYSCOMMON.][SYSEXE]CREATE.EXE;1
Object class name: FILE
File name:
_DSA1000:[MB$.MB.MB$SCRATCH]MB$MBC_BRIGGS_DDSCNF.TMP;1
File ID: (23,1807,0)
Deaccess key: 83C5B4C0
Sequence key: 00124BC4
Status: %SYSTEM-S-NORMAL, normal successful completion
%MB-E-DDSERR, error during MBMAN set configuration
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:12.43 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Privilege used
Event information: GRPPRV used to modify file ownership (SET
FILE/OWNER,
F11BXQP)
Event time: 17-FEB-1996 16:33:12.39
PID: 20401837
Process name: _RTA2:
Username: FIELD
Process owner: [FIELD]
Terminal name: RTA2:
Image name: DSA1000:[SYS0.SYSCOMMON.][SYSEXE]CREATE.EXE;1
Object owner: [FIELD]
Volume name: SYSA_VAX
File name:
_DSA1000:[MB$.MB.MB$SCRATCH]MB$MBC_BRIGGS_DDSCNF.TMP;1
File ID: (23,1807,0)
New object owner: [UCX$AUX,MBMANAGER]
Privileges used: GRPPRV
Sequence key: 00124BC4
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:12.47 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object deaccess
Event time: 17-FEB-1996 16:33:12.46
PID: 20401837
Object class name: FILE
Deaccess key: 83C5B4C0
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:12.56 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object deaccess
Event time: 17-FEB-1996 16:33:12.55
PID: 20401837
Object class name: FILE
Deaccess key: 83DFE4C0
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:12.63 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object access
Event time: 17-FEB-1996 16:33:12.60
PID: 20401837
Process name: _RTA2:
Username: FIELD
Process owner: [FIELD]
Terminal name: RTA2:
Object class name: FILE
Directory name: _DSA1000:[MB$.MB]MB$SCRATCH.DIR;1
Directory ID: (429,458,0)
Directory entry: MB$MBC_BRIGGS_DDSCNF.TMP;1
Access requested: EXECUTE
Sequence key: 00124BD8
Status: %SYSTEM-S-NORMAL, normal successful completion
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:12.66 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object access
Event time: 17-FEB-1996 16:33:12.64
PID: 20401837
Process name: _RTA2:
Username: FIELD
Process owner: [FIELD]
Terminal name: RTA2:
Object class name: FILE
File name:
_DSA1000:[MB$.MB.MB$SCRATCH]MB$MBC_BRIGGS_DDSCNF.TMP;1
File ID: (23,1807,0)
Access requested: READ,WRITE
Privileges used: SYSPRV,GRPPRV
Deaccess key: 83C63F80
Sequence key: 00124BD8
Status: %SYSTEM-S-NORMAL, normal successful completion
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:17.64 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object deaccess
Event time: 17-FEB-1996 16:33:17.63
PID: 20401837
Object class name: FILE
Deaccess key: 83C63F80
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:17.73 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object deaccess
Event time: 17-FEB-1996 16:33:17.72
PID: 20401837
Object class name: FILE
Deaccess key: 83E77C40
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:17.78 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object access
Event time: 17-FEB-1996 16:33:17.76
PID: 20401837
Process name: _RTA2:
Username: FIELD
Process owner: [FIELD]
Terminal name: RTA2:
Object class name: FILE
Directory name: _DSA1000:[MB$.MB]MB$SCRATCH.DIR;1
Directory ID: (429,458,0)
Directory entry: MB$MBC_BRIGGS_DDSCNF.TMP;1
Access requested: EXECUTE
Sequence key: 00124C05
Status: %SYSTEM-S-NORMAL, normal successful completion
%%%%%%%%%%% OPCOM 17-FEB-1996 16:33:17.82 %%%%%%%%%%%
Message from user AUDIT$SERVER on BRIGGS
Security alarm (SECURITY) on BRIGGS, system id: 1128
Auditable event: Object access
Event time: 17-FEB-1996 16:33:17.79
PID: 20401837
Process name: _RTA2:
Username: FIELD
Process owner: [FIELD]
Terminal name: RTA2:
Object class name: FILE
File name:
_DSA1000:[MB$.MB.MB$SCRATCH]MB$MBC_BRIGGS_DDSCNF.TMP;1
File ID: (23,1807,0)
Access requested: READ,EXECUTE
Privileges used: SYSPRV,GRPPRV
Deaccess key: 83C63F80
Sequence key: 00124C05
Status: %SYSTEM-S-NORMAL, normal successful completion
%MB-E-MBC$RECERR, Problem during configuration database recovery phase for DDS
......
Usual checks, incl disk quotas, file access have been done. The above dialup
was done by FIELD account, but customer has also failed with SYSTEM account.
Thanks for any suggestion
Hong
CSC Sydney
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3170.1 | | ACISS2::LENNIG | Dave (N8JCX), MIG, @CYO | Mon Feb 17 1997 13:51 | 36 |
| I'm a bit confused on what you are trying to accomplish.
Do you want MR to use the cluster alias or not? Also, how did you
answer the question about using cluster alias during the CREATE MB?
Why did you disable alias incoming on the VAX member?
Assuming Phase IV on both Alpha and VAX, your config choices are:
1) Use the alias, in which case you would answer Yes to the CREATE MB
alias question and disable alias incoming on the *ALPHA* member
(and use the alias if this was to be the DDS master node)
2) Don't use the alias, in which case you would answer No to CREATE MB,
leave the alias enabled, disabled, or non-existant as you choose
(and use the VAX nodename if this was to be the DDS master node)
Basically, you are choosing how MR will be referenced by other nodes
in the network. If you choose to use the alias, then other nodes in
the network are expected to connect to the cluster alias (and since MR
is not running on the Alpha and you are running Phase IV, you should
disable alias incoming on the Alpha so that random connects to the
alias won't get the member that isn't running MR). If you choose not
to use the alias, then other nodes in the network will connect to MR
on one specific node in the cluster (the VAX) using it's nodename, and
what you do or don't do with the alias is immaterial. If you choose
the latter option, you can only run full MR on that one specific node
(ie if there is more than one VAX member, only the "primary MR node"
can run all the talkers, listeners, servers, etc). If you choose the
former option (with Phase IV decnet) then all nodes with alias incoming
enabled can run full MR. (I won't get into the MINSTART variations).
And of course whichever choice you make needs to be reflected in the
way you configure ALL-IN-1 on the cluster members.
BTW, I see in .0 this was being done from the FIELD account.
Does FIELD meet all the account priv and quota requirments?
Dave
|
| 3170.2 | DDS IVP failed during upgrade installation | GIDDAY::LEH | | Tue Feb 18 1997 06:27 | 97 |
| Dave
Easy answers first:
> Do you want MR to use the cluster alias or not? Also, how did you
> answer the question about using cluster alias during the CREATE MB?
In this instance when the base note was entered,
Reply of N(o) during CREATE MB
> Why did you disable alias incoming on the VAX member?
Didn't want to use alias
> BTW, I see in .0 this was being done from the FIELD account.
> Does FIELD meet all the account priv and quota requirments?
Yes, same problem when I used SYSTEM account today
I learned of more problem details from customer. Their MR upgrade installation
failed on DDS IVP with
................
Directory Service V3.3-313 file check
The total number of files is 7.
All files exist and are the correct size.
End of Directory Service V3.3-313 file check.
Starting the Directory Service
%MB-E-DDSERR, DDS request failed
-DDS-E-NOMSG, Message number 01458072
%DDS-W-NOMSG, Message number 01458090
-SYSTEM-F-LINKEXIT, network partner exited
%MB-E-DDSERR, DDS request failed
-DDS-E-NOMSG, Message number 01458042
%MB-E-IVPERR, the DDS V3.3-313 IVP FAILED.
..............
where 01458072 --> %DDS-E-NOSUP, Function not supported
01458090 --> %DDS-W-FILERR, Error accessing !AS
01458042 --> %DDS-E-SHUTDOWN, DDS has shut down
VMSINSTAL questions and answers:
* Do you want to continue anyway [NO]? y
* Are you satisfied with the backup of your system disk [YES]?
* Does this product have an authorization key registered and loaded? y
* Do you want help text printed before every question [NO]?
* Do you want to purge files replaced by this installation [YES]?
* Do you want to run the IVP after the installation [YES]?
$ ! MR V2.* specs
A Message Router V3.* system has been found. Any data from this
A Message Router V3.* system has been found. Any data from this
* What device is to be used for the MBMANAGER account [DSA1000:]:
* What is the UIC for the MBMANAGER account [UCX$AUX,MBMANAGER]:
* Do you want to keep the same Message Router account passwords [NO]?
* What is the password for the Message Router accounts:
* Confirm the password for the Message Router accounts:
Are [MB$.DDS.WRK]DDS_CONFIG.DAT and [MB$.DDS.DB]DDS*.DAT created during
instal or config phase ? Attempt to do DDS configuration via SET, ENABLE and
RECOVER failed at the last step with
MBC> reco dds
%MB-I-MBC$RECOVER, Recovering configuration database
%MB-I-MBC$RECPHASE, Beginning recovery phase for DDS
%MB-I-CHKDDSREL, checking if DDS relocated to different location ...
%MB-I-CREDDSCNF, creating configuration file for DDS ...
%MB-E-DDSERR, error during MBMAN set configuration
%MB-E-MBC$RECERR, Problem during configuration database recovery phase for DDS
I noticed DDS configuration should create several files in [MB$.MB.MB$SCRATCH]
but in this case only the file MB$MBC_BRIGGS_DDSCNF.TMP was created; and its
interactive execution: @MB$MBC_BRIGGS_DDSCNF.TMP failed at the step
ACCEPT DDS CONFIGURATION
with error %MB-E-DDSERR, DDS request failed
-DDS-E-NOSUP, Function not supported
I tried myself with another installation with full VMSINSTAL OPTIONS tracing
but failed to pick out anything revealing while getting the same error
A colleguage suspected this VAX was a restore from tape backup and as such,
previous MR settings e.g. UIC for the MBMANAGER account [UCX$AUX,MBMANAGER]
can't be changed in an upgrade installation.
How cleaner should this system be, i.e. removing existing UAF accounts/rights
iden, deleting existing [MB$...] files etc.. ?
Thanks for any suggestion
Hong
|
| 3170.3 | | ACISS2::LENNIG | Dave (N8JCX), MIG, @CYO | Tue Feb 18 1997 14:09 | 12 |
| I'm not really sure what to tell you... The fact that the install
procedure says it found a previous installation would seem to indicate
this was not a fresh install. The only place I can think of where you
are likely to get DDS-E-NOSUP is from the *REMOTE* DDS access image
(SYS$LIBRARY:DDS$RMT_VAX // SYS$LIBRARY:DDS$RMT_ALPHA). Is there a
DDS$SHAR logical or DDS$CONFIG logical name table on your system?
If you want to try a semi-clean install, get rid of the SYSUAF and
RIGHTSLIST entries for anything MR related, and delete the [MB$...]
tree and also sys$manager:mb$location.com.
Dave
|
| 3170.4 | yes, it's the remote setup DDS$SHAR | GIDDAY::LEH | | Wed Feb 19 1997 05:16 | 31 |
| Dave
As you pointed out correctly (as always), there existed a system logical
"DDS$SHAR" [exec] = "SYS$LIBRARY:DDS$RMT_VAX.EXE"
probably thanks to the ex-status of the current node, i.e. relying on a remote
MR setup in the past. It was believed this node was re-created from a backup
tape restoration; unfortunately, the above check on this logical had been
overlooked.
As MR installation and configuration also failed to alert this unusal incident,
is there any diagnostic tool that might have revealed the setup? I was thinking
of MB$DEV$STATE but never got around to use it. I looked briefly at the output
of VMSINSTAL with options D(ebug) but nothing stood out.
The 'extra' time in enabling the tracing, audit alarm, plus comparing with
the setup on a working system has been useful in understanding various working
phases of DDS config, e.g. DDS$CONFIG and database files not created/updated
until the command ACCEPT DDS CONFIG is executed. Furthermore, temporary files
MB$MBC_BRIGGS_DDSCNF.TMP, MB$MBC_BRIGGS_DDSDBUPD.TMP MB$MBC_BRIGGS_DDSNCP.TMP
also indicated various DDS updating 'behind the scene"
Glad your suggestion has saved another late night call to you for help
Thanks
Hong
CSC Sydney
|
| 3170.5 | | ACISS2::LENNIG | Dave (N8JCX), MIG, @CYO | Wed Feb 19 1997 11:13 | 10 |
| >>is there any diagnostic tool that might have revealed the setup?
The DDS$SHAR logical and DDS$CONFIG logical name table are created by
SYS$MANAGER:DDS$STARTUP.COM (not to be confused with DDS$START.COM,
which is the procedure kicked off by mb$control) and would typically
be explicitly invoked in the system startup procedure. I don't know if
you consider 'TYPE SYS$MANAGER:SYSTARTUP_VMS.COM' a "diagnostic tool",
but it would have "revealed the setup" :-)
Dave
|
| 3170.6 | if it's that simple ! | GIDDAY::LEH | | Fri Feb 21 1997 06:10 | 17 |
| Dave
> The DDS$SHAR logical and DDS$CONFIG logical name table are created by
> SYS$MANAGER:DDS$STARTUP.COM (not to be confused with DDS$START.COM,
> which is the procedure kicked off by mb$control) and would typically
> be explicitly invoked in the system startup procedure. I don't know if
> you consider 'TYPE SYS$MANAGER:SYSTARTUP_VMS.COM' a "diagnostic tool",
> but it would have "revealed the setup" :-)
I was thinking of , in addition to VMSINSTAL OPTIONS switches, any intelligent
alerts from MR/DDS utilities such as instal or config that might detect the
existence of DDS$SHAR when an attempt to install or configure is invoked.
Failure at DDS IVP stage was very unusual; more so when no config file and
database were created.
Hong
|