Re: Informix Network Connection

So do I. "Lello, Nick" <Nick.Lello@nielsenedi.com> wrote in message news:c2vte7$r5e$1@terabinaries.xmission.com... > > Thomas, > > I believe the correct network connection type for linux is tlitcp not > soctcp. > > > -----Original Message----- > From: owner-informix-list@iiug.org [mailto:owner-informix-list@iiug.org] > On Behalf Of Thomas Ronayne > Sent: Saturday, March 13, 2004 7:03 AM > To: informix-list@iiug.org > Subject: Informix Network Connection > > I am unable to figure out how to make a network connection and would > appreciate someone pointing me in the right direction. On my Slackware > Linux 9.1 system, Informix Dynamic Server 7.30.U, I'm trying to get the > network connection working (so I can use PHP with Informix). The shared > memory connection works fine, but attempting to get the network > connection started is an abject failure (and, yes, I've been through the > > Client/Server Communications section of the manual and I've tried > everything I can think of). > > With onconfig entries > > SERVERNUM 1 # Unique id corresponding to a > Dynamic Server instance > DBSERVERNAME fubar_a # Name of default database server > DBSERVERALIASES fubar_anet # Name of network database> server > NETTYPE ipcshm,1,100,CPU # Configure poll thread(s) > for nettype > NETTYPE soctcp,1,100,NET # Configure poll > thread(s) for nettype > DEADLOCK_TIMEOUT 60 # Max time to wait of lock in > distributed env. > RESIDENT 0 # Forced residency flag (Yes = 1, No > = 0)> > and sqlhost entries > > fubar_a onipcshm fubar informixa > fubar_anet onsoctcp fubar informixanet> > and /etc/services entries > > informixa 1625/tcp # IBM Informix 7.x engine shared > informixanet 1725/tcp # IBM Informix 7.x engine network > > When I execute oninit the online log shows > > Sat Mar 13 09:38:53 2004 > > 09:38:53 Event alarms enabled. ALARMPROG = > '/opt/informix/etc/log_full.sh' > 09:38:59 DR: DRAUTO is 0 (Off) > 09:39:00 Informix Dynamic Server Version 7.30.U Software Serial > Number AAC#A404657 > 09:39:00 listener-thread: err = -27100: oserr = 2: errstr = : > Internal Communications Error: NSF subsystem error. > System error = 2. > 09:39:00 Attempting to bring listener thread down > > 09:39:00 PANIC: Attempting to bring system down > > If I comment out the DBSERVERALIASES and NETTYPE lines in onconfig, > oninit starts fine and everything works as expected. > > Any help would be most appreciated. > > > > sending to informix-list

