Check the Name Server on UNIX
The Name server process (iigcn) is not running if either of the following occurs:
• You receive a specific error indicating that the Name server process (iigcn) failed to start.
• The command ps -aux (BSD) or ps -ef (System V) shows that the iigcn is not running.
You can verify the status of the Name server by attempting to start the Name server manually using the ingstart -iigcn command.
To check the Name server
1. Verify the installation environment by performing the installation checks on Unix as documented in the Ingres System Administrator Guide before attempting to start the Name server. An improper installation environment will cause the Name server to fail to start.
2. Verify that the operating system and TCP/IP versions are correct for your release before continuing with the following additional checks. Use of the wrong version or improper installation of TCP/IP can cause the Name server to fail to start.
Additional checks
1. Verify that TCP/IP is properly installed by typing the following command at the operating system prompt:
telnet localhost
You should get a loopback login to your machine.
2. Verify that your operating system's required TCP daemon process is running.
The specific process name is system-dependent, but on many UNIX systems the process is named "inetd" (use your process name in the command if it is not inetd). Enter the following command at the operating system prompt, or see your operating system manual for your particular TCP/IP implementation:
BSD:
ps -aux | grep inetd
System V:
ps -ef | grep inetd
3. Check that the environment variable II_GCNxx_PORT is not set (this environment variable contains the TCP port identifier of the Name server process):
a. Use the ingprenv utility to verify that this environment variable is not set when the Name server tries to start up.
b. If necessary, use the ingunset command to unset the II_GCNxx_PORT environment variable.
4. If you are still having problems, set the following trace to capture additional diagnostic data before calling Technical Support:
Bourne shell:
II_GC_TRACE=5
II_GC_LOG=stdio (stdio or filename)
export II_GC_TRACE II_GC_LOG
C shell:
setenv II_GC_TRACE 5
setenv II_GC_LOG stdio (stdio or filename)
ingstart -iigcn
5. If you corrected a Name server problem, verify that Enterprise Access will now start as usual:
a. Shut down the partially-started installation with the ingstop command.
b. Restart the installation with the ingstart command.
Last modified date: 08/22/2022