Sdílet prostřednictvím

  • Článek

Monitoring System Health

Topic Last Modified: 2012-02-08

Perform the following checklist periodically, or as a troubleshooting measure if the system is not performing properly. If the system fails any of the checks, at least one of the server components may not be functioning properly. If everything is running, there may be a network or connectivity issue. If a component is not functioning properly, inspect its log file for errors.

  1. Check the available disk space on the database server and on all host computers. Make sure no disks are nearing capacity.
  2. Check CPU and memory usage for all host computers. For details, see Managing CPU and Memory Usage.
  3. Implement a purge strategy for those tables that Group Chat Server does not purge. For example, tblChat, will grow rapidly with a large user base and is the only table that will be exported for database upgrades; tblLogs record Active Directory sync actions; tblPurgedRoles and tblPurgedScope record purges caused by Active Directory sync actions; tblFileToken authorizes file uploads and downloads. File tokens are only valid for a minute after the upload or download has completed; tblConfig will grow very slowly and therefore is not an issue.
  4. If you are using encrypted messaging, confirm that the MTLS certificates are still valid. If they are nearing expiration, arrange to update them.

In addition, perform the following tasks as troubleshooting measures when necessary:

  1. Check the general network health. Make sure DNS is working. If you are using only the Group Chat client in the system, check that port 80 is open and accessible.
  2. Check the permissions for the database user. Make sure the account used to run the service has the necessary permissions for updating the database.
  3. Run the Group Chat client and sign in to an account. Make sure the channels load properly, and that chat history loads for all logged chat rooms.
  4. If you are experiencing trouble transferring files, monitor the Web service for Stopped status using Internet Information Services (IIS) Manager.
  5. If there is unusual behavior related to IM, such as an IM channel the user has accessed not showing up in an Open IM Channel search, verify that all servers, including the Office Communications Server, are running.