14.0 Monitor Agent and Application Error Messages
GWMON: GroupWise Monitor Agent is not listening
Source:
GroupWise Monitor Application.
Possible Cause:
The Monitor Agent is not running.
Possible Cause:
The Monitor Agent is listening on a different port than the one the Monitor Application is using to communicate with it.
Action:
Check the gwmonitor.cfg file to make sure it provides the correct IP address and port number for the Monitor Agent. Correct the information as needed.
GWMON: No route to GroupWise Monitor Agent
Source:
GroupWise Monitor Application.
Possible Cause:
Your firewall is preventing the Monitor Application from communicating with the Monitor Agent.
Action:
Adjust the configuration of your firewall to accommodate communication between the Monitor Application and the Monitor Agent.
Possible Cause:
A router between the Monitor Application and the Monitor Agent is down.
Action:
Resolve any network problems that are preventing GroupWise Monitor from functioning.
GWMON: Path to domain database (/home) is invalid or blocked
Source:
GroupWise Monitor Agent.
Explanation:
The Monitor Agent cannot access the domain database (wpdomain.db) in the directory specified by the /home switch.
Possible Cause:
The location specified by the /home startup switch does not exist.
Possible Cause:
The location specified by the /home startup switch is on a server that is currently not available.
Action:
Check the status of the server where the specified directory is located. Wait for the server to come back up or contact the administrator of that server.
Possible Cause:
The location might be on a server that is not currently mapped.
Action:
Make sure the server where the Monitor Agent is running has a drive mapped to the domain directory on the server where the domain is located if it is using a mapped link.
GWMON: Request timed out waiting for response from GroupWise Monitor Agent
Source:
GroupWise Monitor Application.
Explanation:
The Monitor Application has been able to communicate successfully with the Monitor Agent, but the Monitor Agent has stopped responding.
Possible Cause:
The server where the Monitor Agent is running has gone down.
Action:
Resolve any network problems that are preventing GroupWise Monitor from functioning.
Possible Cause:
The server where the Monitor Agent is running is overburdened or has insufficient system resources available, so that the Monitor Agent cannot respond to the Monitor Application in a timely manner.
Possible Cause:
The Monitor Agent has gone down.
GWMON: The URL to connect to the GroupWise Monitor Agent is invalid
Source:
GroupWise Monitor Application.
Possible Cause:
The Monitor Agent IP address and port number is not correct in the gwmonitor.cfg file.
Action:
Check the gwmonitor.cfg file to make sure it provides the correct IP address and port number for the Monitor Agent. Correct the information as needed.
GWMON: Unable to communicate with GroupWise Monitor Agent
Source:
GroupWise Monitor Application.
Possible Cause:
The Monitor Agent is not running.
Possible Cause:
The server where the Monitor Agent is running has gone down.
Possible Cause:
A router between the Monitor Application and the Monitor Agent is down.
Action:
Resolve any network problems that are preventing GroupWise Monitor from functioning.
Possible Cause:
Your firewall is preventing the Monitor Application from communicating with the Monitor Agent.
Action:
Adjust the configuration of your firewall to accommodate communication between the Monitor Application and the Monitor Agent.
GWMON: Unable to connect to the MTA at IP_address:port
Source:
GroupWise Monitor Agent.
Explanation:
The Monitor Agent cannot connect to the MTA at the IP address and port you specified when prompted.
Action:
Double-check the IP address and port number of the MTA that you want the Monitor Agent to communicate with.
GWMON: Unable to resolve GroupWise Monitor Agent’s host name to a valid IP address
Source:
GroupWise Monitor Application.
Possible Cause:
The Monitor Agent host name is not correct in the gwmonitor.cfg file.
Action:
Check the gwmonitor.cfg file to make sure it provides the correct IP address and port number for the Monitor Agent. Correct the information as needed.