[Zope-dev] Sporadic IOErrors...?

[Bjorn Stabell]

Thanks Shane.

This sounds very plausible.  I seem to recall that we started it in
debug mode, then disowned the process and exited.  That probably caused
debug to stdout to create this kind of error.  Now we should be able to
find the underlying error that caused it to try to write the error to
the first place. :)

> -----Original Message-----
> From: Shane Hathaway [mailto:shane@zope.com]=20
> Sent: Friday, April 04, 2003 23:41
> To: Bjorn Stabell
> Cc: zope-dev@zope.org
> Subject: Re: [Zope-dev] Sporadic IOErrors...?
>=20
>=20
> Bjorn Stabell wrote:
> > Hi Zope gurus,
> >=20
> > After upgrading to Zope 2.6.1 on Linux, when submitting forms, we=20
> > sometimes get this error:
> >=20
> >     Site Error
> >     ...
> >     exceptions.IOError
> >     ...
> >     Traceback:
> > 	Module ZPublisher.Publish, line 150, in publish_module
> > 	Module ZPublisher.Publish, line 114, in publish
> > 	Module Zope.App.startup, line 149, in zpublisher_exception_hook
> > 	Module Products.SiteErrorLog.SiteErrorLog, line 195, in raising
> > 	Module Products.SiteErrorLog.SiteErrorLog, line 206, in
> > 	_do_copy_to_zlog
> > 	Module zLOG, line 130, in LOG
> > 	Module ZLogger.ZLogger, line 16, in log_write
> > 	Module ZLogger.stupidFileLogger, line 27, in __call__
> > 	Module ZLogger.stupidFileLogger, line 90, in stupid_log_write
> > 	IOError: [Errno 5] Input/output error
> > 	...
> >=20
> > It's terrible hard to debug as it happens sporadically, not=20
> > consistently, and we don't get any more debug info than this.  Even=20
> > worse, we have a standard-error-message that emails errors=20
> to us, but=20
> > it fails to do anything in this case.  Any ideas what could=20
> be wrong=20
> > and how to troubleshoot better?  The disks have plenty of=20
> free space;=20
> > after restarting, or waiting a while, things work again.
>=20
> This usually means Python is trying to write to stdout or stderr and=20
> failing because stdout/stderr don't go anywhere.  Make sure=20
> you have a=20
> log file configured (using the EVENT_LOG_FILE environment variable,=20
> rather than the old STUPID_LOG_FILE).
>=20
> Shane
>=20
>=20