Informix Error 27001
27001; connection attempt Technote (troubleshooting) Problem(Abstract) This article describes three common causes for listener-thread: err = -27001: Read error occurred during connection attempt errors. Symptom This error appears in the IBM Informix Dynamic Server (IDS) message log file (ONCONFIG configuration file parameter MSGPATH) and users are not able to connect to the database server.: listener-thread: err = -27001: Read error occurred during connection attempt. Resolving the problem Common causes and solutions for the error are: 1. The connectivity files in the /INFORMIXTMP directory are not removed. The files are in the form of : VP. server_name .0100a server_name Database server name as was set in INFORMIXSERVER environment variable and associated with the tcp connections. Solution: Stop the database server, remove the files from the /INFORMIXTMP directory, and start the database server. 2. The ONCONFIG file settings for the NETTYPE parameter are not correct. This error is widely seen involving tcp network connections when the VP class in the NETTYPE setting is set for CPU vp. Solution: As a work around Change the vp class setting for the NETTYPE configuration parameter from CPU to NET. Factors outside of Informix that can cause 27001 3. An operating system resource limit was reached. Kernel parameters settings require changes. Solution: Check and possibly increase settings for the following kernel parameters or parameters equivalent to them depending on Unix platform: NOFILES SEMMNU NFILES MAXFILES MAXFILE_LIM 4. Network problem. Perhaps the network is busy or packets are being lost. Monitor network and alleviate the problem. 5. Hardware involved in the system ( network card, cables, router, and so on ) is intermittently failing and causing the error. Document information More support for: Informix Servers Software version: 7.3, 9.4, 10.0, 11.1, 11.5 Operating system(s): AIX, HP-UX, Linux, OS X, Solaris, Windows Reference #: 1165598 Modified date: 2004-05-03 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
Server Version 7.30.UC2 on UnixWare 7.0.1. We keep getting frequent Informix freezes on our server caused by the error numbers 27554, 27001I. In this state connections to the application fail:- listener-thread: err = -27001 :oserr = 0 : errstr =: Read error occurring during connection attempt Our NETTYPE is set as tlitcp,1,300,NET We have also tried to reduce the INFORMIXCONTIME to 60 from 300 but there is no change. Can somebody help us please. Regards Tariro Mukanyi Support Consultant - ICL Zimbabwe * 263-4-252540/55 (Bus) * 263-4-703050 (Fax) sending to informix-list... Thread Tools Show Printable Version Email this Page… Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode August 5th,08:17 AM #1 RE:Listener -thread error -27001 Hi We are currently http://www-01.ibm.com/support/docview.wss?uid=swg21165598 using Informix Dynamic Server Version 7.30.UC2 on UnixWare 7.0.1. We keep getting frequent Informix freezes on our server caused by the error numbers 27554, 27001I. In this state connections to the application fail:- listener-thread: err = -27001 :oserr = 0 : errstr =: Read error occurring during connection attempt Our NETTYPE is set as tlitcp,1,300,NET We have also tried to reduce the INFORMIXCONTIME to 60 from 300 but there is no change. Can somebody help us please. Regards Tariro Mukanyi http://www.justskins.com/forums/listener-thread-error-27001-a-96269.html Support Consultant - ICL Zimbabwe * 263-4-252540/55 (Bus) * 263-4-703050 (Fax) sending to informix-list Mukanyi Tariro Guest August 5th,02:50 PM #2 Re: Listener -thread error -27001 Try reducing INFORMIXCONTIME to just a few seconds (set on the client side!). Set it as low as you can. You can use onstat -g ath to see how long the soctcplst thread will be sleeping. During this time nobody else will be able to connect: Threads: tid tcb rstcb prty status vp-class name 12 1093d4e0 0 3 sleeping secs: 9 1cpu soctcplst Maybe you also can find out why it happens so often. What kind of clients do you have? This is normally caused by a client machine that crashes (often a PC) before the initial packages between the client and the server are exchanged or by a hanging network connection. Michael Mukanyi Tariro wrote: > Hi > > We are currently using Informix Dynamic Server Version 7.30.UC2 on UnixWare > 7.0.1. We keep getting frequent Informix freezes on our server caused by the > error numbers 27554, 27001I. In this state connections to the application > fail:- > > listener-thread: err = -27001 :oserr = 0 : errstr =: Read error occurring > during connection attempt > > Our NETTYPE is set as tlitcp,1,300,NET > We have also tried to reduce the INFORMIXCONTIME to 60 from 300 but there is > no change. > > Can somebody help us please
Join INTELLIGENT WORK FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer http://www.tek-tips.com/viewthread.cfm?qid=898334 / IT professional?Join Tek-Tips Forums! Talk With Other Members http://www.sqlserverf1.com/informix-error-messages-and-error-codes-from-error-27001-to-27002/ Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to informix error receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki informix error 27001 reStructuredText code below into your site. Informix solutions Forum at Tek-Tips HomeForumsProject and Data ManagementData Management Programming ToolsInformix solutions Forum Error listener-thread: err = -27001 in online.log thread404-898334 Forum Search FAQs Links MVPs Error listener-thread: err = -27001 in online.log Error listener-thread: err = -27001 in online.log thein (Programmer) (OP) 11 Aug 04 12:14 Does anyone know the cause of this error in online.log.This slows down conciderably the response time11:01:41listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.11:02:44listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.RegardsThein RE: Error listener-thread: err = -27001 in online.log appi (IS/IT--Management) 12 Aug 04 03:05 Did you try to ask your system with finderr -27001???finderr is an Informix Tool and might be installes if you install the Informix Toolshth RE: Erro
Informix Error Messages and Error Codes From Error 27001 to 27002 March 17, 2015 SQLServerF1 Leave a comment Informix Error Code -27001 Read error occurred during connection attempt. This error can occur on either the client or database server side. When you encounter this error on the client side, it indicates that a network I/O error occurred when the client tried to connect to a database server. Probably the connection attempt timed out because the database server or the network was very busy, too many clients were attempting to connect to the database server simultaneously, or the database server was taken off-line during the connection attempt. If you are using Informix Dynamic Server or INFORMIX-OnLine Dynamic Server, verify that the database server is still on-line. If you are using INFORMIX-SE, verify that the sqlexecd daemon for the database server is still running. Use the environment variables INFORMIXCONTIME and/or INFORMIXCONRETRY on the client side to increase the connection time and number of retry attempts. When you encounter this error on the database server side, it is a warning that a network I/O error is detected while the database server is accepting a connection request from a client. This error usually occurs when the database server or the network is very busy or when too many clients are trying to connect to the database server at once. The database server might be taking so long to respond to a client that the client's connection request timed out before the connection is complete. Or possibly a client terminated its connection attempt before the connection is completely established. If this error is seen only occasionally in the server message log, it is just a warning. No corrective action is required on the server side. If this error occurs frequently on a database server that runs on a host with multiple processors, you might want to tune the d