I'm having terrible trouble gettting Freenet 0.3.9.2 to work with Mac OS
X 10.1. The node starts up, but then I can't retrieve any keys. Fproxy
is there, because I can browse to 127:0.0.1:8081,  but that's as far as
I get.    When trying to get something, eventually it will time out with
this message:

--->8---
Network Error

Couldn't retrieve key: MSK@SSK@2vz8xnhEJyJOlBVNfBEOWaohQFEQAgE/freesite//
Hops To Live: 999
--->8---

Nothing will retrieve and this is the only line that ever gets put in 
freenet.log:

--->8---
Oct 20, 2001 4:39:52 PM:Freenet.node.Node:Normal:Freenet Core running on 
49932 (build 392)
--->8---

  I am able to run Freenet fine under Windows.

Also, I'd like to setup a .freenetrc file.  When I generate one, then
I really get problems:

--->8---
Freenet.ListenException
         at Freenet.transport.tcpListener.<init>(tcpListener.java)
         at java.lang.reflect.Constructor.newInstance(Native Method)
         at Freenet.support.Loader.getInstance(Loader.java)
         at Freenet.support.Loader.getInstance(Loader.java)
         at Freenet.ListenerFactory.listen(ListenerFactory.java)
         at Freenet.client.ServletHandler.<init>(ServletHandler.java)
         at Freenet.node.ServiceLauncher.<init>(ServiceLauncher.java)
         at Freenet.node.Node.startNode(Node.java)
         at Freenet.node.Node.main(Node.java)
Freenet.ListenException
         at Freenet.transport.tcpListener.<init>(tcpListener.java)
         at java.lang.reflect.Constructor.newInstance(Native Method)
         at Freenet.support.Loader.getInstance(Loader.java)
         at Freenet.support.Loader.getInstance(Loader.java)
         at Freenet.ListenerFactory.listen(ListenerFactory.java)
         at Freenet.client.ServletHandler.<init>(ServletHandler.java)
         at Freenet.node.ServiceLauncher.<init>(ServiceLauncher.java)
         at Freenet.node.Node.startNode(Node.java)
         at Freenet.node.Node.main(Node.java)
Freenet.ListenException
         at Freenet.transport.tcpListener.<init>(tcpListener.java)
         at java.lang.reflect.Constructor.newInstance(Native Method)
         at Freenet.support.Loader.getInstance(Loader.java)
         at Freenet.support.Loader.getInstance(Loader.java)
         at Freenet.ListenerFactory.listen(ListenerFactory.java)
         at Freenet.client.ServletHandler.<init>(ServletHandler.java)
         at Freenet.node.ServiceLauncher.<init>(ServiceLauncher.java)
         at Freenet.node.Node.startNode(Node.java)
         at Freenet.node.Node.main(Node.java)
--->8---

So I suspect something is wrong. :)  But what could it be?

I've isolated those Exceptions to these lines in the config file:

--->8---
# Set to Freenet.contrib.fcp.FCPHandler to start FCP automatically with 
the node.
services.fcp.class=Freenet.contrib.fcp.FCPHandler
services.fcp.allowedhosts=127.0.0.1
services.fcp.port=8082

# Set to Freenet.contrib.fproxy.HttpHandlerServlet to start FProxy 
automatically with the node
services.fproxy.class=Freenet.contrib.fproxy.HttpHandlerServlet
services.fproxy.allowedhosts=127.0.0.1
services.fproxy.port=8081
services.fproxy.doFiltering=true
services.fproxy.passthroughMimeTypes=text/plain,image/jpeg,image/gif,image/
png,application/octet-
stream,application/zip,audio/basic,audio/midi,audio/mpeg,audio/x-
aiff,audio/x-wav,image/cgm,image/g3fax,image/tiff,image/x-
xbinmap,image/x-xpixmap,image/x-
xwindowdump,application/unknown,image/pjpeg,application/x-debian-package

# Set to Freenet.contrib.xmlrpc.XmlRpcServlet to start XML-RPC 
automatically with the node.
services.xmlrpc.class=Freenet.contrib.xmlrpc.XmlRpcServlet
services.xmlrpc.allowedhosts=127.0.0.1
services.xmlrpc.port=6690
--->8---

If I leave those lines out of the .freenetrc (or don't have a 
.freenetrc),
then I don't get the ListenerExceptions.

I'm almost certain this is not a firewall issue because Freenet works
on my other computers that are behind it.

Any ideas?

Thanks for your help in advance.

Zach


_______________________________________________
Support mailing list
[EMAIL PROTECTED]
http://lists.freenetproject.org/mailman/listinfo/support

Reply via email to