Folks, Config: Zope 2.3.2 / Solaris 2.6 After 23 days of adding and removing files, we've bumped into a file descriptor table problem on our Solaris 2.6 platform. The situation was reported in a standard Zope error web response with the following contents: Error Type: OSError Error Value: [Errno 24] Too many open files: '/var/tmp/@12939.7266' Unfortunately, I was unable to "lsof" the crippled Zope instance. However, I have looked at the restarted instance and found twelve long-standing open files in the /var directory. Since file descriptors are a scarce resource in Solaris 2.6, I've jumped the ulimit value up to 256 and Zope is off and running again. Are long-standing temporary files a typical Zope signature? Did I miss a discussion of this topic? Regards, Dave
On Mon, 4 Jun 2001, Astheimer, David (GXS) wrote:
Are long-standing temporary files a typical Zope signature?
Not long-standing. Are you running any custom products? (Maybe something like ThreadSafeCounter?) Are you indexing a lot of stuff? I just saw Chris Withers mention that Zope writes big indexes to files so not to hog much memory... could be something like that?
participants (2)
-
Astheimer, David (GXS) -
Erik Enge