RE: Network driver cannot bind a name to the port

unfortunately, on our server rebooting didn't get rid of the files so the problem persists through any amount of reboots. I think the files in /INFORMIXTMP are explained very well in the Administrator's Guide near the back, if anyone's interested in knowing what the engine places there. Best regards, Edmund Nigel Gall Senior Information Systems Specialist Process Plant Services Limited Atlantic Avenue, Point Lisas Industrial Estate Point Lisas, Couva, Trinidad & Tobago, W.I. Tel: (868) 636 2906 x 274 Fax: (868) 679 3770 -----Original Message----- From: Brice Avila [mailto:bavila@wamnet.com] Sent: Thursday, September 14, 2000 2:52 PM To: Nigel Gall Subject: Re: Network driver cannot bind a name to the port One can also reboot the server, though Nigel's steps are considerably easier. Brice Nigel Gall wrote: > > Dealing specifically with the *-25572 Network driver cannot bind a name to > the port* error, we get that whenever our server crashes (i.e. OS crash) > without bringing the engine down properly first. What happenes is that some > engine files needed for proper network port management get left in > /INFORMIXTMP and this causes the engine to think that you already have > another instance of the engine running on the port you specified for it in > /etc/services. > > What you need to do is: > > - Login as root (because /INFORMIXTMP and all its contents are owned by > root). > > - cd /INFORMIXTMP > > - mkdir tmp (create a temporary subdirectory of /INFORMIXTMP). > > - mv * tmp > > - mv .??* tmp (these two commands move all files to the tmp directory). > > - Start you instance (check for other config problems first, if any). > > hope this helps. > > Best regards, > > Edmund Nigel Gall > Senior Information Systems Specialist > Process Plant Services Limited > Atlantic Avenue, Point Lisas Industrial Estate > Point Lisas, Couva, Trinidad & Tobago, W.I. > Tel: (868) 636 2906 x 274 Fax: (868) 679 3770 > > -----Original Message----- > From: Yarlagadda, Ravi [mailto:ryarlagadda@labattusa.com] > Sent: Tuesday, September 12, 2000 10:59 AM > To: informix-list@iiug.org > Subject: Network driver cannot bind a name to the port > > Installing IDS (WORK GROUP SERVER) 7.31 FC6 (64 bit version) on HP-UX11.0. > > I tried to initialize using ONMONITOR utility and it doesn't allowed to > complete all field inputs. (PERFORMANCE TUNING PARAMETERS SCREEN). I called > Informix Tech support, ONMONITOR utility has known bug (it seems according > to Informix tech support ) in the above environment and couldn't initialize > the server. Server should be initialize in alternative procedure. > > I changed the onconfig, sqlhosts and /etc/services files and I tried to > initialize with oninit -iyv command and Server was not initialize and "Net > work driver cannot bind a name to the port " message found in the log file. > > Please find the attachments : > ------------------------------------------ > 1. oninit -iyv : the output is as follows : > > Checking group membership to determine server run modesucceeded > Reading configuration file '/informix/7.31/etc/onconfig.ifmx'...succeeded > Creating /INFORMIXTMP/.infxdirs ... succeeded > Creating infos file "/informix/7.31/etc/.infos.ifmx_online" ... > "/informix/7.31/ > etc/.conf.ifmx_online" ... succeeded > Writing to infos file ... succeeded > Checking config parameters...succeeded > Allocating and attaching to shared memory...succeeded > Creating resident pool 5380 kbytes...succeeded > Creating buffer pool 15994 kbytes...succeeded > Creating buffer pool 10 kbytes...succeeded > Initializing rhead structure...succeeded > Initializing ASF ...succeeded > Initializing Dictionary Cache and Stored Procedure Cache...succeeded > Bringing up ADM VP...succeeded > Creating VP classes...succeeded > Onlining 0 additional cpu vps...succeeded > Onlining 2 IO vps...succeeded > Forking main_loop thread...succeeded > Initialzing DR structures...succeeded > Forking 1 'ipcshm' listener threads...succeeded > Forking 1 'soctcp' listener threads...succeeded > Forking 0 'soctcp' listener threads...succeeded > Starting tracing...succeeded > Initializing 1 flushers...succeeded > Initializing log/checkpoint information... > > 2. LOG message in online.log : > ------------------------------------- > 08:53:52 Event alarms enabled. ALARMPROG = > '/informix/7.31/etc/log_full.sh' > 08:53:58 DR: DRAUTO is 0 (Off) > 08:53:58 Informix Dynamic Server Version 7.31.FC6 Software SerialNumber > ACN > #A313826 > 08:53:58 listener-thread: err = -25572: oserr = 227: errstr = : Network> driver > cannot bind a name to the port. > System error = 227. > 08:53:58 Attempting to bring listener thread down. > > 08:53:58 Server stopped. > > 08:53:58 Informix Dynamic Server Stopped. > 08:53:58 mt_shm_remove: WARNING: may not have removed all/correctsegments > > ---------------------------------------------------------------------------- > ------------- > 3. $INFORMIXDIR/etc/sqlhosts entrires : > ---------------------------------------------------- > > ifmx_online onsoctcp locnet2 ifmx_srvc > ifmx_tcp onsoctcp locnet1 ifmx_tcp> > 5. /etc/services/ entries : > ------------------------------ > ifmx_srvc 1525/tcp # service used by OnLine/DSA > ifmx_dev_srvc 2056/tcp # serviced used by OnLine/DSA Development > ifmx_shm 2057/tcp # service used by OnLine/DSA > locnet2 2058/tcp # service used on OnLine/DSA > ifmx_tcp 2059/tcp > > 4. $INFORMIXDIR/etc/onconfig.ifmx > ---------------------------------------------- > # Root Dbspace Configuration > > ROOTNAME rootdbs # Root dbspace name > ROOTPATH /informix/7.31/chunks/rootdbs> # Path for device containing root dbspace > ROOTOFFSET 0 # Offset of root dbspace into device > (Kbytes) > ROOTSIZE 30000 # Size of root dbspace (Kbytes)> > # Disk Mirroring Configuration Parameters > > MIRROR 1 # Mirroring flag (Yes = 1, No = 0) > MIRRORPATH # Path for device containing mirrored root> # Path for device containing mirrored root > 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 16 # Number of logical log files > LOGSIZE 500 # Logical log size (Kbytes)> > # Diagnostics > > MSGPATH /informix/7.31/online.log # System message log file path > CONSOLE /dev/null # System null message path > # ALARMPROGRAM /informix/7.31/logs.sh # Alarm program path> > # System Archive Tape Device > > TAPEDEV /dev/null # Tape device path@@N