[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Help-gnunet] Database corrupted
From: |
Ludovic Courtès |
Subject: |
Re: [Help-gnunet] Database corrupted |
Date: |
Sat, 12 Jun 2004 23:21:57 +0200 |
User-agent: |
Mutt/1.5.4i [Guile enabled] |
Hi,
44 days, 21 hours, 28 minutes, 11 seconds ago,
Christian Grothoff wrote:
> First I'd suggest looking at the log (~/.gnunet/log). Also you can try
> starting gnunetd with "-d -L DEBUG" in which case the error messages are
> printed to the terminal (gnunetd won't daemonize with "-d").
Well, it's been some time since I last wrote about my problems. ;-)
Anyway, here's what happens :
May 8 20:23:58 gnunetd up and running
May 8 20:23:59 WARNING: getIndexedFileName called with index out of bounds
(35)
May 8 20:23:59 FAILURE: Database inconsistent! (index points to invalid
offset (35)
May 8 20:23:59 WARNING: getIndexedFileName called with index out of bounds
(35)
May 8 20:23:59 FAILURE: Database inconsistent! (index points to invalid
offset (35)
And this goes on and on. `gnunet-check' complains likewise:
May 8 20:02:07 WARNING: getIndexedFileName called with index out of bounds
(33)
Bad CHKS content indexed for 25663B30F063C263AC60DB9D9284B5FB89D7FE3F Will
fix (deferred).
May 8 20:02:07 WARNING: getIndexedFileName called with index out of bounds
(34)
Bad CHKS content indexed for B8D7006A023B7CEFC3F6C262F79EC0C96323D06E Will
fix (deferred).
Is there a way to repair the database? Would `gnunet-convert' still be
able to convert it into a MySQL database for instance?
Thanks,
Ludovic.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [Help-gnunet] Database corrupted,
Ludovic Courtès <=