Network driver bind issue

Hi, I'm having a problem starting up a database. Oninit -v shows everything starting no problem and I am brought back to the command line happily. However, onstat after that shows the shared memory is not initialized. In the log we have: listener-thread: err = -25572: oserr = 9: errstr = : Network driver cannot bind a name to the port. However, there is nothing using the TCP port I'm trying to use. I've also tried changing the port number (twice) with no luck. It definitely appears to be a problem with the TCP as if I comment out the dbserveralias and the entry in sqlhosts the DB will start up (with just it's shared memory connection). I'm using onsoctcp, running Informix 9.30UC3 on an SGI O200. Another oddity I saw from the oninit -v is "Forking 1 'soctcp' listener threads...succeeded"..eh what? Any help would be much appreciated. Tosh Baird.

Hi, you may want to check the ports (currently) in use on your system by using a system utility, e.g. "netstat -an". This should show you (in numerical format) the port numbers in use and you can check if the one you intended for IDS is used already (though it's not easy to find out by whom ...). [ On a system, not only the ports listed in /etc/services are used, but many others as well. On some systems, ranges are defined for dynamically assigning port numbers. If you're in this range by accident, then you can have sporadic problems with ports already in use. Though I'm not sure how these things are implemented in the TCP/IP stack on SGI ... ] Also you may want to check whether a file's been created with the service name (e.g. in /INFORMIXTMP directory). Generally this is a potential problem with non-TCP/IP protocols, since for TCP/IP protocols usually no such file is generated. But again I'm not 100% sure about the implementation on SGI. The message that the listener was forked successfully refers to the creation of the thread/process. It does not mean that the thread/process does not hit an obstacle during it's life-time. Admittedly, it happens quite early in this case, but anyway after creation ... Regards, Martin -- Martin Fuerderer IBM Informix Development Munich Data Management Solutions "Tosh Baird" <Tosh.Baird@peace.com> Sent by: forum.subscriber@iiug.org 20.10.2003 05:12 To: ids@iiug.org cc: Subject: Network driver bind issue [2045] Hi, I'm having a problem starting up a database. Oninit -v shows everything starting no problem and I am brought back to the command line happily. However, onstat after that shows the shared memory is not initialized. In the log we have: listener-thread: err = -25572: oserr = 9: errstr = : Network driver cannot bind a name to the port. However, there is nothing using the TCP port I'm trying to use. I've also tried changing the port number (twice) with no luck. It definitely appears to be a problem with the TCP as if I comment out the dbserveralias and the entry in sqlhosts the DB will start up (with just it's shared memory connection). I'm using onsoctcp, running Informix 9.30UC3 on an SGI O200. Another oddity I saw from the oninit -v is "Forking 1 'soctcp' listener threads...succeeded"..eh what? Any help would be much appreciated. Tosh Baird.

Thanks for all your replies. I've checked the ports using netstat -an and fuser and none of the numbers I've tried was in use already. Note this database WAS working last week (moral of the story: never go on holiday). As requested, here are the relevant entries from sqlhosts, /etc/services, /etc/hosts and my onconfig file: Sqlhosts: itstst03tcp onsoctcp bilbo itstst03tcp /etc/services: itstst03tcp 10238/tcp onconfig: NETTYPE soctcp,1,30,NET DBSERVERALIASES itstst03tcp And /etc/hosts: 10.0.1.86 bilbo.peace.co.nz bilbo -----Original Message----- From: Martin Fuerderer [mailto:MARTINFU@de.ibm.com] Sent: Tuesday, October 21, 2003 1:45 AM To: Tosh Baird Cc: forum.subscriber@iiug.org; ids@iiug.org Subject: Re: Network driver bind issue [2045] Hi, you may want to check the ports (currently) in use on your system by using a system utility, e.g. "netstat -an". This should show you (in numerical format) the port numbers in use and you can check if the one you intended for IDS is used already (though it's not easy to find out by whom ...). [ On a system, not only the ports listed in /etc/services are used, but many others as well. On some systems, ranges are defined for dynamically assigning port numbers. If you're in this range by accident, then you can have sporadic problems with ports already in use. Though I'm not sure how these things are implemented in the TCP/IP stack on SGI ... ] Also you may want to check whether a file's been created with the service name (e.g. in /INFORMIXTMP directory). Generally this is a potential problem with non-TCP/IP protocols, since for TCP/IP protocols usually no such file is generated. But again I'm not 100% sure about the implementation on SGI. The message that the listener was forked successfully refers to the creation of the thread/process. It does not mean that the thread/process does not hit an obstacle during it's life-time. Admittedly, it happens quite early in this case, but anyway after creation ... Regards, Martin -- Martin Fuerderer IBM Informix Development Munich Data Management Solutions "Tosh Baird" <Tosh.Baird@peace.com> Sent by: forum.subscriber@iiug.org 20.10.2003 05:12 To: ids@iiug.org cc: Subject: Network driver bind issue [2045] Hi, I'm having a problem starting up a database. Oninit -v shows everything starting no problem and I am brought back to the command line happily. However, onstat after that shows the shared memory is not initialized. In the log we have: listener-thread: err = -25572: oserr = 9: errstr = : Network driver cannot bind a name to the port. However, there is nothing using the TCP port I'm trying to use. I've also tried changing the port number (twice) with no luck. It definitely appears to be a problem with the TCP as if I comment out the dbserveralias and the entry in sqlhosts the DB will start up (with just it's shared memory connection). I'm using onsoctcp, running Informix 9.30UC3 on an SGI O200. Another oddity I saw from the oninit -v is "Forking 1 'soctcp' listener threads...succeeded"..eh what? Any help would be much appreciated. Tosh Baird.