Most Linux distributions will require editing some kind of network interface. There is a general paranoia in the Linux/UNIX community regarding r-commands, ( rlogin, rcp, rpc, etc ) telnet, and inetd due to their limited security architecture. Most Linux systems do not even put telnet or the r-coomands on the system, you will have to do this manually. Most likely you will have an sshd set up,and again it will probably have to be turned on manually. Many systems have sshd set up to be lit on boot, so this may or may not be an issue. sshd will not work at all if you do not edit the sshd_config file from its original default. Trying to telnet to your system will work only if you configure it in your /etc/inetd.conf and it is even installed on your machine. Again, inetd is another amongst the services that are not being turned on by default, and as a result you may not be getting ANY networking to work. It may not even be installed, so check this out as well. I don't know what Red Hat does, so the following will work on SuSE, Gentoo, other distros outside of RH. Inetd: ( Check to see if it's even installed ) If you are using inetd, you will most likely have to turn it on. Uncomment the desired services /etc/inetd.conf /etc/init.d/inetd start|stop Xinetd: ( Check to see if it's even installed ) Xinetd works with individual conf files for each service. Services are typically enabled with the "disable = no" directive. You will find them in an xinetd.d directory, typically /etc/xinetd.d . The desired service will not function if the config is "disabled = yes". /etc/xinetd.conf and /etc/xinetd.d/config-files /etc/init.d/xinetd start|stop Also check to see if this directive is in any config: only_from = localhost This will limit connections as well. SSH ( Check to see if it's even installed ) /etc/ssh/sshd_config /etc/init.d/sshd start|stop You may even have a firewall turned on that is blocking all ports with IPtables. This is yet another reason why you might not connect. Check to see if a firewall is running, turn it off and see if that is causing the blockage. Also, you can have all three of the above installed and working at the same time. Good luck! -DG- Neil Truby wrote: > So do I. > > "Lello, Nick" <Nick.Lello@nielsenedi.com> wrote in message > news:c2vte7$r5e$1@terabinaries.xmission.com... > >>Thomas, >> >>I believe the correct network connection type for linux is tlitcp not >>soctcp. >> >> >>-----Original Message----- >>From: owner-informix-list@iiug.org [mailto:owner-informix-list@iiug.org] >>On Behalf Of Thomas Ronayne >>Sent: Saturday, March 13, 2004 7:03 AM >>To: informix-list@iiug.org >>Subject: Informix Network Connection >> >>I am unable to figure out how to make a network connection and would >>appreciate someone pointing me in the right direction. On my Slackware >>Linux 9.1 system, Informix Dynamic Server 7.30.U, I'm trying to get the >>network connection working (so I can use PHP with Informix). The shared >>memory connection works fine, but attempting to get the network >>connection started is an abject failure (and, yes, I've been through the >> >>Client/Server Communications section of the manual and I've tried >>everything I can think of). >> >>With onconfig entries >> >> SERVERNUM 1 # Unique id corresponding to a >> Dynamic Server instance >> DBSERVERNAME fubar_a # Name of default database server >> DBSERVERALIASES fubar_anet # Name of network database>>server >> NETTYPE ipcshm,1,100,CPU # Configure poll thread(s) >> for nettype >> NETTYPE soctcp,1,100,NET # Configure poll >> thread(s) for nettype >> DEADLOCK_TIMEOUT 60 # Max time to wait of lock in >> distributed env. >> RESIDENT 0 # Forced residency flag (Yes = 1, No >> = 0)>> >>and sqlhost entries >> >> fubar_a onipcshm fubar informixa >> fubar_anet onsoctcp fubar informixanet>> >>and /etc/services entries >> >> informixa 1625/tcp # IBM Informix 7.x engine shared >> informixanet 1725/tcp # IBM Informix 7.x engine network >> >>When I execute oninit the online log shows >> >> Sat Mar 13 09:38:53 2004 >> >> 09:38:53 Event alarms enabled. ALARMPROG = >> '/opt/informix/etc/log_full.sh' >> 09:38:59 DR: DRAUTO is 0 (Off) >> 09:39:00 Informix Dynamic Server Version 7.30.U Software Serial >> Number AAC#A404657 >> 09:39:00 listener-thread: err = -27100: oserr = 2: errstr = : >> Internal Communications Error: NSF subsystem error. >> System error = 2. >> 09:39:00 Attempting to bring listener thread down >> >> 09:39:00 PANIC: Attempting to bring system down >> >>If I comment out the DBSERVERALIASES and NETTYPE lines in onconfig, >>oninit starts fine and everything works as expected. >> >>Any help would be most appreciated. >> >> >> >>sending to informix-list > > >

