Example sqlhosts file
A long-time Informix user installing SE 7.2 on Red Hat Linux 5.2 (no docs) asked how to write an sqlhosts entry for a local, non-TCP connection, getting error -25591 "Transport control received an invalid connection address". Art Kagel gave the sqlhosts layout (servername, protocol, hostname, service/port) and advised adding services to /etc/services. Jonathan Leffler explained the likely cause: the hostname field must match the real machine name, and with seipcpip the last field is an executable (relative to $INFORMIXDIR/lib), not an /etc/services entry; also Linux uses sesoctcp rather than setlitcp. The poster then repeated his config with the real hostname but still 'sqlexec'; no confirmation of a working fix is recorded.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
I've used Informix since ver 1.1 (just had to say that), but am confused by the sqlhosts file. The last version I worked on was 4.1 and didn't use it for the SE engine. Now that I've D/L the 7.2 SE (no docs) I'm in the dark about the sqlhost file. Can anyone give me a breif example of setting one up to run locally for development? I also have the 4gl-RDS installed. Thanks - Rick Mills
Rick Mills wrote: > > I've used Informix since ver 1.1 (just had to say that), but am confused > by the sqlhosts file. The last version I worked on was 4.1 and didn't > use it for the SE engine. Now that I've D/L the 7.2 SE (no docs) I'm > in the dark about the sqlhost file. Can anyone give me a breif example > of setting one up to run locally for development? I also have the 4gl-RDS > installed. In 4.xx the sqlhosts file was only used as part of the network product which was a separate product. The 7.x line integrates networking into the base engine product. The format for the sqlhosts file is: servername protocol hostname service/port ex: webserv seipcstr mymachine sqlexec webremote setlitcp mymachine sqltcp then add the two services with unused port numbers to /etc/services and you ready to go. See the release notes for supported protocols on your platform. Art S. Kagel
Thanks for the reply - I'm just trying to set up a local connection-
NON-tcp, using unamed pipes, but I get an error msg -
25591: Transport control received an invalid connection address
My sqlhosts file:
local_se seipcpip local_hostname sqlexec
any thoughts?
-rick
Art S. Kagel <kagel@bloomberg.net> wrote:
> In 4.xx the sqlhosts file was only used as part of the network product
> which was a separate product. The 7.x line integrates networking into
> the base engine product.
> The format for the sqlhosts file is:
> servername protocol hostname service/port
> ex:
> webserv seipcstr mymachine sqlexec
> webremote setlitcp mymachine sqltcp
> then add the two services with unused port numbers to /etc/services and
> you ready to go. See the release notes for supported protocols on your
> platform.
> Art S. Kagel
In article <7c71it$qmg$1@eve.enteract.com>,
Rick Mills <rick@enteract.com> wrote:
>
> Thanks for the reply - I'm just trying to set up a local connection-
> NON-tcp, using unamed pipes, but I get an error msg -
>
> 25591: Transport control received an invalid connection address>
> My sqlhosts file:
>
> local_se seipcpip local_hostname sqlexec
>
> any thoughts?
>
> -rick
>
>>>> See the release notes for supported protocols on your platform. <<<<<<
>
> > Art S. Kagel
>
With best regards, Juri Dovgart,
Bank's "Ukraine" System Administrator;‰
-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
In article <7c823u$ink$1@nnrp1.dejanews.com>,
dua1@my-dejanews.com wrote:
> In article <7c71it$qmg$1@eve.enteract.com>,
> Rick Mills <rick@enteract.com> wrote:
> >
> > Thanks for the reply - I'm just trying to set up a local connection-
> > NON-tcp, using unamed pipes, but I get an error msg -
> >
> > 25591: Transport control received an invalid connection address> >
> > My sqlhosts file:
> >
> > local_se seipcpip local_hostname sqlexec
> >
> > any thoughts?
> >
> > -rick
> >
>
> >>>> See the release notes for supported protocols on your platform. <<<<<<
> >
> > > Art S. Kagel
> >
>
And by the way, who gave you idea to name service as "sqlexec" ????
With best regards, Juri Dovgart,
Bank's "Ukraine" System Administrator;‰
-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
dua1@my-dejanews.com wrote: > In article <7c71it$qmg$1@eve.enteract.com>, > > > Art S. Kagel THere are no release notes with the ftp'd file, and none that I can see on the site anywhere. Does anyone have release notes specific to RedHat Linux 5.2? > > > With best regards, Juri Dovgart, > Bank's "Ukraine" System Administrator;‰ > -----------== Posted via Deja News, The Discussion Network ==---------- > http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
dua1@my-dejanews.com wrote: > In article <7c823u$ink$1@nnrp1.dejanews.com>, > And by the way, who gave you idea to name service as "sqlexec" ???? Page 39 of the System Administrator's manual for Informix SE. -rick > With best regards, Juri Dovgart, > Bank's "Ukraine" System Administrator;‰ > -----------== Posted via Deja News, The Discussion Network ==---------- > http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
Rick Mills wrote:
>
> Thanks for the reply - I'm just trying to set up a local connection-
> NON-tcp, using unamed pipes, but I get an error msg -
>
> 25591: Transport control received an invalid connection address
I note that you subsequently said you're using Linux. Please include
such platform information up front -- it helps.
Unless your machine is called local_hostname, you need to
fix that part of your entry to match what hostname or uname -n says.
That includes the domain information if there is any!
With seipcpip connections, the last field is the name of an
executable, not the name of a service in /etc/services. In fact,
the executable is specified relative to $INFORMIXDIR/lib unless the
name is an absolute pathname. I have an entry in my Sun workstation
sqlhosts file which reads:
se_monitor seipcpip osiris /work/jleffler/bin/sqlmonitor
It runs my monitor program quite happily, thank you.
Also, on Linux, network connections use sesoctcp, not setlitcp.
> My sqlhosts file:
>
> local_se seipcpip local_hostname sqlexec
>
> any thoughts?
>
> -rick
>
> Art S. Kagel <kagel@bloomberg.net> wrote:
> > In 4.xx the sqlhosts file was only used as part of the network
> > product which was a separate product. The 7.x line integrates
> > networking into the base engine product.
>
> > The format for the sqlhosts file is:
>
> > servername protocol hostname service/port
>
> > ex:
> > webserv seipcstr mymachine sqlexec
> > webremote setlitcp mymachine sqltcp
>
> > then add the two services with unused port numbers to
> > /etc/services and you ready to go. See the release notes
> > for supported protocols on your platform.
--
Jonathan Leffler (jleffler@informix.com, jleffler@earthlink.net)
Guardian of DBD::Informix v0.60 -- see http://www.perl.com/CPAN
#include <disclaimer.h>
Jonathan Leffler <jleffler@earthlink.net> wrote:
> I note that you subsequently said you're using Linux. Please include
> such platform information up front -- it helps.
Sorry - of course you're right:
Stock Redhat Linux 5.2 Glibc 2.07
Host name: vihta
sqlhosts file:
local_se seipcpip vihta sqlexec
INFORMIXDIR=/usr/informix
INFORMIXSERVER=local_se
Error msg: 25591 Transport Control received an invalid connection address
Thanks for tolerating my incomplete posts!
-rick mills