SE on Linux
Informix SE 7.24 on Red Hat 6.0: connecting via the seipcpip entry in sqlhosts gave error -25591 ("Transport control received an invalid connection or address"), while the sesoctcp entry worked. One reply claimed the release notes and Informix support said only sesoctcp was supported on Linux, but others showed seipcpip does work. Suggested fixes: the service name (e.g. sqlexec) must exist in /etc/services, and the hostname in sqlhosts must match what uname returns (FQDN if applicable) rather than a loopback address. No confirmation from the original poster is recorded.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Installed Informix SE 7.24uc5 and 7.24ue5 on different boxes running RedHat 6.0. Used the trial version S/N and key. When connecting to "local_se" in dbaccess I get the same error message on both servers: "25591: Transport control received an invalid connection or address." When connecting to "sqlserv" it works fine.
Any ideas? I have been through Infomrix tech support on this. Also have SE running on HPUX without any problems.
DETAILS
/home/informix/etc/sqlhosts
local_se seipcpip echo2 sqlexec
sqlserv sesoctcp echo2 se_tcp
[blank line]
/etc/services
se_tcp 1525/tcp
/etc/hosts
129.1.1.10 echo2
env
INFORMIXDIR=/home/infomrix
INFORMIXSERVER=local_se
PATH=/home/informix/bin:. . .
Alan Miner wrote:
>
> Installed Informix SE 7.24uc5 and 7.24ue5 on different boxes running RedHat 6.0. Used the trial version S/N and key. When connecting to "local_se" in dbaccess I get the same error message on both servers: "25591: Transport control received an invalid connection or address." When connecting to "sqlserv" it works fine.
>
> Any ideas? I have been through Infomrix tech support on this. Also have SE running on HPUX without any problems.
The release notes say that only sesoctcp is supported, not seipcpip as
you seem to use in your sqlhosts.
So you've got to use your sqlserv server which uses sesoctcp.
On Wed, 17 May 2000 19:26:55 GMT, David Stes Wrote:
> Alan Miner wrote:
>>
>> Installed Informix SE 7.24uc5 and 7.24ue5 on different boxes running
>> RedHat 6.0. Used the trial version S/N and key. When connecting to
>> "local_se" in dbaccess I get the same error message on both servers:
>> "25591: Transport control received an invalid connection or address."
>> When connecting to "sqlserv" it works fine.
>>
>> Any ideas? I have been through Infomrix tech support on this.
>> Also have SE running on HPUX without any problems.
>
> The release notes say that only sesoctcp is supported, not seipcpip as
> you seem to use in your sqlhosts.
>
> So you've got to use your sqlserv server which uses sesoctcp.
I wouldnt say so. I have it working fine with :
local seipcpip orpheus sqlexec
Of course it does need to be able to resolve the hostname so you might want
to check that it has an entry in /etc/hosts . Orpheus is in my /etc/hosts
as 127.0.0.2 but it will resolve to a different address when I am on the
network.
/J\\
Jonathan Stowe wrote: > > >> Any ideas? I have been through Infomrix tech support on this. Me too, and informix support told me seipcpip was not supported. > > The release notes say that only sesoctcp is supported, not seipcpip as > > you seem to use in your sqlhosts. The release notes are the one in /usr/informix/release/en_us/0333/SE_7.2 > > So you've got to use your sqlserv server which uses sesoctcp. > > I wouldnt say so. I have it working fine with : > > local seipcpip orpheus sqlexec > > Of course it does need to be able to resolve the hostname so you might want > to check that it has an entry in /etc/hosts . Orpheus is in my /etc/hosts > as 127.0.0.2 but it will resolve to a different address when I am on the > network. You're right. I tried it and indeed it works! So despite informix support and the release notes, it works!! Actually why would you need a hostname and tcp service name for seipcpip?
I believe that for ipcpip you need to have the servicename, sqlexec, in
/etc/service, just like se_tcp. Only shared memory connections (which
SE does not support) ignore the servicename. Having coded many ipcpip
style servers myself I can say the service is required and used as an
IP style connection is made through the named pipe.
Art S. Kagel
Alan Miner wrote:
>
> Installed Informix SE 7.24uc5 and 7.24ue5 on different boxes running RedHat 6.0. Used the trial version S/N and key. When connecting to "local_se" in dbaccess I get the same error message on both servers: "25591: Transport control received an invalid connection or address." When connecting to "sqlserv" it works fine.
>
> Any ideas? I have been through Infomrix tech support on this. Also have SE running on HPUX without any problems.
>
> DETAILS
> /home/informix/etc/sqlhosts
> local_se seipcpip echo2 sqlexec
> sqlserv sesoctcp echo2 se_tcp
> [blank line]
>
> /etc/services
> se_tcp 1525/tcp
>
> /etc/hosts
> 129.1.1.10 echo2
>
> env
> INFORMIXDIR=/home/infomrix
> INFORMIXSERVER=local_se
> PATH=/home/informix/bin:. . .
The point seems to be that the hostname for seipcpip must be what is
returned by uname. If it gives the fully qualified domain name, then the
sqlhosts must also contain the FQDN for seipcpip.
In the case of sesoctcp on the other hand the loopback address also works
for me (but not for seipcpip!).
Still it is not clear to me what you mean by "IP style connection" made
through the pipe or named pipe. IP has nothing to do with all this.
Normally for a named pipe (a FIFO?) you don't need a tcp port number or
host name.
On Fri, 19 May 2000, Art S. Kagel wrote:
> I believe that for ipcpip you need to have the servicename, sqlexec, in
> /etc/service, just like se_tcp. Only shared memory connections (which
> SE does not support) ignore the servicename. Having coded many ipcpip
> style servers myself I can say the service is required and used as an
> IP style connection is made through the named pipe.
>
> Art S. Kagel
>
> Alan Miner wrote:
> >
> > Installed Informix SE 7.24uc5 and 7.24ue5 on different boxes running RedHat 6.0. Used the trial version S/N and key. When connecting to "local_se" in dbaccess I get the same error message on both servers: "25591: Transport control received an invalid connection or address." When connecting to "sqlserv" it works fine.
> >
> > Any ideas? I have been through Infomrix tech support on this. Also have SE running on HPUX without any problems.
> >
> > DETAILS
> > /home/informix/etc/sqlhosts
> > local_se seipcpip echo2 sqlexec
> > sqlserv sesoctcp echo2 se_tcp
> > [blank line]
> >
> > /etc/services
> > se_tcp 1525/tcp
> >
> > /etc/hosts
> > 129.1.1.10 echo2
> >
> > env
> > INFORMIXDIR=/home/infomrix
> > INFORMIXSERVER=local_se
> > PATH=/home/informix/bin:. . .>
Tray with /etc/services sqlexec 1525/udp
David Stes wrote:
>
> The point seems to be that the hostname for seipcpip must be what is
> returned by uname. If it gives the fully qualified domain name, then the
> sqlhosts must also contain the FQDN for seipcpip.
>
> In the case of sesoctcp on the other hand the loopback address also works
> for me (but not for seipcpip!).
>
> Still it is not clear to me what you mean by "IP style connection" made
> through the pipe or named pipe. IP has nothing to do with all this.
No it does not. But Informix is coding using network style code, setting
up a UNIX domain Socket (class AF_UNIX), rather than managing the pipe
manually. The bind() system call requires a port number for this just like
for a TCP/IP connection setup and so the service name has to be in
/etc/services so that getservbyname will find it and return a port number.
> Normally for a named pipe (a FIFO?) you don't need a tcp port number or
> host name.
Assuming that you open the pipe just using open and manage the I/O and
handshaking yourself. Meanwhile setting it up as a UNIX domain socket you
can take advantage of precoded management and just treat it like a network
connection. Like I said, I've done it, very sweet.
Art S. Kagel
> On Fri, 19 May 2000, Art S. Kagel wrote:
>
> > I believe that for ipcpip you need to have the servicename, sqlexec, in
> > /etc/service, just like se_tcp. Only shared memory connections (which
> > SE does not support) ignore the servicename. Having coded many ipcpip
> > style servers myself I can say the service is required and used as an
> > IP style connection is made through the named pipe.
> >
> > Art S. Kagel
> >
> > Alan Miner wrote:
> > >
> > > Installed Informix SE 7.24uc5 and 7.24ue5 on different boxes running RedHat 6.0. Used the trial version S/N and key. When connecting to "local_se" in dbaccess I get the same error message on both servers: "25591: Transport control received an invalid connection or address." When connecting to "sqlserv" it works fine.
> > >
> > > Any ideas? I have been through Infomrix tech support on this. Also have SE running on HPUX without any problems.
> > >
> > > DETAILS
> > > /home/informix/etc/sqlhosts
> > > local_se seipcpip echo2 sqlexec
> > > sqlserv sesoctcp echo2 se_tcp
> > > [blank line]
> > >
> > > /etc/services
> > > se_tcp 1525/tcp
> > >
> > > /etc/hosts
> > > 129.1.1.10 echo2
> > >
> > > env
> > > INFORMIXDIR=/home/infomrix
> > > INFORMIXSERVER=local_se
> > > PATH=/home/informix/bin:. . .> >