listener-thread: err = -27001:
Posted in 2010
Topics: General Discussion
Any help on this error? 00:00:39 listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt. 00:10:39 listener-thread: err = -408: oserr = 0: errstr = : Invalid message type received from the sqlexec process.oca Thanks a lot, juan roca
Hello. Most kind of 27001 errors are related to network problems, like an external connection with some "mistaken" thing, you could get more information based on your operational system logs. Regards. Em Qua, 2010-05-19 Ã s 04:07 -0400, JUAN ROCA escreveu: > Any help on this error? > > 00:00:39 listener-thread: err = -27001: oserr = 0: errstr = : Read error > occurred during connection attempt. > > 00:10:39 listener-thread: err = -408: oserr = 0: errstr = : Invalid > message type received from the sqlexec process.oca > > Thanks a lot, > > juan roca > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > Alexandre Marini Especialista DBA msn: alexandre_marini@hotmail.com SEFAZ-MS / SGI-UGSGR / Sistemas IBM-Informix IBM Certified Professional - Informix Dynamic Server v.10 / v.11
Any help on this error? 00:00:39 listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt. 00:10:39 listener-thread: err = -408: oserr = 0: errstr = : Invalid message type received from the sqlexec process.oca Thanks a lot, juan roca Response: The 27001 error generally indicates that the engine believed there should have been data on the other end of the tcp/ip connection and it went to read from the end point, and it returned 0 bytes so the connection attempt errors out. The 408 would mean that we expect a certain message to be received from an informix client in a certain format, however, when the engine read the packet, it was not the correct type/format message. Both these errors could indicate some non-informix client attempting to connect to the server and send data to the port the server is listening on. In the case of the 27001 just a simple connect() and close from any network client would show up as a 27001 error on the listener thread. In the 408 case, that network client would have to do the connect() and then actually do a write on that end point to get the listener thread to generate a 408 error. You'd probably have to use network packet sniffing to try and verify if non-informix clients were attempting to connect to the servers listener threads network port. Although in newer server releases (I don't recall of the top of my head when that was added) I believe there is some debug code that can be turned on to get the IP address of the incoming client connection request, which can at least help try and determine if end up with some IP address that you know shouldn't be connecting to the server. Jacques Renaut IBM Informix Advanced Support APD Team
Tracing client IP address with xtrace http://www-01.ibm.com/support/docview.wss?uid=swg21162482 --- Em qua, 19/5/10, JACQUES RENAUT <jrenaut@us.ibm.com> escreveu: De: JACQUES RENAUT <jrenaut@us.ibm.com> Assunto: Re: listener-thread: err = -27001: [20188] Para: ids@iiug.org Data: Quarta-feira, 19 de Maio de 2010, 11:11 Any help on this error? 00:00:39 listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt. 00:10:39 listener-thread: err = -408: oserr = 0: errstr = : Invalid message type received from the sqlexec process.oca Thanks a lot, juan roca Response: The 27001 error generally indicates that the engine believed there should have been data on the other end of the tcp/ip connection and it went to read from the end point, and it returned 0 bytes so the connection attempt errors out. The 408 would mean that we expect a certain message to be received from an informix client in a certain format, however, when the engine read the packet, it was not the correct type/format message. Both these errors could indicate some non-informix client attempting to connect to the server and send data to the port the server is listening on. In the case of the 27001 just a simple connect() and close from any network client would show up as a 27001 error on the listener thread. In the 408 case, that network client would have to do the connect() and then actually do a write on that end point to get the listener thread to generate a 408 error. You'd probably have to use network packet sniffing to try and verify if non-informix clients were attempting to connect to the servers listener threads network port. Although in newer server releases (I don't recall of the top of my head when that was added) I believe there is some debug code that can be turned on to get the IP address of the incoming client connection request, which can at least help try and determine if end up with some IP address that you know shouldn't be connecting to the server. Jacques Renaut IBM Informix Advanced Support APD Team ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.
Hi Juan, It seems you are trying to connect to a remote IDS server. What client software are you using for the connection ? Is that client version in "phase" with the target server version ? Regards, Henri MOUKOURI On 19/05/2010 09:07, JUAN ROCA wrote: > Any help on this error? > > 00:00:39 listener-thread: err = -27001: oserr = 0: errstr = : Read error > occurred during connection attempt. > > 00:10:39 listener-thread: err = -408: oserr = 0: errstr = : Invalid > message type received from the sqlexec process.oca > > Thanks a lot, > > juan roca > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > >