|
Problem IT41016
|
Status: Closed |
DEFINING DBSERVERNAME TO CREATE MULTIPLE LISTENER THREADS IS THROWING ASSERT WARNING
|
| product: |
INFORMIX SERVER / 5725A3900 / E10 - |
| Problem description: |
When DBSERVENAME is defined like this:
DBSERVERNAME my_tcp-4
my_tcp onscptcp machine 1234
you get Assert Warning during startup
13:42:03 Assert Warning: Unable to bind to the port (1234) on
the host (10.11.12.13) for the server (my_tcp).
13:42:03 IBM Informix Dynamic Server Version 14.10.FC8
13:42:03 Who: Session(8, informix@, 0, (nil))
Thread(13, soctcplst, 0, 1)
File: soc_be.c Line: 2500
13:42:04 listener-thread@soc_be.c:2348: err = -25572: oserr =
2: errstr = : Network driver cannot bind a name to the port.
System error = 2.
13:42:04 sql_listener: ASF_LISTEN failed
13:42:04 Attempting to bring listener thread down.
And listener threads are not started |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server 14.10.xC8. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 14.10.xC9. *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server 14.10.xC8. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 14.10.xC9. *
**************************************************************** |
| Comment |
Fixed in Informix Server 14.10.xC9. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 24.05.2022
26.09.2022
26.09.2022 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
