> horn@schaefer.math.wisc.edu (Jeffrey Horn) writes: > I am getting the following error message in Ingres > > ::[3988 , 002D4AF0]: Mon Jun 29 11:59:12 1992 - E_CLFE04_BS_ACCEPT_ERR Unable to accept incoming connection.System communication error: Too many open files. > > During a vision session, the screen just hangs when I try a compile. This > doesn't happen every time, but when it does it is really annoying. I have > to re-start the database. > > We just installed another package (non-ingres) that uses up some shared > memory and semaphores on the system. There does seem to be some correlation > between the times users are in this package and the times we have > these error messages. depending on your unix, there's probably a file-handle limit in the kernel config somewhere -- either that or the number of sockets available. since files/sockets and shared memory are allocated out of static memory they can end up competing for the same pool. try checking the config file for file/socket limits or total kernel memory (or shutting down the new application!). steve lembark Jeff - We've had this problem too. On a Decstation 3100 running Ultrix. We were told by Ingres Tech Support that the problem was an Ultrix limit of 64 open files per process. The server, then, can not open more than 64 files. We were seeing the problem when one developer used ABF/GO which opens lots of files and we also had other production users in the server. The ABF process would appear to hang, the other users would go on. We were told to try a second server, which we have done and it seems to work pretty well. However, our production server, still does have the problem sometimes. When we see the problem our server writes the above message (E_CLFE04_BS_ACCEPT_ERR ...) over and over to the errlog.log file filling 1 or 2 M of disk. VERY annoying. Now we have a production server and a development server. Our developer no longer has a problem, the production server does sometimes but the users don't seem to notice (I guess they don't hang). This problem cropped up when we move the machine into our user's office and they began to use the Xterm environment. Now they have several windows open etc, etc. Before the machine was elsewhere and the monitor was not being used. All users telneted in as vt100 terminals. Could this be a connection? -- Nina Boss Madison Academic Computing Center-University of Wisconsin Internet: ninab@macc.wisc.edu, NeXTmail w/attachments: ninab@zuchinni.macc.wisc.edu
© William Yuan 2000
Email William