English

How To: Interpret ArcGIS Server 9.2 (Solaris/Linux) Diagnostic test results

Summary

Instructions provided describe how to interpret the ArcGIS Server 9.2(Solaris/Linux) Diagnostic test results. The Diagnostic test is run through the Server_diag_tool script located in the $AGSHOME/scripts directory.

Note:
$AGSHOME refers to the ArcGIS Server installation directory
The diagnostic check provides valuable information on the state of ArcGIS Server and is recommended to be run in the following situations:
  • ArcGIS Server fails to start or is not functioning as expected.
  • Unable to log in to the ArcGIS Server Manager.
  • Unable to connect to the ArcGIS Server from ArcCatalog.
With the ArcGIS Server 9.2 release, ArcGIS Server diagnostic can be run on a Solaris/Linux machine installed with Server Object Manager (SOM) and Server Object Container (SOC) by running the script 'Server_diag_tool' from a terminal. This script should be run as the install owner of ArcGIS Server.
Note:
At 9.2 release, the diagnostic script cannot be run on a SOC only machine.

Procedure

This section provides information and explains the checks performed by the diagnostic tool.
 

CodeDefinition
check /etc/hosts: has entry for localhostThe /etc/hosts file should contain an entry for the localhost. If this entry does not exist, the check fails.
check /etc/hosts: localhost = 127.0.0.1This verifies if the loopback IP address for localhost is set to 127.0.0.1. An example is as follows: 127.0.0.1 localhost
check /etc/hosts: has entry for hostname (hostname)This verifies if the /etc/hosts file has an entry for the ArcGIS Server host name.
check /etc/hosts: hostname != 127.0.0.1This fails if the IP address for the host name is set to the loopback address. It is required that the host name entry in the /etc/hosts file has a valid IP address. For example:
check /etc/passwd: user agsadminThis verifies if the /etc/passwd file contains an entry for the user 'agsadmin'. This Operating System (OS) user is created by the ArcGIS Server setup at the time of install.
check /etc/passwd: user agsuserThis verifies if the /etc/passwd file contains an entry for the user 'agsuser'. This OS user is created by the ArcGIS Server setup at the time of install.
check permissions of <install location>The ArcGIS install directory should have at least 744 privilege (drwxr--r--) for the ArcGIS Server owner.
Note:
The required privilege is only 711 (drwx--x--x) and not 744. It is a bug in the ArcGIS Server 9.2 diagnostic tool that it checks for 744 privilege (drwxr--r--).
check <install location>: has spaceThis verifies if the disk space usage for the ArcGIS Server install directory is not 100%.
check /tmp : folder existsThe /tmp directory is used periodically to store temporary files. This check validates the presence of this directory.
check /tmp : is writableThis verifies if the user that owns ArcGIS Server has write permissions to the /tmp directory.
check /tmp : has spaceThis verifies if the disk space usage for /tmp is not 100%.
check check <path to Server Directory 1..N>The diagnostic tool obtains the list of all server directories from <install location>/server/system/Server.dat and validates the existence of each directory. 
Example:

check <install location>/server/serverdir/arcgisoutput
check <install location>/server/serverdir/arcgisjobs
check <install location>/server/serverdir/arcgiscache
check Core Service Status : RunningThis verifies if the Core Services are running. The Core Services form the interoperability layer for the ArcGIS Server, and their role is critical to the functioning of the ArcGIS Server. 
check RPC PortThis verifies if the Core Services are using a fixed port 135 for Remote Procedure Calls (RPC). 
check Registry for ESRI\ArcServerThis verifies that the Registry used by the ArcGIS Server contains the necessary entries for the location and type of installation. These entries are created by the Setup program. 
check Security TypeThis verifies if the security authentication type for the Core Services is set correctly. 
check Security DomainThis verifies if the Domain name used by the Core Service security mechanism is the same as the host name. 
check Security DomainServerThis verifies if the DomainServer name used by the Core Service security mechanism is the same as the host name. Both Domain name and Domain server specify the host where the Identity Server, for the ArcGIS Server, is running.
check process: remotesaThis verifies if the 'Identity Server' process (remotesa) is running. Identity Server provides authentication services for the ArcGIS Server. 
check process: slapdThis verifies if the Directory Server process (ns-slapd) is running. Directory Server is a repository for storing ArcGIS Server user accounts. 
check process: mwrpcssThis verifies if the process mwrpcss, which represents the RPC Server, is running. The ArcGIS Server framework is built upon the distributed component object (DCOM) technology that supports distribution of component object model (COM) objects across different machines and communication between them. The mwrpcss process provides this support on Solaris and Linux.
check process: regssThis verifies if the process regss, which represents the Registry Service is running. The Registry Service is responsible for managing the registry data used by Core Services.
check process: watchdogThis verifies if the process watchdog is running. Watchdog is part of the Core Services and is responsible for keeping mwrpcss and regss processes alive. If mwrpcss and/or regss processes terminate unexpectedly the watchdog starts them again immediately.
check process: arcsom.exeThis verifies if the Server Object Manager (SOM) is running.
check process: java -jar arcgis_manager as <ArcGIS Server install owner>This verifies if the ArcGIS Server Manager is running as the ArcGIS Server install owner. 
check process: arcgis/java/manager/service/tomcat as <ArcGIS Server install owner>This verifies if the Tomcat server which hosts the deployed Web applications and Web services is running as the ArcGIS Server install owner.
check if LDAP server is runningThis is an additional check for Directory Server to verify if it is listening on the port (MWR_LDAPPORT) as specified in the /etc/remotesa/remotesa.config file. This port is 62000 by default.
check arcsom.exe permissionsThis verifies if the Server Object Manager executable (<install location>/bin/arcsom.exe) has been given Read, Write and Set-UserID (setuid) access rights. 
check arcsoc.exe permissionsThis verifies if the Server Object Container executable (<install location>/bin/arcsoc.exe) has been given Read, Write and Set-UserID (setuid) access rights.
check User MappingsThis verifies if the ArcGIS Server install owner has at least Read and Write access to the user map file in the following location: <install location>/servercore/.Server/.arcgis_usermap
check if the Server <SOC host name> is reachableThe diagnostic tool obtains the list of all Server Machines (SOCs) from <install location>/server/system/Server.dat and verifies if each Server Machine is reachable. 
check if SOC is running on <SOC host name>The diagnostic tool obtains the list of all Server Machines (SOCs) from <install location>/server/system/Server.dat and verifies if the ArcGIS Server on each of those machines is alive and listening on Port 135.
check if port 8399 is listeningThis verifies if the internal Tomcat server, which hosts the deployed Web applications and Web services, is listening on port 8399.
check if port 8309 is listeningThis verifies if the AJP/1.3 Connector is listening on port 8309. 
check if port 8099 is listeningThis verifies if the internal Tomcat server which hosts the ArcGIS Server Manager is listening on port 8099.
check if port 8109 is listeningThis verifies if the AJP/1.3 Connector is listening for ArcGIS Server Manager requests on port 8109.
 

Related Information