25506 sqlexecd error message
Posted in 1995
Topics: Connectivity: ESQL/C, 4GL & Embedded SQL
We are having a problem with 5.03.01 UC1 of Informix Online and ISTAR It seems that the user goes away but the utmp entry indicates that there is a dead process. Here is how the services section is set up for the connections. ------------------------------------------------------------------ /etc/services ae 901/tcp cust 902/tcp dtla 903/tcp dtlb 904/tcp dacca 905/tcp daccb 906/tcp These are the versions of Informix we are using. ----------------------------------------------------- INFORMIX EMBEDDED SQL for C Version 5.03.UC1 Copyright (C) 1984-1994 Informix Software, Inc. INFORMIX-4GL Version 4.12.UE1 Copyright (C) 1984-1994 Informix Software, Inc. INFORMIX-SQL Version 4.12.UE1 Copyright (C) 1984-1994 Informix Software, Inc. INFORMIX-OnLine Version 5.03.UC1 Copyright (C) 1986-1994 Informix Software, Inc. INFORMIX-STAR Version 5.03.UC1 Copyright (C) 1988-1994 Informix Software, Inc. This is what we are getting in our logs when it occurs. -------------------------------------------------------------------- 25506 The sqlexecd daemon cannot accept a connection on the socket.: Connection timed out sqlexec kbncr12.ims.att.com 1o0u -naesrv sqlexec kbncr12.ims.att.com 1cjs -naesrv sqlexec kbncr12.ims.att.com 0755 -naesrv sqlexec kbncr12.ims.att.com 17op -naesrv sqlexec kbncr12.ims.att.com 087o -naesrv sqlexec kbncr12.ims.att.com 1fls -naesrv sqlexec kbncr12.ims.att.com 10sp -naesrv sqlexec kbncr12.ims.att.com 1mv6 -naesrv 25506 The sqlexecd daemon cannot accept a connection on the socket.: Connection timed out sqlexec kbncr12.ims.att.com 1hk2 -naesrv sqlexec kbncr12.ims.att.com 1shz -naesrv sqlexec kbncr12.ims.att.com 00sx -naesrv sqlexec kbncr12.ims.att.com 07c5 -naesrv sqlexec kbncr12.ims.att.com 100m -naesrv 25523 The sqlexecd daemon cannot bind the network structures.: System error: Address already in use Running menu for front end application. Connections are client/server locally on the system not across the the network. Synonyms are being used. Has anyone out there experienced this error with ISTAR? TCP looks just fine and works great (just not the port that ISTAR happens to want to run on). The other users are left working just fine on the system until they log out of the database and try to get access again. When they do they are met with an error message about being unable to connect to the network. Thanks for any assistance, Rb.