Server Down

Back Home Up Next

horizontal rule

Home
Up

 

 

 

 

 

When Servers Go Down

Overview

Certain GroupWise processes are dependent on specific servers remaining up for their own continued fuctionality. To whit, the following are the dependencies of GW processes listed by the server on which they depend.

horizontal rule

Legend

RED = Server that was down.

GREEN = Servers needing attention when a server goes down.

BLUE = Process on server that needs attention.

horizontal rule

Click on server that was down to proceed to instructions.

DSC1      DSC2      GWSMTP      DSCGW5

horizontal rule

DSC1

Listserv: Uses EFC1 for access to the EFC1 post office. Should EFC1 fail: Reboot listserv after EFC1 has come back on line.


horizontal rule

DSC2

GWSMTP: This is the server on which GWIA (formerly SMTP)  is running.   In addition to SMTP it also runs our POP3 and IMAP gateways. It depends on DSC2 for access to the domain database. Should DSC2 fail: GWIA will lose connection to the database. Recent changes in it's configuration allow it to come back up when it can reconnect to DSC2 if the connection hasn't been broken for too long. If for some reason this doesn't appear to happen, enter "GWIA" at the console. The gateway is designed to wait a short while before completing the load. If DSC2 is up, running and visible to GWSMTP, just press ENTER to accept the default response of "Y". Otherwise, just wait and it will load in about two minutes.

GWSMTP: Restart the GroupWise 4.1 WebAccess running on GWSMTP. Type "STOPWEB" at the console prompt, wait until it shows unloading, then type "STARTWEB" at the console to restart WebAccess.

DSCGW5: Web Access 5 gateway needs to be rebooted. At the console prompt enter "STOPWEB5". When the console indicates a completed shutdown, restart the gateway by entering "STRTWEB5".

MTA: Check the MTA screen on DSC2 when all post offices and gateways have had time to come up.If one gateway doesn't appear to open it's very likely INET. To check this press F10 and choose Configuration Status. If INET is showing closed, press ESCape twice to back out then do the following out at DOS.

  1. Go to \\DSC2\SYS\DCCCD\MSLOCAL\MSHOLD\INEAF74\4
  2. Type in the following:
  3. FOR %F IN (*.*) DO MOVE %F \\DSC2\SYS\DCCCD\WPGATE\INET\WPCSIN\4
  4. This will move almost all the files from the hold directory back into the gateway directory for re-handling. You will probably get a file locked error on one or two files. Wait it out until these files are handled by MTA  and disappear. If other files show up run the above command again to move them out. 
  5. When the files are cleared, go back to the MTA screen on DSC2 and press F10.
  6. Select Configuration Status.
  7. Select INET (press ENTER.)
  8. Select Resume and Yes.
  9. ESCape three times to return to the main MTA screen.
  10. .If the MTA screen doesn't show INET opening, recheck the file system and repeat.

horizontal rule

GWSMTP

GWSTMP: If GWSMTP abends it's likely that a reboot will cause a problem with GWIA loading if GWSMTP has been down for only a short time. This is due to a file in the domain directories that is locked by GWIA. If GWSMTP won't load GWIA and displays a message indicating that 000 Process is already active you will need to unlock the file.
To unlock the file you'll need to RCONSOLE DSC2 or go to the console and use Monitor to find which connection has a lock on

\\DSC2\SYS\DCCCD\WPGATE\INET\000.PRC\PROC.

Delete that connection. It should belong to WPC. Then go back to GWSMTP and try to reload GWIA by typing "GWIA" at the console.

When GWSMTP is rebooted it should reload one module through GWIA.NCF. The AUTOEXEC.NCF is set to delay the load in order to give the server time to recognize that the domain server exists.

 

GWDSC5

DSCGW5: This is the server currently running the GroupWise 5.5 version of WebAccess. If it goes, down a simple reboot should suffice.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

horizontal rule