| Title: | Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server |
| Notice: | Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server |
| Moderator: | CPEEDY::KENNEDY |
| Created: | Fri Dec 18 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4319 |
| Total number of notes: | 18478 |
Pathworks/VMS 5.0D -eco3 OpenVMS 6.1 cluster The PWRK$LMSRV logfile contains numerous of the following errors: FATAcquireClusterLock: lock conversion failed, lockid=xxxxxx, status=00002124 FATGetSecurityBuffer: failed to acquire lock, status 00002124 The PWRK$LMSRV logfile ends with the following stack dump: Highly ungood from module LM$BLD_ROOT:[LM.UTIL.SRC]GC.C at line 311! Module Name Routine Name Line number rel PC GC checkptr 8907 000004FC GC gcfree 9421 00002Bd4 etc, etc. Are these related problems? I believe the dump has been IPMT'd before in CFS 43196/41596 which resulted in a patch for 5.0d-eco2 ? This patch is not included in 5.0d-eco3 ? Rein Harle Digital Pathworks Support
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4214.1 | VMSNET::P_NUNEZ | Wed Mar 19 1997 13:43 | 13 | ||
Rein,
I think there were still a few GC problems in v5.0D ECO3, but one of
the engineers will need to confirm (do an IPMT).
Might also want to be sure that vms 6.1 (AXP or VAX?) is up to rev
level in respect to cluster locking (status 00002124=invalid lock id).
Find whatever ECO is supplying the most recent version of LOCKING.EXE
and make sure you have it cluster wide. For example, for VAX/VMS V6.1,
VAXSHAD09_061 has it (even though you may not use host-based volume
shadowing, apply the kit anyway).
Paul
| |||||
| 4214.2 | UTRTSC::SWEEP | I want a lolly... | Thu Apr 10 1997 07:27 | 6 | |
All GC buffer problems fixed in e eco 1, but there is 1 little
problem left with account login hours that could cause a gc buffer
corruption.
Adrie
Rein why don't you walk around the corner to ask.
| |||||