On Wed, 2005-10-19 at 10:41 -0400, Nick Mathewson wrote:
> On Tue, Oct 18, 2005 at 10:55:22AM +0200, Marco Calamari wrote:
> [...]
> > LOG.warn("Couldn't connect to %s",self.address)
> > File "/usr/lib/python2.3/site-packages/mixminion/Common.py", line
> > 1010, in warn
> > self.log("WARN", message, *args)
> > File "/usr/lib/python2.3/site-packages/mixminion/Common.py", line
> > 974, in log
> > self._log(severity, message, args)
> > File "/usr/lib/python2.3/site-packages/mixminion/Common.py", line
> > 995, in _log
> > h.write(severity, m)
> > File "/usr/lib/python2.3/site-packages/mixminion/Common.py", line
> > 841, in write
> > self.file.flush()
>
> Oh, strange. It looks like it's giving an EIO error when it's trying
> to write a message to the log file. Could your disk be full or
> something? (EIO is a very vague message; what platform is this on?)
It is a pbox, a Soekris 4801 board with a Geode 386-like processor
and an emulated IDE disk on flash disk.
Linux Debian Sarge I386 w/ 2.6.8.1 standard kernel
This error however happens, less frequently, on standard pc hardware
with real ide disk too.
So a wear of some flash memory block due to too much write on the
simulated fs is not my first guess.
Some race condition on connection attempt to dead nodes ?
Ciao. Marco
>
> yrs,
--
"Oggi e' il domani di cui ci dovevamo preoccupare ieri."
Attachment:
signature.asc
Description: This is a digitally signed message part