Article
If you run your GroupWise resources on a NCS cluster you should not use GWHA; use cluster monitoring instead. If you enable monitoring a sample script is created for you testing only the POOL and the VOLUME. So you might want to add a simple monitoring script.
Create a script "1677.sh" with the following content:
#!/bin/sh
netstat -lnt | grep -wq ${1}:1677
1677 is the GroupWise Post-office default port; feel free to change it to whatever you actually have in use.
Flag it executable
chmod +x 1677.sh
and copy it on every cluster node. In you NCS cluster monitor script add the following line(s).
exit_on_error /opt/rz/1677.sh PO1-IPAddress
Your monitor script should look now like:
#!/bin/bash . /opt/novell/ncs/lib/ncsfuncs exit_on_error status_fs /dev/evms/POOLNAME /opt/novell/nss/mnt/.pools/POOLNAME nsspool exit_on_error status_secondary_ipaddress ClusterResourceIP exit_on_error ncpcon volume VOLUMENAME # PostOffice Test exit_on_error /opt/rz/1677.sh PO1-IPAddress exit_on_error /opt/rz/1677.sh PO2-IPAddress exit 0
Finally enable and configure monitoring on the cluster resource in iManager.

Pretty easy and it works perfect, enjoy!
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.
Related Articles
- GroupWise 8 - 3 node Cluster (OES2) - Scripts for YOU!
- GroupWise Monitoring in OES2 Novell Clustering
- Troubleshooting Groupwise High Availability in a Linux Cluster Environment
- OES2 Rolling Cluster Upgrade from NetWare - Part 5 - iPrint Web Code Migration to OES2 Linux
- Setting Up GroupWise Clustering with OES2
User Comments
- Be the first to comment! To leave a comment you need to Login or Register
- 3106 reads


0