Problem: On our HP-UX machine we are getting error 239 entries in our interbase.log file when starting InterBase by using the IBMGR utility. What does error 239 mean? Solution: The error is ECONNREFUSED, and is documented in the /usr/include/sys/errno.h file. On Solaris, SCO Open Server and other UNIX OS's the error number will be different. The error messages relate to the sequence of events that occur when IBMGR starts InterBase. The sequence of event is: 1. Start the IBGuardian process 2. Wait a period of time 3. Repeatedly attempt to connect until success or a timeout value is reached If the IBMGR utility attempts to connect before the InterBase server begins listening for connections, then the tcp/ip stack will return an ECONNREFUSED error. The IBMGR utility in turn writes this error entry in the interbase.log file. As long as there is a successful connection and IBMGR says that InterBase was successfully started then all is well. The entry in the interbase.log file can be looked at as a side-effect of the IBMGR startup process. Are these log file entries a bug? It depends on how one looks at the situation. The connection attempt is used as part of the steps to determine if the IBServer process is correctly listening for connections. If the connect attempt happens too soon the tcp/ip error of ECONNREFUSED is returned by the tcp/ip stack. What is the proper decision to make regarding this error? Do we throw the error message away or write it to a log? What about other tcp/ip errors?
Last Modified: 20-OCT-00