Re: [Help-gnunet] gnunet-check segfaults (broken gdbm files?)

[Igor Wronsky]

On Tue, 9 Dec 2003, Markku Tavasti wrote:

> Ok, reboot, no big problem. Start running gnunet-check. Starts fine,
> founds errors since some files have been moved after indexing. But:
> Bad content indexed for A5811360B40FB308B9EA0828BBD2B693FB0CCDF3
> Will fix (deferred).
> Segmentation fault

You should use gdb to find out what actually caused the
segfault. Instructions are on the gnunet webpage, see
'reporting bugs'. If the segv is internal to gdbm, there
is not much to be done. If its not inside gdbm, we should
fix gnunet-check. So we need to know which one it is.

> I'm running with default configs, gdbm database. I suppose it is
> corrupted, what to do?

Last time I checked, a year ago or so, gdbm database
couldn't be fixed.

The good side of using MySQL is that the db can be fixed
from internal corruption, with some possible loss of data. In
any case thats better than rm -rf. We are not entirely sure
how reliable our mysql module is w.r.t. data preservation,
there may be some sequence of operations or some specific
operation that can lose data. I have personal indication
that blocks *can* go missing with mysql, atleast if tables
are repaired. Other than that, there has been no stability
problems or other traceable faulty operation reported that
would've been caused by mysql db.

> Is it hard to set up gnunet with mysql?

Hard is relative. I wouldn't say its too difficult.


Igor