GroupWise WebAccess Agent stops intermittently and shows status dead

  • 7002916
  • 06-Apr-2009
  • 27-Apr-2012

Environment

Novell GroupWise 8
Novell GroupWise WebAccess 8
Novell Open Enterprise Server 2 (Linux based)

Situation

GroupWise WebAccess Agent stops intermittently.
GroupWise WebAccess Agent status shows "dead"
GroupWise WebAccess Agent crashes.




Resolution

Currently this issue is under investigation.

This document is intended to provide the workaround and will help in keeping the least possible downtime.

Here is a sample scipt to manage agent status. This script checks to see if the webaccess agent is running, if not it restarts it and sends an e-mail notification.

===============================================================================================

#!/bin/bash

declare -i CNT=0
#Modify the name of the GroupWise WebAccess agent startup file to match the actual name.
CNT=`ps -aef | grep -v grep | grep -c '@webac80a.waa'`

if [ $CNT -eq 0 ]
then
echo "Restarting the GroupWise WebAccess"
echo "Restarted the GroupWise WebAccesss" `! date` >> /var/log/novell/groupwise/gwwachk.log
#Modify the name of the WebAccess. Check the name by typing the command "rcgrpwise status". Consider the name which is under brackets.
/etc/init.d/grpwise start WEBAC80A &
mail -s "GroupWise WebAccess restarted" emailaddress@yourdomain.com < /var/log/novell/groupwise/smtpalertwa.txt
else
echo "The GroupWise WebAccess is running"
fi

=============================================================================================

Create a script by adding the above mention information and make it "executable".

Create a file named "smtpalertwa.txt" for email notification.

Make sure to run it as a CRON job and set the interval to execute it.

Additional Information

In the process of troubleshooting this issue. One can try the following:
1. Delete the GroupWise WebAccess Agent object from the ConsoleOne.
2. Remove the GroupWise WebAccess Agent RPM.
3. Rebuild the Domain database under which GroupWise WebAccess Agent resides.
4. Reinstall the GroupWise WebAccess Agent.

If the above all fails to resolved the issue than this workaround will be of a great help.