Dear Zopers Since this morning I have witnessed a new error in my Zope application. It is a database with a ZPT interface that makes use of ZCatalog for browsing through its contents. When I do this I get an IOError now and then. When I refresh the same bits of data a second later the problem is gone. It is not predictable when this happens. Packing the ZODB (from 80MB to 5MB) did not help. This happens with Zope 2.7 on Win2K. Has anybody else experienced this before? Is it Zope or Windows (I have yet to test this on my Red Hat box) or a hardware problem? kind regards Andre Site Error An error was encountered while publishing this resource. *Error Type: IOError* *Error Value: [Errno 9] Bad file descriptor* ------------------------------------------------------------------------ Troubleshooting Suggestions * The URL may be incorrect. * The parameters passed to this resource may be incorrect. * A resource that this resource relies on may be encountering an error. For more detailed information about the error, please refer to the error log. If the error persists please contact the site maintainer. Thank you for your patience. -- ------------------------------------------------------------------------------ The disclaimer that applies to e-mail from TNO Physics and Electronics Laboratory can be found on: http://www.tno.nl/disclaimer/email.html ------------------------------------------------------------------------------
AP Meyer wrote at 2004-3-17 12:57 +0100:
Since this morning I have witnessed a new error in my Zope application. It is a database with a ZPT interface that makes use of ZCatalog for browsing through its contents. When I do this I get an IOError now and then. When I refresh the same bits of data a second later the problem is gone. It is not predictable when this happens. Packing the ZODB (from 80MB to 5MB) did not help.
This happens with Zope 2.7 on Win2K.
Has anybody else experienced this before? Is it Zope or Windows (I have yet to test this on my Red Hat box) or a hardware problem?
What did your log file tell you? If it does not tell you anything, configure your "error_log" to log exceptions to the log file. Look into your log file when the error occurs again. -- Dieter
participants (2)
-
AP Meyer -
Dieter Maurer