u Uler ([EMAIL PROTECTED]) wrote:

> > 30-Jun-02 3:47:03 AM (freenet.node.rt.DataObjectRoutingStore, main): bad
> > reference while resolving: 0x0 : d1d585f4b776ecc9667c1701a654ca01bf146134
> > freenet.node.BadReferenceException: NodeReference self signature check
> > failed.

I think the error message quoted above is actually being produced while
Freenet is processing the seednodes.ref file, which contains a list of
node refs (public keys) for *other* nodes.  One or more of the node refs
in that file is probably corrupted, which causes Freenet to ignore it,
and to produce that error message.  If I'm right, then we can safely
ignore the message.

> Truthfully, I'm not sure what it means. But it has something to do with your
> node's own nodereference, which is located in the myOwn.ref file in the main
> Freenet directory.

The file myOwn.ref is created by the Windows installer as a convenience
for people who want to share their node reference with others.  That file
is not read by Freenet at all.

The node's private key is in the node_XXXXX file.  That is the file
that Freenet reads upon startup.  The myOwn.ref file is basically
the public key which matches it.

> If you keep getting this kind of error AND your node
> doesn't start working after you've tried the above, you may want to consider
> DELETING the myOwn.ref file WHILE YOUR NODE IS TURNED OFF. When you restart
> your node, this file should be recreated correctly.

That will have no useful effect.  Also, I'm pretty sure that Freenet
will *not* re-create that file automatically simply by being executed.
You'd have to use the --export switch:

Command-line switches
---------------------
  -h|--help                prints this help message
  --system                 prints JVM properties
  -v|--version             prints out version info
  --manual                 prints a manual in HTML
  -x|--export <file>|-     exports a signed NodeReference
  -s|--seed <file>|-       seeds routing table with refs
  -c|--config <file>       generates or updates config file
  -p|--paramFile <file>    path to a config file in a non-default location

If you just install Freenet's jar files on a Unix box and set it up
according to the readme files, you don't get a myOwn.ref file.  You
have to run "CLASSPATH=mumble java freenet.node.Main --export myOwn.ref"
to get one.  The Windows installer does that for you.

-- 
Greg Wooledge                  |   "Truth belongs to everybody."
[EMAIL PROTECTED]              |    - The Red Hot Chili Peppers
http://wooledge.org/~greg/     |

Attachment: msg00809/pgp00000.pgp
Description: PGP signature

Reply via email to