Cool Solutions

Configure GroupWise High Availability (GWHA) in 5 easy steps!

peter6960

By:

March 1, 2011 2:28 pm

Reads: 10215

Comments:4

Score:0

written by Peter van der Walt for www.netcb.com

 

Introduction

Enabling the GWHA component on Linux enables your GroupWise system to automatically restart agents when they stop running for whatever reason. This greatly reduces manual administration and system downtime.

I have been configuring this on all my GroupWise installations on Linux and have only had great experiences with this.

I have found the Novell documentation to be a bit vague, so it took me a day or two to figure out how to actually deploy GWHA – I thus decided to create a article showing how easily it can be deployed, requiring only 5 simple steps!

Steps

  1. Install GroupWise Monitor on one of the GroupWise servers
    1. Install and Configure GW Monitor on one server
  2. Edit the /etc/init.d/grpwise-ma script and uncomment the MA-OPTIONS line.In the screenshot below, you can see a Sample:

    The modifed /etc/init.d/grpwise-ma script

    Leave the Username as ‘gwha’, change the password to whatever you want to use, and change the Poll time to how many seconds you want to wait before checking the agents are still running.

  3. On all the GroupWise servers to be monitored:– check /etc/opt/novell/groupwise/gwha.conf
    – run ‘useradd gwha’ to create a local user for GWA to run as
    – run ‘passwd gwha’ to set the user’s password to the one used in step 2.
    – Yast -> Xinetd -> gwha -> Toggle Status On – to ensure that the GWHA is enabled.
  4. Test that the GWHA daemon is listening (netstat -nl | grep 8400)
  5. Test by killing the agent’s processes and confirm that GWHA restarts the agents

    Do a ‘ps -eaf | grep mta’ for example, and kill the MTA’s process using a ‘kill -9 <PID>’

    Do a ‘rcgrpwise status’ to see if the MTA’s status goes “dead” followed by “running” after the GroupWise monitor’s poll time passed, it detected the agent as dead and restarted it.

Conclusion

As simple as that! In 5 easy steps you have configured GroupWise High Availability!

If any of the gwpoa, gwmta, gwinter or gwia processes should stop running – the GroupWise monitor will detect the agent status as Dead and issue the start command through the GWHA daemon – in seconds without any operator intervention!

VN:F [1.9.22_1171]
Rating: 0.0/5 (0 votes cast)

Tags:
Categories: GroupWise, Technical

Disclaimer: This content is not supported by Novell. 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 it thoroughly before using it in a production environment.

4 Comments

  1. By:1032600

    1) If you use the SuSEfirewall2, be sure to open port 8400 on every server that hosts agents.
    2) Run the Monitor Agent, if possible, on a server different from your agent servers.
    3) Become familiar with /var/run/novell/groupwise/*.pid files as these directly correlate with the results you see when you run ‘rcgrpwise status’. I.e. when you see status “[unused]” on your agents, it means there is no .pid file for that agent, not necessarily that the agent isn’t running. Confirm whether an agent is truly running with ‘ps -ax | grep gw”.
    4) You can also use “rcgrpwise stop …” to test the auto-restarting of agents; this will gracefully shut down your agent instead of abruptly (kill -9). Then use repeated “rcgrpwise status” to watch for the agent to change to “Running” status.

    VN:F [1.9.22_1171]
    Rating: 0.0/5 (0 votes cast)
  2. By:sharfuddin

    Thanks for sharing this Article.

    and what if a node/box running a service/role like Post Office(PO) goes offline ? I mean does GWHA also starts the service(e,g PO , IA, MTA) on another node if the primary server for that role goes offline.

    And is it also possible to configure GWHA to make a Load Balancing Cluster of Internet Agents.

    VN:F [1.9.22_1171]
    Rating: 0.0/5 (0 votes cast)
  3. By:abens

    I installed GW Montior and I can see all my PO’s the MTA and such. I configured the the grpwise-ma file, verified the GWHA is enabled in Yast and ran a ps -aef | grep gwha to verify it was running. I shut down the MTA and it never comes back up.

    OES Linux 2.0.3 x64 SLES 10 sp 3 GW 2012 SP1

    I must have missed something.

    VN:F [1.9.22_1171]
    Rating: 0.0/5 (0 votes cast)
    • By:hillt

      When that happens to me it’s usually a new server where I’ve forgotten to add the “gwha” user (with the correct password) to that server. You might want to double-check that step.

      VN:F [1.9.22_1171]
      Rating: 0.0/5 (0 votes cast)

Comment

RSS