[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-GNUnet] gnunet 0.7.0: fslibtest fails

From: Vasil Dimov
Subject: Re: [bug-GNUnet] gnunet 0.7.0: fslibtest fails
Date: Mon, 21 Nov 2005 15:34:24 +0200
User-agent: Mutt/1.5.11

On Fri, Nov 18, 2005 at 04:53:05PM -0800, Christian Grothoff wrote:
> Since I don't have access to a BSD box and since it seems that our BSD 
> maintainer has abandoned the port, I don't see much that I can do to help you 
> based on this data at this point -- other than saying that the testcase 
> should succeed ;-).
That's useful information, now I know to focus on gnunetd,
not fslibtest when trying to figure out what's wrong, thanks!

> One thing that may help the diagnosis is running gnunetd with a higher 
> log-level and/or including the LOG output from gnunetd in the output (just 
> edit check.conf in the fs/lib/ directory) -- typically gnunetd should then  
> log some indication as to what was going wrong in fslibtest 
> (to /tmp/gnunet-check-fslib/logs).  With that info, we maybe able to figure 
> out what is going on.

Hmmz, I sent gnunetd's output with loglevel DEBUG. It can be seen on
https://gnunet.org/mantis/view.php?id=976, under "server output:".
The only highest level is EVERYTHING which only adds *a lot* of
useless(?) lines like:
EVERYTHING: No peers found for slot 177
EVERYTHING: No peers found for slot 173
EVERYTHING: No peers found for slot 167
EVERYTHING: No peers found for slot 166
EVERYTHING: No peers found for slot 148

It seems what the only message, relative to fslibtest's run is the
WARNING below:

Nov 17 08:39:13 MESSAGE: `gnunetd' startup complete.
Nov 17 08:39:20 WARNING: Unindexed ODB block 
 from offset 0 already missing from datastore.
Nov 17 08:39:22 INFO: shutdown request accepted from client

Can gnunetd be forced to log more detailed information?

Vasil Dimov

Attachment: pgpuocBH8wi7y.pgp
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]