GWHA - argh! Can't get it to work!

[hurlburj]

I don't know if you ever got this working, but I had a hell of a time, too. If you want to change the polling rate, you have to change it on the monitor servlet web page, not the agent web page. Why? Just because. Try changing it here:

http://servername/gwmon/gwmonitor

Secondly, make sure that you have port 8400 open on the box you want to restart the agent from. You can test it by telnet from your monitor server:

telnet <target server> 8400

You should see a prompt for a username and password. If you get that far, then the gwha agent should be able to restart your services.

You also need to check and make sure your target server can talk to your monitor server.


Hope that helps.

I swear, if gwha had a neck I'd choke it. I'm so frustrated that I can't get this service to function. I'm pretty sure everything's configured correctly, but if I stop an agent it never gets restarted by gwha.

Server: OES2, fully patched. GroupWise 7.0.3 - installed components on this server are MTA, GWIA, 1 PO, WebAccess Agent, Monitor, gwha, Mesenger agents. WebAccess App is on a separate front-end server.

All agents loading correctly. Can access monitor via http://server:8200.
-----------------------------------------------
/etc/xinetd.d/gwha:

service gwha
{
socket_type = stream
protocol = tcp
wait = no
user = root
server = /opt/novell/groupwise/agents/bin/gwha
instances = 1
type = UNLISTED
port = 8400
disabled = no
}
---------------------------------------
/etc/opt/novell/groupwise/gwha.conf:

[gwha]
ssl = yes
key = /opt/novell/messenger/certs/mailSSL.key
cert = /opt/novell/messenger/certs/mailSSL.b64
password = <password>

*note: This is the same certificate used for Messenger, which is working correctly so the cert info/password must be good.

-----------------------------------------
/etc/init.d/grpwise-ma:
MA_CONFIG=/opt/novell/groupwise/agents/share/monitor.xml
MA_BIN=/opt/novell/groupwise/agents/bin/gwmon

MA_OPTIONS="--hauser gwhauser --hapassword <password> --hapoll 15"

* Using the same password as the cert - would this cause a problem?
--------------------------------------------------------------------------
It is loading via xinetd - at least I think it is, it's showing as an active process with ps. One weird thing is that even though I'm setting the polling for monitor to 15 seconds, when viewing via the web it doesn't actually show a dead agent for 5 minutes. I see in preferences there is a poll cycle setting configured for 300 seconds, but if I change it and save it always stays at 300.

So after configuring everything and rebooting the server for good measure, I stop the PO and keep checking status. I've let it run for well beyond 5 mins and it never starts back up. What am I missing??!!