-25572 Network driver cannot bind a name to the port.
Hi,
I am getting following error message
"-25572 Network driver cannot bind a name to the port."
Please find the contain of INFORMIX environment variables, sqlhosts,
services and onconfig file.
INFORMIX environment variables
INFORMIXDIR=/usr/informix/9.40.UC1
INFORMIXSERVER=kam940q1
ONCONFIG=onconfig.kam940q1
SQLHOSTS
kam940q1 ontlitcp kamal shailesh
kamxpsq1.1 onipcshm kamal infsrv2
SERVICES
shailesh 8000/tcp # Informix database client
connection
#infsrv0 8000/tcp # Informix database client
connection
infsrv2 7206/tcp # Informix database client
connection
infsrv6 7201/tcp # Informix database client
connection
infsrv7 7202/tcp # Informix database client
connection
infsrv8 7203/tcp # Informix database client
connection
infsrv9 7204/tcp # Informix database client
connection
infsrv13 7266/tcp # Informix database client
connection
infsrv14 7267/tcp # Informix database client
connection
onconfig.kam940q1
# Root Dbspace Configuration
ROOTNAME rootdbs # Root dbspace name
ROOTPATH /usr/informix/databases/kam940q1/datafiles/root.dbf
ROOTOFFSET 0 # Offset of root dbspace into device
(Kbytes)
ROOTSIZE 35000 # Size of root dbspace (Kbytes) 9/96:changed from20000
# 1/7/97: changed from 22500 to 25000
# Disk Mirroring Configuration Parameters
MIRROR 0 # Mirroring flag (Yes = 1, No = 0)
# Path for device containing mirrored root
# MIRRORPATH /usr/informix/databases/kam940q1/mirrorfiles/mirror.dbf
MIRROROFFSET 0 # Offset into mirrored device (Kbytes)
# Physical Log Configuration
PHYSDBS rootdbs # Location (dbspace) of physical log
PHYSFILE 2000 # Physical log file size (Kbytes)# Logical Log Configuration
LOGFILES 6 # Number of logical log files
LOGSIZE 1000 # Logical log size (Kbytes)
# Diagnostics
# System message log file path
MSGPATH /usr/informix/databases/kam940q1/logfiles/online.log
CONSOLE /usr/informix/databases/kam940q1/logfiles/console.log
ALARMPROGRAM # Alarm program path
# System Archive Tape Device
TAPEDEV /usr/informix/databases/kam940q1/logfiles/tape # Tape
device path
TAPEBLK 32 # Tape block size (Kbytes)
TAPESIZE 1024000 # Maximum amount of data to put on tape
(Kbytes)
# Log Archive Tape Device
LTAPEDEV /usr/informix/databases/kam940q1/logfiles/ltape # Log tape
device path
LTAPEBLK 32 # Log tape block size (Kbytes)
LTAPESIZE 1024000 # Max amount of data to put on log tape
(Kbytes)
# Optical
STAGEBLOB # INFORMIX-OnLine/Optical staging area
# System Configuration
SERVERNUM 1 # Unique id corresponding to a OnLineinstance
DBSERVERNAME kam940q1 # Name of default database server
DBSERVERALIASES # List of alternate dbservernames
DEADLOCK_TIMEOUT 60 # Max time to wait of lock in distributed
env.
RESIDENT 0 # Forced residency flag (Yes = 1, No = 0)
MULTIPROCESSOR 0 # 0 for single-processor, 1 formulti-processor
NUMCPUVPS 1 # Number of user (cpu) vps
SINGLE_CPU_VP 1 # If non-zero, limit number of cpu vps toone
NOAGE 0 # Process aging
AFF_SPROC 0 # Affinity start processor
AFF_NPROCS 0 # Affinity number of processors
# Shared Memory Parameters
LOCKS 5000 # Maximum number of locks
BUFFERS 200 # Maximum number of shared buffers
NUMAIOVPS 2 # Number of IO vps
PHYSBUFF 32 # Physical log buffer size (Kbytes)
LOGBUFF 32 # Logical log buffer size (Kbytes)LOGSMAX 6 # Maximum number of logical log files
CLEANERS 1 # Number of buffer cleaner processes
SHMBASE 0x0A000000L # Shared memory base address
NETTYPE ipcshm,1,20,CPU # Override sqlhosts defaults# NETTYPE tlitcp,1,20,NET # Override sqlhosts defaults
SHMVIRTSIZE 8000 # initial virtual shared memory segment size
SHMADD 8192 # Size of new shared memory segments
(Kbytes)
SHMTOTAL 0 # Total shared memory (Kbytes). 0=>unlimited
CKPTINTVL 300 # Check point interval (in sec)
LRUS 8 # Number of LRU queues
LRU_MAX_DIRTY 60 # LRU percent dirty begin cleaning limit
LRU_MIN_DIRTY 50 # LRU percent dirty end cleaning limit
LTXHWM 50 # Long transaction high water markpercentage
LTXEHWM 60 # Long transaction high water mark
(exclusive)
TXTIMEOUT 300 # Transaction timeout (in sec)
STACKSIZE 32 # Stack size (Kbytes)
# System Page Size
# BUFFSIZE - OnLine no longer supports this configuration parameter.
# To determine the page size used by OnLine on your platform
# see the last line of output from the command, 'onstat -b'.nate
dbservernames
# Recovery Variables
# OFF_RECVRY_THREADS:
# Number of parallel worker threads during fast recovery or an offline
restore.
# ON_RECVRY_THREADS:
# Number of parallel worker threads during an online restore.
OFF_RECVRY_THREADS 10 # Default number of offline worker threads
ON_RECVRY_THREADS 1 # Default number of online worker threads
# Data Replication Variables
# DRAUTO: 0 manual, 1 retain type, 2 reverse type
DRAUTO 0 # DR automatic switchover
DRINTERVAL 30 # DR max time between DR buffer flushes (in
sec)
DRTIMEOUT 30 # DR network timeout (in sec)# DR lost+found file path
DRLOSTFOUND /usr/informix/databases/kam940q1/logfiles/dr.lostfound
# Read Ahead Variables
RA_PAGES # Number of pages to attempt to read ahead
RA_THRESHOLD # Number of pages left before next group
# CDR Variables
CDR_EVALTHREADS 1,2 # evaluator threads (per-cpu-vp,additional)
CDR_DSLOCKWAIT 5 # DS lockwait timeout (seconds)
CDR_QUEUEMEM 4096 # Maximum amount of memory for any CDR queue
(Kbytes)
CDR_NIFCOMPRESS 0 # Link level compression (-1 never, 0 none,
9 max)
# Backup/Restore variables
BAR_ACT_LOG /usr/informix/9.40.UC1/bar_act.log
BAR_MAX_BACKUP 0
BAR_RETRY 1
BAR_DEBUG 9
BAR_DEBUG_LOG /usr/informix/9.40.UC1/bar_debug.log
BAR_NB_XPORT_COUNT 10
BAR_XFER_BUF_SIZE 31
BAR_PROGRESS_FREQ 0
BAR_BSALIB_PATH /usr/informix/9.40.UC1/lib/libbsa.so
# DBSPACETEMP:
# OnLine equivalent of DBTEMP for SE. This is the list of dbspaces
# that the OnLine SQL Engine will use to create temp tables etc.
# If specified it must be a colon separated list of dbspaces that exist
# when the OnLine system is brought online. If not specified, or if
# all dbspaces specified are invalid, various ad hoc queries will create
# temporary files in /tmp instead.
# Default temp dbspaces
DBSPACETEMP tempdbs1
# DUMP*:
# The following parameters control the type of diagnostics information which
# is preserved when an unanticipated error condition (assertion failure)
occurs
# during OnLine operations.
# For DUMPSHMEM, DUMPGCORE and DUMPCORE 1 means Yes, 0 means No.
DUMPDIR /usr/informix/databases/kam940q1/dumpfiles # Preserve diagnostics in
this directory
DUMPSHMEM 1 # Dump a copy of shared memory
DUMPGCORE 0 # Dump a core image using 'gcore'
DUMPCORE 0 # Dump a core image (Warning:this aborts
OnLine)
DUMPCNT 1 # Number of shared memory or gcore dumps for# a single user's session
# ADT*
# The following parameters control the type and level of secure auditing
# present in the OnLine system. By default, ADTMODE is 0 and auditing
# is disabled
More,
Shailesh wrote:
you have DBSERVERNAME = kam940q1 and NETTYPE = ipcshm,1,20,CPUin you
onconfig file.
But for this combinations there is no entry in sqlhosts.
You'll have to switch either
DBSERVERNAME to kamxpsq1.1 to use the second entry
or NETTYPE to tlitcp,1,20,NET to use the first entry out of sqlhosts.
>Hi,
>
>I am getting following error message
>
>"-25572 Network driver cannot bind a name to the port."
>
>Please find the contain of INFORMIX environment variables, sqlhosts,
>services and onconfig file.
>
>INFORMIX environment variables
>INFORMIXDIR=/usr/informix/9.40.UC1
>INFORMIXSERVER=kam940q1
>ONCONFIG=onconfig.kam940q1>
>SQLHOSTS
>kam940q1 ontlitcp kamal shailesh
>kamxpsq1.1 onipcshm kamal infsrv2>
>SERVICES
>shailesh 8000/tcp # Informix database client
>connection
>#infsrv0 8000/tcp # Informix database client
>connection
>infsrv2 7206/tcp # Informix database client
>connection
>infsrv6 7201/tcp # Informix database client
>connection
>infsrv7 7202/tcp # Informix database client
>connection
>infsrv8 7203/tcp # Informix database client
>connection
>infsrv9 7204/tcp # Informix database client
>connection
>infsrv13 7266/tcp # Informix database client
>connection
>infsrv14 7267/tcp # Informix database client
>connection
>
>
>
>onconfig.kam940q1
># Root Dbspace Configuration
>
>ROOTNAME rootdbs # Root dbspace name
>ROOTPATH /usr/informix/databases/kam940q1/datafiles/root.dbf
>ROOTOFFSET 0 # Offset of root dbspace into device
>(Kbytes)
>ROOTSIZE 35000 # Size of root dbspace (Kbytes) 9/96:changed from>20000
> # 1/7/97: changed from 22500 to 25000
>
># Disk Mirroring Configuration Parameters
>
>MIRROR 0 # Mirroring flag (Yes = 1, No = 0)
># Path for device containing mirrored root
># MIRRORPATH /usr/informix/databases/kam940q1/mirrorfiles/mirror.dbf
>MIRROROFFSET 0 # Offset into mirrored device (Kbytes)>
># Physical Log Configuration
>
>PHYSDBS rootdbs # Location (dbspace) of physical log
>PHYSFILE 2000 # Physical log file size (Kbytes)># Logical Log Configuration
>
>LOGFILES 6 # Number of logical log files
>LOGSIZE 1000 # Logical log size (Kbytes)>
># Diagnostics
>
># System message log file path
>MSGPATH /usr/informix/databases/kam940q1/logfiles/online.log
>CONSOLE /usr/informix/databases/kam940q1/logfiles/console.log
>ALARMPROGRAM # Alarm program path>
># System Archive Tape Device
>
>TAPEDEV /usr/informix/databases/kam940q1/logfiles/tape # Tape
>device path
>TAPEBLK 32 # Tape block size (Kbytes)
>TAPESIZE 1024000 # Maximum amount of data to put on tape
>(Kbytes)>
># Log Archive Tape Device
>
>LTAPEDEV /usr/informix/databases/kam940q1/logfiles/ltape # Log tape
>device path
>LTAPEBLK 32 # Log tape block size (Kbytes)
>LTAPESIZE 1024000 # Max amount of data to put on log tape
>(Kbytes)>
># Optical
>
>STAGEBLOB # INFORMIX-OnLine/Optical staging area
>
># System Configuration
>
>SERVERNUM 1 # Unique id corresponding to a OnLine>instance
>DBSERVERNAME kam940q1 # Name of default database server
>DBSERVERALIASES # List of alternate dbservernames
>DEADLOCK_TIMEOUT 60 # Max time to wait of lock in distributed
>env.
>RESIDENT 0 # Forced residency flag (Yes = 1, No = 0)
>
>MULTIPROCESSOR 0 # 0 for single-processor, 1 for>multi-processor
>NUMCPUVPS 1 # Number of user (cpu) vps
>SINGLE_CPU_VP 1 # If non-zero, limit number of cpu vps to>one
>
>NOAGE 0 # Process aging
>AFF_SPROC 0 # Affinity start processor
>AFF_NPROCS 0 # Affinity number of processors>
># Shared Memory Parameters
>
>LOCKS 5000 # Maximum number of locks
>BUFFERS 200 # Maximum number of shared buffers
>NUMAIOVPS 2 # Number of IO vps
>PHYSBUFF 32 # Physical log buffer size (Kbytes)
>LOGBUFF 32 # Logical log buffer size (Kbytes)>LOGSMAX 6 # Maximum number of logical log files
>CLEANERS 1 # Number of buffer cleaner processes
>SHMBASE 0x0A000000L # Shared memory base address
>NETTYPE ipcshm,1,20,CPU # Override sqlhosts defaults># NETTYPE tlitcp,1,20,NET # Override sqlhosts defaults
>SHMVIRTSIZE 8000 # initial virtual shared memory segment size
>SHMADD 8192 # Size of new shared memory segments
>(Kbytes)
>SHMTOTAL 0 # Total shared memory (Kbytes). 0=>unlimited
>CKPTINTVL 300 # Check point interval (in sec)
>LRUS 8 # Number of LRU queues
>LRU_MAX_DIRTY 60 # LRU percent dirty begin cleaning limit
>LRU_MIN_DIRTY 50 # LRU percent dirty end cleaning limit
>LTXHWM 50 # Long transaction high water mark>percentage
>LTXEHWM 60 # Long transaction high water mark
>(exclusive)
>TXTIMEOUT 300 # Transaction timeout (in sec)
>STACKSIZE 32 # Stack size (Kbytes)>
># System Page Size
># BUFFSIZE - OnLine no longer supports this configuration parameter.
># To determine the page size used by OnLine on your platform
># see the last line of output from the command, 'onstat -b'.nate
>dbservernames
>
>
># Recovery Variables
># OFF_RECVRY_THREADS:
># Number of parallel worker threads during fast recovery or an offline
>restore.
># ON_RECVRY_THREADS:
># Number of parallel worker threads during an online restore.
>
>OFF_RECVRY_THREADS 10 # Default number of offline worker threads
>ON_RECVRY_THREADS 1 # Default number of online worker threads>
># Data Replication Variables
># DRAUTO: 0 manual, 1 retain type, 2 reverse type
>DRAUTO 0 # DR automatic switchover
>DRINTERVAL 30 # DR max time between DR buffer flushes (in
>sec)
>DRTIMEOUT 30 # DR network timeout (in sec)># DR lost+found file path
>DRLOSTFOUND /usr/informix/databases/kam940q1/logfiles/dr.lostfound
>
># Read Ahead Variables
>RA_PAGES # Number of pages to attempt to read ahead
>RA_THRESHOLD # Number of pages left before next group>
># CDR Variables
>CDR_EVALTHREADS 1,2 # evaluator threads (per-cpu-vp,additional)
>CDR_DSLOCKWAIT 5 # DS lockwait timeout (seconds)
>CDR_QUEUEMEM 4096 # Maximum amount of memory for any CDR queue
>(Kbytes)
>CDR_NIFCOMPRESS 0 # Link level compression (-1 never, 0 none,
>9 max)>
># Backup/Restore variables
>BAR_ACT_LOG /usr/informix/9.40.UC1/bar_act.log
>BAR_MAX_BACKUP 0
>BAR_RETRY 1
>BAR_DEBUG 9
>BAR_DEBUG_LOG /usr/informix/9.40.UC1/bar_debug.log
>BAR_NB_XPORT_COUNT 10
>BAR_XFER_BUF_SIZE 31
>BAR_PROGRESS_FREQ 0
>BAR_BSALIB_PATH /usr/informix/9.40.UC1/lib/libbsa.so>
>
># DBSPACETEMP:
># OnLine equivalent of DBTEMP for SE. This is the list of dbspaces
># that the OnLine SQL Engine will use to create temp tables etc.
># If specified it must be a colon separated list of dbspaces that exist
># when the OnLine system is brought online. If not specified, or if
># all dbspaces specified are invalid, various ad hoc queries will create
># temporary files in /tmp instead.
>
># Default temp dbspaces
>DBSPACETEMP tempdbs1>
># DUMP*:
># The following parameters control the type of diagnostics information which
># is preserved when an unanticipated error condition (assertion failure)
>occurs
># during OnLine operations.
># For DUMPSHMEM, DUMPGCORE and DUMPC
Hi,
is this a message that you get from the listener thread,
right away upon startup of the server ?
Or is this a message that you get when trying the first connect
to the running server (assuming that it runs properly) ?
Or does this message appear sometime upon a connection
attempt while there are already established sessions (and
those users can work with the database) ?
If the server is running (i.e. got past startup), then you
can do "onstat -g ntu" to check that there is a listener thread
listening with the correct protocol.
You can put a comment before the remaining NETTYPE
parameter in your onconfig file. This NETTYPE is for ipcshm,
but you've a server name configured only for tlitcp, so this
NETTYPE parameter is not helpful (there are versions known
to do funny things in this situation).
Are you sure that protocol tlitcp is supported on your platform ?
Check the machine specific notes
( in $INFORMIXDIR/release/en_us/0333/... ) to find out.
Run "netstat -an" system utility to find out if the port 8000
you want to use is "occupied" by someone else. In that case
use a different (unique) portnumber.
Make sure that the server has enough resources, especially
concurrently open file descriptors, because each TCP/IP
connection requires one of those (in addition to those for
all the chunks, message file, etc.).
You may have observed that others diligently provide
the exact IDS version number (e.g. 9.40.UC2) and platform
information when asking questions. As you can see, this
often makes sense, because there are quite a few things
that can depend on this ...
Regards,
Martin
--
Martin Fuerderer
IBM Informix Development Munich, Germany
Information Management
forum.subscriber@iiug.org wrote on 21.01.2005 06:13:46:
>
> Hi,
>
> I am getting following error message
>
> "-25572 Network driver cannot bind a name to the port."
>
> Please find the contain of INFORMIX environment variables, sqlhosts,
> services and onconfig file.
>
> INFORMIX environment variables
> INFORMIXDIR=/usr/informix/9.40.UC1
> INFORMIXSERVER=kam940q1
> ONCONFIG=onconfig.kam940q1>
> SQLHOSTS
> kam940q1 ontlitcp kamal shailesh
> kamxpsq1.1 onipcshm kamal infsrv2>
> SERVICES
> shailesh 8000/tcp # Informix database
client
> connection
> #infsrv0 8000/tcp # Informix database
client
> connection
> infsrv2 7206/tcp # Informix database client
> connection
> infsrv6 7201/tcp # Informix database client
> connection
> infsrv7 7202/tcp # Informix database client
> connection
> infsrv8 7203/tcp # Informix database client
> connection
> infsrv9 7204/tcp # Informix database client
> connection
> infsrv13 7266/tcp # Informix database client
> connection
> infsrv14 7267/tcp # Informix database client
> connection
>
>
>
> onconfig.kam940q1
> # Root Dbspace Configuration
>
> ROOTNAME rootdbs # Root dbspace name
> ROOTPATH /usr/informix/databases/kam940q1/datafiles/root.dbf
> ROOTOFFSET 0 # Offset of root dbspace into device
> (Kbytes)
> ROOTSIZE 35000 # Size of root dbspace (Kbytes) 9/96:changedfrom
> 20000
> # 1/7/97: changed from 22500 to 25000
>
> # Disk Mirroring Configuration Parameters
>
> MIRROR 0 # Mirroring flag (Yes = 1, No = 0)
> # Path for device containing mirrored root
> # MIRRORPATH /usr/informix/databases/kam940q1/mirrorfiles/mirror.dbf
> MIRROROFFSET 0 # Offset into mirrored device (Kbytes)>
> # Physical Log Configuration
>
> PHYSDBS rootdbs # Location (dbspace) of physical log
> PHYSFILE 2000 # Physical log file size (Kbytes)> # Logical Log Configuration
>
> LOGFILES 6 # Number of logical log files
> LOGSIZE 1000 # Logical log size (Kbytes)>
> # Diagnostics
>
> # System message log file path
> MSGPATH /usr/informix/databases/kam940q1/logfiles/online.log
> CONSOLE /usr/informix/databases/kam940q1/logfiles/console.log
> ALARMPROGRAM # Alarm program path>
> # System Archive Tape Device
>
> TAPEDEV /usr/informix/databases/kam940q1/logfiles/tape # Tape
> device path
> TAPEBLK 32 # Tape block size (Kbytes)
> TAPESIZE 1024000 # Maximum amount of data to put on tape
> (Kbytes)>
> # Log Archive Tape Device
>
> LTAPEDEV /usr/informix/databases/kam940q1/logfiles/ltape # Log
tape
> device path
> LTAPEBLK 32 # Log tape block size (Kbytes)
> LTAPESIZE 1024000 # Max amount of data to put on log tape
> (Kbytes)>
> # Optical
>
> STAGEBLOB # INFORMIX-OnLine/Optical staging area
>
> # System Configuration
>
> SERVERNUM 1 # Unique id corresponding to a OnLine> instance
> DBSERVERNAME kam940q1 # Name of default databaseserver
> DBSERVERALIASES # List of alternate dbservernames
> DEADLOCK_TIMEOUT 60 # Max time to wait of lock indistributed
> env.
> RESIDENT 0 # Forced residency flag (Yes = 1, No =
0)
>
> MULTIPROCESSOR 0 # 0 for single-processor, 1 for> multi-processor
> NUMCPUVPS 1 # Number of user (cpu) vps
> SINGLE_CPU_VP 1 # If non-zero, limit number of cpu vpsto
> one
>
> NOAGE 0 # Process aging
> AFF_SPROC 0 # Affinity start processor
> AFF_NPROCS 0 # Affinity number of processors>
> # Shared Memory Parameters
>
> LOCKS 5000 # Maximum number of locks
> BUFFERS 200 # Maximum number of shared buffers
> NUMAIOVPS 2 # Number of IO vps
> PHYSBUFF 32 # Physical log buffer size (Kbytes)
> LOGBUFF 32 # Logical log buffer size (Kbytes)> LOGSMAX 6 # Maximum number of logical log files
> CLEANERS 1 # Number of buffer cleaner processes
> SHMBASE 0x0A000000L # Shared memory base address
> NETTYPE ipcshm,1,20,CPU # Override sqlhosts defaults> # NETTYPE tlitcp,1,20,NET # Override sqlhosts defaults
> SHMVIRTSIZE 8000 # initial virtual shared memory segmentsize
> SHMADD 8192 # Size of new shared memory segments
> (Kbytes)
> SHMTOTAL 0 # Total shared memory (Kbytes).
0=>unlimited
> CKPTINTVL 300 # Check point interval (in sec)
> LRUS 8 # Number of LRU queues
> LRU_MAX_DIRTY 60 # LRU percent dirty begin cleaning limit
> LRU_MIN_DIRTY 50 # LRU percent dirty end cleaning limit
> LTXHWM 50 # Long transaction high water mark> percentage
> LTXEHWM 60 # Long transaction high water mark
> (exclusive)
> TXTIMEOUT 300 # Transaction timeout (in sec)
> STACKSIZE 32 # Stack size (Kbytes)>
> # System Page Size
> # BUFFSIZE - OnLine no longer supports this configuration parameter.
> # To determine the page size used by OnLine on your platform
> # see the last line of output from the command, 'onstat
-b'.nate
> dbservernames
>
>
> # Recovery Variables
> # OFF_RECVRY_THREADS:
> # Number of parallel worker threads during fast recovery or an offline
> restore.
> # ON_RECVRY_THREADS:
> # Number of parallel worker threads during an online restore.
>
> OFF_RECVRY_THREADS 10 # Default number of offline workerthreads
> ON_RECVRY_THREADS 1 # Default number of online workerthreads
>
> # Data Replication Variables
> # DRAUTO: 0 manual, 1 retain type, 2 reverse type
> DRAUTO 0 # DR automat
Hello:
You may also want to look at your sqlhosts file.
Check how the host name is listed. I have found that changing the
server's host name (in sqlhosts) from a name to the server's IP address
could also possibly resolve this problem.
Best regards,
Martin M. Graney
Network Manager
Queues Enforth Development, Inc.
14 Summer Street
2nd Floor
Malden, MA 02148
781-870-1100
-----Original Message-----
From: forum.subscriber@iiug.org [mailto:forum.subscriber@iiug.org] On
Behalf Of Martin Fuer....
Sent: Friday, January 21, 2005 4:02 AM
To: ids@iiug.org
Subject: Re: -25572 Network driver cannot bind a name to the port.
[4071]
Hi,
is this a message that you get from the listener thread,
right away upon startup of the server ?
Or is this a message that you get when trying the first connect
to the running server (assuming that it runs properly) ?
Or does this message appear sometime upon a connection
attempt while there are already established sessions (and
those users can work with the database) ?
If the server is running (i.e. got past startup), then you
can do "onstat -g ntu" to check that there is a listener thread
listening with the correct protocol.
You can put a comment before the remaining NETTYPE
parameter in your onconfig file. This NETTYPE is for ipcshm,
but you've a server name configured only for tlitcp, so this
NETTYPE parameter is not helpful (there are versions known
to do funny things in this situation).
Are you sure that protocol tlitcp is supported on your platform ?
Check the machine specific notes
( in $INFORMIXDIR/release/en_us/0333/... ) to find out.
Run "netstat -an" system utility to find out if the port 8000
you want to use is "occupied" by someone else. In that case
use a different (unique) portnumber.
Make sure that the server has enough resources, especially
concurrently open file descriptors, because each TCP/IP
connection requires one of those (in addition to those for
all the chunks, message file, etc.).
You may have observed that others diligently provide
the exact IDS version number (e.g. 9.40.UC2) and platform
information when asking questions. As you can see, this
often makes sense, because there are quite a few things
that can depend on this ...
Regards,
Martin
--
Martin Fuerderer
IBM Informix Development Munich, Germany
Information Management
forum.subscriber@iiug.org wrote on 21.01.2005 06:13:46:
>
> Hi,
>
> I am getting following error message
>
> "-25572 Network driver cannot bind a name to the port."
>
> Please find the contain of INFORMIX environment variables, sqlhosts,
> services and onconfig file.
>
> INFORMIX environment variables
> INFORMIXDIR=/usr/informix/9.40.UC1
> INFORMIXSERVER=kam940q1
> ONCONFIG=onconfig.kam940q1>
> SQLHOSTS
> kam940q1 ontlitcp kamal shailesh
> kamxpsq1.1 onipcshm kamal infsrv2>
> SERVICES
> shailesh 8000/tcp # Informix database
client
> connection
> #infsrv0 8000/tcp # Informix database
client
> connection
> infsrv2 7206/tcp # Informix database client
> connection
> infsrv6 7201/tcp # Informix database client
> connection
> infsrv7 7202/tcp # Informix database client
> connection
> infsrv8 7203/tcp # Informix database client
> connection
> infsrv9 7204/tcp # Informix database client
> connection
> infsrv13 7266/tcp # Informix database client
> connection
> infsrv14 7267/tcp # Informix database client
> connection
>
>
>
> onconfig.kam940q1
> # Root Dbspace Configuration
>
> ROOTNAME rootdbs # Root dbspace name
> ROOTPATH /usr/informix/databases/kam940q1/datafiles/root.dbf
> ROOTOFFSET 0 # Offset of root dbspace into device
> (Kbytes)
> ROOTSIZE 35000 # Size of root dbspace (Kbytes) 9/96:changedfrom
> 20000
> # 1/7/97: changed from 22500 to 25000
>
> # Disk Mirroring Configuration Parameters
>
> MIRROR 0 # Mirroring flag (Yes = 1, No = 0)
> # Path for device containing mirrored root
> # MIRRORPATH /usr/informix/databases/kam940q1/mirrorfiles/mirror.dbf
> MIRROROFFSET 0 # Offset into mirrored device (Kbytes)>
> # Physical Log Configuration
>
> PHYSDBS rootdbs # Location (dbspace) of physical log
> PHYSFILE 2000 # Physical log file size (Kbytes)> # Logical Log Configuration
>
> LOGFILES 6 # Number of logical log files
> LOGSIZE 1000 # Logical log size (Kbytes)>
> # Diagnostics
>
> # System message log file path
> MSGPATH /usr/informix/databases/kam940q1/logfiles/online.log
> CONSOLE /usr/informix/databases/kam940q1/logfiles/console.log
> ALARMPROGRAM # Alarm program path>
> # System Archive Tape Device
>
> TAPEDEV /usr/informix/databases/kam940q1/logfiles/tape # Tape
> device path
> TAPEBLK 32 # Tape block size (Kbytes)
> TAPESIZE 1024000 # Maximum amount of data to put ontape
> (Kbytes)
>
> # Log Archive Tape Device
>
> LTAPEDEV /usr/informix/databases/kam940q1/logfiles/ltape # Log
tape
> device path
> LTAPEBLK 32 # Log tape block size (Kbytes)
> LTAPESIZE 1024000 # Max amount of data to put on logtape
> (Kbytes)
>
> # Optical
>
> STAGEBLOB # INFORMIX-OnLine/Optical staging area
>
> # System Configuration
>
> SERVERNUM 1 # Unique id corresponding to a OnLine> instance
> DBSERVERNAME kam940q1 # Name of default databaseserver
> DBSERVERALIASES # List of alternate dbservernames
> DEADLOCK_TIMEOUT 60 # Max time to wait of lock indistributed
> env.
> RESIDENT 0 # Forced residency flag (Yes = 1, No =
0)
>
> MULTIPROCESSOR 0 # 0 for single-processor, 1 for> multi-processor
> NUMCPUVPS 1 # Number of user (cpu) vps
> SINGLE_CPU_VP 1 # If non-zero, limit number of cpu vps
to
> one
>
> NOAGE 0 # Process aging
> AFF_SPROC 0 # Affinity start processor
> AFF_NPROCS 0 # Affinity number of processors>
> # Shared Memory Parameters
>
> LOCKS 5000 # Maximum number of locks
> BUFFERS 200 # Maximum number of shared buffers
> NUMAIOVPS 2 # Number of IO vps
> PHYSBUFF 32 # Physical log buffer size (Kbytes)
> LOGBUFF 32 # Logical log buffer size (Kbytes)> LOGSMAX 6 # Maximum number of logical log files
> CLEANERS 1 # Number of buffer cleaner processes
> SHMBASE 0x0A000000L # Shared memory base address
> NETTYPE ipcshm,1,20,CPU # Override sqlhosts defaults> # NETTYPE tlitcp,1,20,NET # Override sqlhosts defaults
> SHMVIRTSIZE 8000 # initial virtual shared memorysegment
size
> SHMADD 8192 # Size of new shared memory segments
> (Kbytes)
> SHMTOTAL 0 # Total shared memory (Kbytes).
0=>unlimited
> CKPTINTVL 300 # Check point interval (in sec)
> LRUS 8 # Number of LRU queues
> LRU_MAX_DIRTY 60 # LRU percent dirty begin cleaninglimit
> LRU_MIN_DIRTY 50 # LRU percent dirty end cleaning limit
> LTXHWM 50 # Long transaction high water mark> percentage
> LTXEHWM 60 # Long transaction high water mark
> (exclusive)
> TXTIMEOUT 300 # Transaction timeout (in sec)
> STACKSIZE 32 # Stack size (Kbytes)>
> # System Page Size@@N
Related threads
- onbar -c -F in Windows Informix instance
- Anyone... SQLCODE=-668, ISAM error=-1
- Not using the 100% logical log page size alloacted to informix