Groupwise cluster resource goes comatose when unloaded or during failover.
(Last modified: 25Nov2002)
This document (10074866) is provided subject to the disclaimer at the end of this document.
fact
Novell NetWare 5.1
Novell GroupWise 6 SP1
Cluster Services 1.6
Novell NetWare Cluster Services Support Pack 3
symptom
Groupwise cluster resource goes comatose when unloaded or during failover.
Problem only occurs if Groupwise resource is loaded in protected memory.
Resource has to be manually unloaded.
Cluster volumes do not failover.
If the unload script is entered at the console manually, it works just fine.
If GroupWise is not loaded in protected memory, it loads and unloads fine.
CLUSTER-<WARNING>-<10180>: CRM: Error executing load script for groupwise failed on command line 7 unload kill address space =pronosmta
CLUSTER-<WARNING>-<10180>: CRM: Error executing load script for groupwise failed on command line 4 unload kill address space =examplepoa
CVSBIND(deregister): CLUSTEREXAMPLE_NSSGW_SERVER x.x.x.x:524
WSASetService() failed, error = -1, 10109
CLUSTER-<WARNING>-<10180>: CRM: Error executing load script for groupwise failed on command line 10 CVSBIND DEL CLUSTEREXAMPLE_NSSGW_SERVER x.x.x.x
change
Applied NW5SP4.EXE and Cluster Services SP3
fix
This issue has been reported to development.
As a workaround, put the commands from the unload script into an NCF file and execute the ncf file as part of the cluster resource unload script.
document
| Document Title: | Groupwise cluster resource goes comatose when unloaded or during failover. |
| Document ID: | 10074866 |
| Solution ID: | NOVL82386 |
| Creation Date: | 24Sep2002 |
| Modified Date: | 25Nov2002 |
| Novell Product Class: | Groupware NetWare |
disclaimer
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.