On Fri, Feb 21, 2003 at 09:47:13AM -0800, [EMAIL PROTECTED] wrote:There is something going wrong. Around build 640 I was able after a few hours to fill about half my bandwidth limit with 10 to 30 incoming connections handled per hour and find most sites. Since then, with all subsequent builds, somewhere between one in a thousand and 1 in a hundred thousand connection attempts succeeds, I can only rarely find any freesites and Frost gets about one message a day or none. No incoming connection attempts, or perhaps one or two bunches of a dozen per day. I have reseeded frequently, left the node running for up to 3 days, checked connections to the node port via telnet from another ISP, used all the defaults in freenet.conf apart from average bandwidth limits (which are not approached) and clients exempt from them. Latest Sun Java. Only distinctive feature is it is a low power machine with 256MB data store, but load average varies only from 0.6 to 4.
My connection to the Internet is �bersimple. No nasty NAT, no proud proxy, no rough router. A normal ADSL like millions of people have.
Build 561 freenet.ini: ipAddress=
Environment: Architecture and Operating System Architecture x86 Available processors 1 Operating System Windows 2000 OS Version 5.0
Java Virtual Machine JVM Vendor Sun Microsystems Inc. JVM Name Java HotSpot(TM) Client VM JVM Version 1.4.1_01-b01
Free space in the data store approx. 4 GiB
Firewall settings are working, as there were times when I had more incoming requests.
Here is what I do:
1. Connect to the Internet 2. Start Freenet 3. "Autodetection of IP addresses" detects my IP address correctly! 4. Receiving incoming connections, e.g. 12 per minute. 5. ARK sequence number stays "0" and even I CAN'T retrieve this [EMAIL PROTECTED],bla/0
This is normal. There is no need to insert an ARK unless your IP changes.
6. Browsing freesites works. Even retrieving stuff that isn't in my data store.
7. Excerpts from the log regarding announcements (including two "successfully"):
Announcing, QThread-25): Found 3 announcement targets for this node.
Announcing, QThread-25): Announcement failed to BLABLA at depth 15.
Announcing, QThread-25): Announcement failed to BLABLA at depth 15.
Announcing, QThread-28): Announcement failed to BLABLA at depth 15.
Announcing, QThread-124): Found 3 announcement targets for this node.
Announcing, QThread-124): Announcement failed to BLABLA at depth 12.
Announcing, QThread-124): Announcement failed to BLABLA at depth 12.
Announcing, QThread-124): Announcement failed to BLABLA at depth 12.
Announcing, QThread-204): Found 3 announcement targets for this node.
Announcing, QThread-204): Announcement failed to BLABLA at depth 9.
Announcing, QThread-204): Announcement failed to BLABLA at depth 9.
ExecuteAnnouncement, QThread-197): Announcement attempt failed: The announcement was restarted too many times.
Announcing, QThread-197): Announcement failed to BLABLA at depth 9.
Announcing, QThread-300): Found 3 announcement targets for this node.
Announcing, QThread-300): Announcement failed to BLABLA at depth 6.
Announcing, QThread-300): Announcement failed to BLABLA at depth 6.
ExecuteAnnouncement, QThread-306): Announcement attempt failed: The announcement was restarted too many times.
Announcing, QThread-322): Announcement failed to BLABLA at depth 6.
Announcing, QThread-346): Found 3 announcement targets for this node.
Announcing, QThread-346): Announcement failed to BLABLA at depth 3.
Announcing, QThread-346): Announcement failed to BLABLA at depth 3.
NewInitialRequest, QThread-338): Scheduling post-announcement request on chain BLABLA, for key BLABLA
NewInitialRequest, QThread-338): Scheduling post-announcement request on chain BLABLA, for key BLABLA
Announcing, QThread-338): Announced node successfully to BLABLA at depth 3.
Announcing, QThread-533): Found 2 announcement targets for this node.
Announcing, QThread-554): Announcement failed to BLABLA at depth 3.
Announcing, QThread-501): Announcement failed to BLABLA at depth 3.
Announcing, QThread-587): Found 2 announcement targets for this node.
NewInitialRequest, QThread-639): Scheduling post-announcement request on chain BLABLA, for key BLABLA
Announcing, QThread-639): Announced node successfully to BLABLA at depth 2.
Announcing, QThread-644): Announcement failed to BLABLA at depth 2.
How old is your seednodes file? If you enable logLevel=debug, you get much more detailed info... it is quite common that the reason for all these announcement failures is connection failed...
8. While Freenet is running I changed my IP address by disconnecting and reconnecting.Hmmm. Shift+reload? You're sure it hasn't changed?
9. Although there happened some "Checkpoint: Autodetection of IP addresses" tasks, my IP address on the environment page stays the same, previous one.10. "Incoming Connections" drops to 0.HMMMMM.
And what now?
Is there anything in the code which might make individual connections fail with a slow processor??? Anything else I can measure or check on (not much room for log files, and the Freenet host is not allowed to have a network file system)?
--
Roger Hayter
_______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