Hi, I would say your have to rename the service _or_ your DBSERVERNAME Both are named itstst03tcp. Can that have been changed?? Brg / Johan At 22:35 20/10/2003, you wrote: >Thanks for all your replies. > >I've checked the ports using netstat -an and fuser and none of the >numbers I've tried was in use already. Note this database WAS working >last week (moral of the story: never go on holiday). As requested, here >are the relevant entries from sqlhosts, /etc/services, /etc/hosts and my >onconfig file: > >Sqlhosts: > >itstst03tcp onsoctcp bilbo itstst03tcp> >/etc/services: > >itstst03tcp 10238/tcp > >onconfig: > >NETTYPE soctcp,1,30,NET >DBSERVERALIASES itstst03tcp> >And /etc/hosts: > >10.0.1.86 bilbo.peace.co.nz bilbo > > >-----Original Message----- >From: Martin Fuerderer [mailto:MARTINFU@de.ibm.com] >Sent: Tuesday, October 21, 2003 1:45 AM >To: Tosh Baird >Cc: forum.subscriber@iiug.org; ids@iiug.org >Subject: Re: Network driver bind issue [2045] > >Hi, > >you may want to check the ports (currently) in use on your system >by using a system utility, e.g. "netstat -an". This should show you >(in numerical format) the port numbers in use and you can check >if the one you intended for IDS is used already (though it's not easy >to find out by whom ...). > > [ On a system, not only the ports listed in /etc/services are used, > but many others as well. On some systems, ranges are defined > for dynamically assigning port numbers. If you're in this range > by accident, then you can have sporadic problems with ports > already in use. > Though I'm not sure how these things are implemented in the > TCP/IP stack on SGI ... ] > >Also you may want to check whether a file's been created with the >service name (e.g. in /INFORMIXTMP directory). Generally this is >a potential problem with non-TCP/IP protocols, since for TCP/IP >protocols usually no such file is generated. But again I'm not 100% >sure about the implementation on SGI. > >The message that the listener was forked successfully refers to the >creation of the thread/process. It does not mean that the >thread/process does not hit an obstacle during it's life-time. >Admittedly, it happens quite early in this case, but anyway after >creation ... > >Regards, >Martin >-- >Martin Fuerderer >IBM Informix Development Munich >Data Management Solutions > > > > > >"Tosh Baird" <Tosh.Baird@peace.com> >Sent by: forum.subscriber@iiug.org >20.10.2003 05:12 > > > To: ids@iiug.org > cc: > Subject: Network driver bind issue [2045] > > > >Hi, > >I'm having a problem starting up a database. Oninit -v shows everything >starting no problem and I am brought back to the command line happily. >However, onstat after that shows the shared memory is not initialized. >In the log we have: > >listener-thread: err = -25572: oserr = 9: errstr = : Network driver >cannot bind a name to the port. > >However, there is nothing using the TCP port I'm trying to use. I've >also tried changing the port number (twice) with no luck. It definitely >appears to be a problem with the TCP as if I comment out the >dbserveralias and the entry in sqlhosts the DB will start up (with just >it's shared memory connection). I'm using onsoctcp, running Informix >9.30UC3 on an SGI O200. > >Another oddity I saw from the oninit -v is "Forking 1 'soctcp' listener >threads...succeeded"..eh what? > >Any help would be much appreciated. > >Tosh Baird.

Tosh Baird wrote: > Thanks for all your replies. > > I've checked the ports using netstat -an and fuser and none of the > numbers I've tried was in use already. Note this database WAS working > last week (moral of the story: never go on holiday). As requested, here > are the relevant entries from sqlhosts, /etc/services, /etc/hosts and my > onconfig file: > > Sqlhosts: > > itstst03tcp onsoctcp bilbo itstst03tcp> > /etc/services: > > itstst03tcp 10238/tcp > > onconfig: > > NETTYPE soctcp,1,30,NET > DBSERVERALIASES itstst03tcp> > And /etc/hosts: > > 10.0.1.86 bilbo.peace.co.nz bilbo I didn't see what your original problem was. That port number looks large, is that correct? I'm pretty sure that IDS doesn't look at host alias names, although that may have changed in more recent versions, so try swapping your host name round: /etc/hosts: 10.0.1.86 bilbo bilbo.peace.co.nz Or use the full name in your sqlhosts file. You can also debug by putting the actual ip address and port number directly in your sqlhosts file. If that works, then you have a problem with the relevant system file lookups. I prefer to use the names for production though, as it helps document the system. Cheers, -- Mark. +----------------------------------------------------------+-----------+ | Mark D. Stock mailto:mdstock@MydasSolutions.com |//////// /| | Mydas Solutions Ltd http://MydasSolutions.com |///// / //| | +-----------------------------------+//// / ///| | |We value your comments, which have |/// / ////| | |been recorded and automatically |// / /////| | |emailed back to us for our records.|/ ////////| +----------------------+-----------------------------------+-----------+