Re: [freenet-support] Corrupt node.crypt and persistant-temp

2013-10-14 Thread Dennis New 
On Mon, 14 Oct 2013 00:39:05 -0400, Steve Dougherty wrote:
 On 10/10/2013 08:56 AM, james kaufman wrote:
  I'm not sure what I've done wrong but I so often find myself with a
  message along the lines of the node.db40.crypt and
  persistant-temp-***  can't be started(I think).  The only way I seem
  to be able to fix it is to copy a backup copy of freenet (or
  reinstall of course) Thing is it happens every few days at times,
  like right now..  freenet is happily working though and it doesn't
  happen until I shutdown for whatever reason which seems to go fine
  until I try and start it back up. Stupidly I overwrote the log file,
  the only message that was different and at the time it happened this
  time was something along the lines of cleaning chk(something)
  store... this was the first time the node and pers-temp message
  happened while freenet was actually running.
  
  This has been happing for a long time so many versions, and a lot of
  clean OS installs of my PC etc..  any clues as to what is going on
  on my pc to cause this or how I can minimize it happening ?   My
  poc is even running new hardware now but it still happens a lot.
 
 I'm sorry Freenet is so unstable for you! That's certainly not
 supposed to happen, and I don't know off the top of my head what
 could be causing it for sure.
 
 Do you hibernate your machine, or might your hard drive be failing and
 corrupting files? It's also possible that it's a bug in Freenet or the
 database it uses, though I haven't known such problems to happen every
 single shutdown.
 
 What operating system are you using?
 
 If you are able to get a list of steps to reproduce the problem it
 will become practical to fix the root cause.

I'm pretty confident that there are some pretty serious bugs in the
db4o code. It seems to happen to everyone, at some point. Happened to
me a few days ago with a large download. Or perhaps with too many
downloads in the queue. Hopefully the reproduceability in this case
will help.
___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-requ...@freenetproject.org?subject=unsubscribe

Re: [freenet-support] Corrupt node.crypt and persistant-temp

2013-10-14 Thread james kaufman 

 
 Date: Mon, 14 Oct 2013 08:19:03 -0400
 From: denn...@dennisn.dyndns.org
 To: support@freenetproject.org

  
  Do you hibernate your machine, or might your hard drive be failing and
  corrupting files? It's also possible that it's a bug in Freenet or the
  database it uses, though I haven't known such problems to happen every
  single shutdown.
  
  What operating system are you using?
  
  If you are able to get a list of steps to reproduce the problem it
  will become practical to fix the root cause.
 
 I'm pretty confident that there are some pretty serious bugs in the
 db4o code. It seems to happen to everyone, at some point. Happened to
 me a few days ago with a large download. Or perhaps with too many
 downloads in the queue. Hopefully the reproduceability in this case
 will help.
 ___
Interesting because it had been fine up until the point where I added a lot of 
downloads, about 40GB, 102 files. So it's been a struggle getting through them 
with the corruption happening so that seems to be a main trigger for it on my 
end.  I've put logging on to debug so hopefully it catches something.   
  ___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-requ...@freenetproject.org?subject=unsubscribe