Thought of one other thing for NFS: Make sure rpc.statd is running. -DG- Data Goob wrote: > > Most Linux distributions will require editing some kind of network > interface. There is a general paranoia in the Linux/UNIX community > regarding r-commands, ( rlogin, rcp, rpc, etc ) telnet, and inetd > due to their limited security architecture. > > Most Linux systems do not even put telnet or the r-coomands on the > system, you will have to do this manually. Most likely you will > have an sshd set up,and again it will probably have to be turned > on manually. Many systems have sshd set up to be lit on boot, so > this may or may not be an issue. sshd will not work at all if you > do not edit the sshd_config file from its original default. > > Trying to telnet to your system will work only if you configure it > in your /etc/inetd.conf and it is even installed on your machine. > Again, inetd is another amongst the services that are not being > turned on by default, and as a result you may not be getting ANY > networking to work. It may not even be installed, so check this > out as well. > > I don't know what Red Hat does, so the following will work on SuSE, > Gentoo, other distros outside of RH. > > Inetd: ( Check to see if it's even installed ) > > If you are using inetd, you will most likely have to turn > it on. Uncomment the desired services > > /etc/inetd.conf > /etc/init.d/inetd start|stop > > Xinetd: ( Check to see if it's even installed ) > > Xinetd works with individual conf files for each service. > Services are typically enabled with the "disable = no" > directive. You will find them in an xinetd.d directory, > typically /etc/xinetd.d . The desired service will not > function if the config is "disabled = yes". > > /etc/xinetd.conf and /etc/xinetd.d/config-files > /etc/init.d/xinetd start|stop > > Also check to see if this directive is in any config: > only_from = localhost > > This will limit connections as well. > > SSH ( Check to see if it's even installed ) > > /etc/ssh/sshd_config > /etc/init.d/sshd start|stop > > You may even have a firewall turned on that is blocking all ports > with IPtables. This is yet another reason why you might not connect. > Check to see if a firewall is running, turn it off and see if that > is causing the blockage. > > Also, you can have all three of the above installed and working at > the same time. > > Good luck! > > -DG- > > > Neil Truby wrote: > >> So do I. >> >> "Lello, Nick" <Nick.Lello@nielsenedi.com> wrote in message >> news:c2vte7$r5e$1@terabinaries.xmission.com... >> >>> Thomas, >>> >>> I believe the correct network connection type for linux is tlitcp not >>> soctcp. >>> >>> >>> -----Original Message----- >>> From: owner-informix-list@iiug.org [mailto:owner-informix-list@iiug.org] >>> On Behalf Of Thomas Ronayne >>> Sent: Saturday, March 13, 2004 7:03 AM >>> To: informix-list@iiug.org >>> Subject: Informix Network Connection >>> >>> I am unable to figure out how to make a network connection and would >>> appreciate someone pointing me in the right direction. On my Slackware >>> Linux 9.1 system, Informix Dynamic Server 7.30.U, I'm trying to get the >>> network connection working (so I can use PHP with Informix). The shared >>> memory connection works fine, but attempting to get the network >>> connection started is an abject failure (and, yes, I've been through the >>> >>> Client/Server Communications section of the manual and I've tried >>> everything I can think of). >>> >>> With onconfig entries >>> >>> SERVERNUM 1 # Unique id corresponding to a >>> Dynamic Server instance >>> DBSERVERNAME fubar_a # Name of default database server >>> DBSERVERALIASES fubar_anet # Name of network database>>> server >>> NETTYPE ipcshm,1,100,CPU # Configure poll thread(s) >>> for nettype >>> NETTYPE soctcp,1,100,NET # Configure poll >>> thread(s) for nettype >>> DEADLOCK_TIMEOUT 60 # Max time to wait of lock in >>> distributed env. >>> RESIDENT 0 # Forced residency flag (Yes = 1, No >>> = 0)>>> >>> and sqlhost entries >>> >>> fubar_a onipcshm fubar informixa >>> fubar_anet onsoctcp fubar informixanet>>> >>> and /etc/services entries >>> >>> informixa 1625/tcp # IBM Informix 7.x engine shared >>> informixanet 1725/tcp # IBM Informix 7.x engine network >>> >>> When I execute oninit the online log shows >>> >>> Sat Mar 13 09:38:53 2004 >>> >>> 09:38:53 Event alarms enabled. ALARMPROG = >>> '/opt/informix/etc/log_full.sh' >>> 09:38:59 DR: DRAUTO is 0 (Off) >>> 09:39:00 Informix Dynamic Server Version 7.30.U Software Serial >>> Number AAC#A404657 >>> 09:39:00 listener-thread: err = -27100: oserr = 2: errstr = : >>> Internal Communications Error: NSF subsystem error. >>> System error = 2. >>> 09:39:00 Attempting to bring listener thread down >>> >>> 09:39:00 PANIC: Attempting to bring system down >>> >>> If I comment out the DBSERVERALIASES and NETTYPE lines in onconfig, >>> oninit starts fine and everything works as expected. >>> >>> Any help would be most appreciated. >>> >>> >>> >>> sending to informix-list >> >> >> >> > >

