Re: [Help-gnunet] Re: gnunetd suddenly very unstable

[Christian Grothoff]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 24 September 2002 06:26 pm, Christian Drechsler wrote:
> hi there!
>
> i found the real error now when i started gnunetd -d. now i can see:
>
> gdbm fatal: lseek error
>
> actually, i don't know what an lseek is; X-) but i'm just running
> gnunet-check -a, maybe that will help.

Well, gdbm is the database that we are using, and an lseek error can only mean 
that the database was corrupted (beats me how/why, I didn't write gdbm, we're 
just using it). gnunet-check-a may not be able to fix that by itself, you may 
have to delete the gdbm database (~/.gnunet/database.gdbm) and then run 
"gnunet-check -a" to regenerate it (there will be some loss of data, though). 

About the indirection table full, did you run 0.4.6c? Finally, the message:

Sep 25 00:56:16 ROUTING: Query is pending, not forwarded, no local lookup

is no error and not even a warning, it's perfectly happy normal operation, so 
don't worry about it.

Christian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9kP/E9tNtMeXQLkIRAkNpAJ9PDmynElb5AFfl+GC33EErgxGnfwCePe+C
UqZeZYh0KAm6S89GxQ0h0n0=
=qQio
-----END PGP SIGNATURE-----