Name Server Errors on Linux
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 this by attempting to start the Name Server manually.
Check for Name Server Errors on Linux
If the Name Server does not start, follow these steps:
1. Verify that TCP/IP is properly installed by typing the following command at the operating system prompt:
telnet localhost
A loopback login to your machine occurs.
2. Verify that the required TCP daemon process for your operating system is running.
The specific process name is system dependent, but on many Linux systems, the process is named “inetd” (use your process name in the command below if it is not inetd). Issue the following command at the operating system prompt, or see your operating system manual for your particular TCP/IP implementation:
BSD:
ps -aux | grop inetd
System V:
ps -ef | grep inetd
3. Check that the Actian X 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 corrected a Name Server problem, verify that Actian X starts normally:
a. Shut down the partially started installation with the ingstop command.
b. Restart the installation with the ingstart command.
5. If you are still having problems, set the following trace to capture additional diagnostic data before calling technical support:
II_GC_TRACE=5
II_GC_LOG = stdio (stdio or filename); export II_GC_TRACE II_GC_LOG
Last modified date: 11/09/2022