Data Goob <datagoob@netscape.net> writes: > Most Linux systems do not even put telnet or the r-coomands on the > system, you will have to do this manually. Most likely you will > have an sshd set up,and again it will probably have to be turned > on manually. Many systems have sshd set up to be lit on boot, so > this may or may not be an issue. sshd will not work at all if you > do not edit the sshd_config file from its original default. You are fairly safe installing only the clients. > Trying to telnet to your system will work only if you configure it > in your /etc/inetd.conf and it is even installed on your machine. Only true if you are trying to connect to telnetd, which I just finished advising not installing. Actually, you can use the telnet client to connect to any port with an active listener: smtp, http, nntp, informix, etc. > Again, inetd is another amongst the services that are not being > turned on by default, and as a result you may not be getting ANY > networking to work. It may not even be installed, so check this > out as well. If you most likely have an sshd set up and working, then you have an *inetd running. > You may even have a firewall turned on that is blocking all ports > with IPtables. This is yet another reason why you might not connect. > Check to see if a firewall is running, turn it off and see if that > is causing the blockage. Which is why I suggested that he try telnetting to the machine name at the informix port he defined. If he can't resolve the machine name, then it's a DNS problem. If he can't connect to the informix port, then more investigation is required as to whether the engine is down, or the port is firewalled. Use of "netstat -an" can be of assistance to determine whether the engine is up and what port it is listening on. -- Forte International, P.O. Box 1412, Ridgecrest, CA 93556-1412 Ronald Cole <ronald@forte-intl.com> Phone: (760) 499-9142 President, CEO Fax: (760) 499-9152 My GPG fingerprint: C3AF 4BE9 BEA6 F1C2 B084 4A88 8851 E6C8 69E3 B00B

Agreed Ronald. The problem with Linux or UNIX is that networking is still a domain of expertise that many DBAs or application people do not have. Trivial networking is not trivial to the inexperienced. To make matters worse, the problem solving effort, however noble, might not be solved unless the networking infrastructure is set correctly in the first place. Most Linux distributions still lack decent front-end tools for diagnosing networking in a way that makes sense to people that don't do networking for a living. There are a few exceptions. SuSE has a decent set of networking GUIs, albeit still somewhat primitive. One of the tools I highly recommend is nmap, another iptraf. Nmap is a great way to see what ports are open on any system, and the Xnmap GUI is fantastic. This tool appears somewhat intimidating on the surface but is quite easy to use and quite powerful. The Xnmap GUI is simply an overlay for the command line program. Iptraf is a great monitoring tool, but will probably not be of much good if you're networking is not working. There's always the ifconfig command, and even more ghastly, iptables. ( iptables -L ). http://www.insecure.org/nmap/nmap_download.html http://iptraf.seul.org/ Good Luck! "Ronald Cole" <ronald@forte-intl.com> wrote in message news:m3fzcav6si.fsf@yakisoba.forte-intl.com... > Data Goob <datagoob@netscape.net> writes: > > Most Linux systems do not even put telnet or the r-coomands on the > > system, you will have to do this manually. Most likely you will > > have an sshd set up,and again it will probably have to be turned > > on manually. Many systems have sshd set up to be lit on boot, so > > this may or may not be an issue. sshd will not work at all if you > > do not edit the sshd_config file from its original default. > > You are fairly safe installing only the clients. > > > Trying to telnet to your system will work only if you configure it > > in your /etc/inetd.conf and it is even installed on your machine. > > Only true if you are trying to connect to telnetd, which I just > finished advising not installing. Actually, you can use the telnet > client to connect to any port with an active listener: smtp, http, > nntp, informix, etc. > > > Again, inetd is another amongst the services that are not being > > turned on by default, and as a result you may not be getting ANY > > networking to work. It may not even be installed, so check this > > out as well. > > If you most likely have an sshd set up and working, then you have an > *inetd running. > > > You may even have a firewall turned on that is blocking all ports > > with IPtables. This is yet another reason why you might not connect. > > Check to see if a firewall is running, turn it off and see if that > > is causing the blockage. > > Which is why I suggested that he try telnetting to the machine name at > the informix port he defined. If he can't resolve the machine name, > then it's a DNS problem. If he can't connect to the informix port, > then more investigation is required as to whether the engine is down, > or the port is firewalled. Use of "netstat -an" can be of assistance > to determine whether the engine is up and what port it is listening > on. > > -- > Forte International, P.O. Box 1412, Ridgecrest, CA 93556-1412 > Ronald Cole <ronald@forte-intl.com> Phone: (760) 499-9142 > President, CEO Fax: (760) 499-9152 > My GPG fingerprint: C3AF 4BE9 BEA6 F1C2 B084 4A88 8851 E6C8 69E3 B00B