CustomerenvironmentHeartbeatEnabledGroupWise

From MicroFocusInternationalWiki
Jump to: navigation, search
-My other wikis


This page will serve as customer environment documentation of SLES 10 SP1 Heartbeat enabled GroupWise system.

  1. Administering Heartbeat
  2. Troubleshooting Heartbeat
  3. See word document called sles10_env_quicksheetProjectComplete.doc, which has all the IP addr, and each system and the HTTP GW Monitor URLs


The Administering Heartbeat and Troubleshooting heartbeat will have non-customer specific elements, this document will be customer specific information.


Mapping a drive so as to administer GroupWise

Currently one needs to map to the primary IP address of the server (ideally one would map to the DNS/IP addr of the resource).

  1. Find out where the resource resides - look at hb_gui (ssh into one of the nodes and type hb_gui (if you are on windows you'll want xming installed and configured).
  2. Map to x.x.80.5, .6 or .8 and then the share name
  3. To find out the share name cat /etc/samba/smb.conf for example here are the main shares:
    1. miapo
    2. doa
    3. pridom
    4. gwia
    5. restore
  4. Before clicking next on the map drive, click different user and put in gwuser and the correct password.

Chat/IM services

Starting/stoping IM services

  1. ssh into gwmail4
  2. rcnovell-nmaa stop|status|start (archive agent)
  3. rcnovell-nmma stop|status|restart (messenger agent)

Updating IM configuration

  1. /opt/novell/messenger/configure.sh

Migration notes

  1. http://wiki.novell.com/index.php/MovingIMfromNWtoLinux

IM troubleshooting

  1. netstat -na | grep 8300, if not listening then
  2. rcnovell-nmma status
  3. and or ps aux | grep mma
  4. then based on what you see, you may want to
    1. rcnovell-nmma stop
    2. kill -9 PID you saw in step 3


WebAccess

  1. See also webaccess install notes
  2. The main conf file is in /etc/apache2/conf.d/gw.conf
  3. Currently apache is configured to serve up index.html from /var/opt/novell/gw
  4. The ssl configuration is at /etc/apache2/vhost.d/vhost-email.conf
  5. webaccess can be restarted by:
    1. stop services
      1. rcapache2 stop
      2. rctomcat5 stop
      3. rcgrpwise stop
    2. start services
      1. rcapache2 start
      2. rctomcat5 start
      3. rcgrpwise start
  6. Any changes to the webaccess objects or config files will require a restart of the webaccess application and or agent.

Putting in a public certificate

  1. SSLCertificateFile /etc/apache2/ssl.crt/CAsigned.crt (public)
  2. SSLCertificateKeyFile /etc/ssl/servercerts/email.domain.com.key (Private)
  3. SSLCertificateChainFile /etc/apache2/ssl.crt/CAsigned.crt (intermediate)
    1. to update a certificate that has expired update the /etc/apache2/vhost.d/*.conf with the new 509 CAsisgned.crt and intermediate (premium intermediate certificate inter.crt)- JUST CALL VERISIGN

http://wiki.novell.com/images/c/cf/Ssl_apache2.JPG

What if the GroupWise agents won't start up

If hb_gui or commandline fail to start the agents, and we don't have any clues as to WHY they are not starting (looking in logs etc), then we need to do the following.

  1. First try the hb_gui and reload that resource or click the re-cycle button (on the group or the particular sub-resource)
  2. Second rcgrpwise status (look for the failing status, and then
    1. rcgrpwise start FAILINGREAGENT
      1. example: rcgrpwise start DOA
      2. example: rcgrpwise start DOAPRIM
      3. example: rcgrpwise start MIA.DOA
  3. Modify the GW startup file and un-remark (make active the /noconfig this way settings in the startup file will be READ, verses just what is in the database file
    1. GW Startup files
      1. /gwise/mia/groupwise/agents/share/mia.poa
      2. /gwise/gwia/groupwise/agents/share/gwiadom.mta
      3. /gwise/gwia/groupwise/agents/share/gwia.cfg
      4. /gwise/doa/groupwise/agents/share/doa.mta
      5. /gwise/pridom/groupwise/agents/share/doaprim.mta
  4. Start the agent with the --show command. (recall you must be on a linux admin machine or have xming installed and configured). WATCH the startup of the --show for clues as to WHY it is not starting.
    1. POA
      1. opt/novell/groupwise/bin/gwpoa --show @ /gwise/mia/groupwise/agent/share/mia.poa &
    2. MTA
      1. opt/novell/groupwise/agents/bin/gwmta @ /gwise/pridom/groupwise/agents/share/doaprim.mta &


GWIA

  1. config file: :/gwise/gwia/groupwise/agents/share/gwia.cfg
  2. binary: :/opt/novell/groupwise/agents/bin
  3. gw startup file looks for which GW names to use and with paths to use: etc/opt/novell/groupwise/gwha.conf

What if GWIA stops listening

    1. netstat -na | grep 25
    2. telnet ipaddress 25 (if noting then proceed with more aggressive measures)
    3. Go into the HTTP GW Monitor and try to restart it
    4. If that fails, rcgrpwise stop GWIADOM.GWIA (wait a few min.)
    5. If that fails, ps aux | grep gwia note the PID
      1. kill -9 NotedPID
    6. Then wait for heartbeat to restart it, then go into hb_gui and reload that resource.
    7. If that fails, rcgrpwise start GWIADOM.GWIA