RE: [freenet-support] Announcement problem
Nope, that is not it. I am *pretty* sure that this is the way: When announcing your node will send an announcement message with a specific HTL to 3 of the nodes in you routing table.. These three will in their turn distribute the announcement on to the best match in their routing table.. and so on until the HTL becomes zero.. Much like a plain insert. /N -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: den 11 februari 2003 15:50 To: Niklas Bergh Subject: RE: [freenet-support] Announcement problem At 12.53 11/02/03 +0100, you wrote: >I have seen that earlier too but I haven't noticed it for a long time >now.. > >I think that if your node has been running earlier and because of that >is present in other nodes routingtables and thereby recieveing incoming >connections everything should start working because of that... This is what I find strange; after announcement, I must be in routing tables of all nodes that are in my routing table this is the supposed way things works, isn't it ? Ciao. Marco >/N > >-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED]] On Behalf Of >[EMAIL PROTECTED] >Sent: den 11 februari 2003 11:36 >To: [EMAIL PROTECTED] >Subject: Re: [freenet-support] Announcement problem > > >At 02.45 11/02/03 -0500, you wrote: >>On Mon, 2003-02-10 at 20:07, Greg Wooledge wrote: >>> Build 611? Are you sure about that? I have made contact with >>> (unstable) nodes with build numbers as high as 663. >>> >>> Are you also seeing your problem with the stable builds? >> >>Sorry for the typo... that should say 661. Also tried it tonight with >>556: no successful announcements, same types of exceptions I included >>before. > >I don't know if this is significant, but in the last couple of month >my fresly bootsrapped node (now stable 552) has no traffic until I do >some retrieve with fproxy; then it begin to have traffic that >stabilize in a couple of hours. > >HTH. Marco > > >-- >+ il Progetto Freenet - segui il coniglio bianco+ >* the Freenet Project - follow the white rabbit* >* Marco A. Calamari[EMAIL PROTECTED] www.marcoc.it * >* PGP RSA: ED84 3839 6C4D 3FFE 389F 209E 3128 5698 * >+ DSS/DH: 8F3E 5BAE 906F B416 9242 1C10 8661 24A9 BFCE 822B + > > > >___ >Support mailing list >[EMAIL PROTECTED] >http://hawk.freenetproject.org:8080/mailman/listinfo/support -- + il Progetto Freenet - segui il coniglio bianco+ * the Freenet Project - follow the white rabbit* * Marco A. Calamari[EMAIL PROTECTED] www.marcoc.it* * PGP RSA: ED84 3839 6C4D 3FFE 389F 209E 3128 5698 * + DSS/DH: 8F3E 5BAE 906F B416 9242 1C10 8661 24A9 BFCE 822B + ___ Support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/mailman/listinfo/support
Re: [freenet-support] Announcement problem
At 02.45 11/02/03 -0500, you wrote: >On Mon, 2003-02-10 at 20:07, Greg Wooledge wrote: >> Build 611? Are you sure about that? I have made contact with >> (unstable) nodes with build numbers as high as 663. >> >> Are you also seeing your problem with the stable builds? > >Sorry for the typo... that should say 661. Also tried it tonight with >556: no successful announcements, same types of exceptions I included >before. I don't know if this is significant, but in the last couple of month my fresly bootsrapped node (now stable 552) has no traffic until I do some retrieve with fproxy; then it begin to have traffic that stabilize in a couple of hours. HTH. Marco -- + il Progetto Freenet - segui il coniglio bianco+ * the Freenet Project - follow the white rabbit* * Marco A. Calamari[EMAIL PROTECTED] www.marcoc.it* * PGP RSA: ED84 3839 6C4D 3FFE 389F 209E 3128 5698 * + DSS/DH: 8F3E 5BAE 906F B416 9242 1C10 8661 24A9 BFCE 822B + ___ Support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/mailman/listinfo/support
Re: [freenet-support] Announcement problem
On Mon, 2003-02-10 at 20:07, Greg Wooledge wrote: > Build 611? Are you sure about that? I have made contact with > (unstable) nodes with build numbers as high as 663. > > Are you also seeing your problem with the stable builds? Sorry for the typo... that should say 661. Also tried it tonight with 556: no successful announcements, same types of exceptions I included before. -Brian ___ Support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/mailman/listinfo/support
Re: [freenet-support] Announcement problem
Brian Auton ([EMAIL PROTECTED]) wrote: > My node has also been unable to announce... In the hope that some files > were corrupted, I tried a fresh install of freenet-unstable-20030208.tgz > (build 611), with the same result. Build 611? Are you sure about that? I have made contact with (unstable) nodes with build numbers as high as 663. Are you also seeing your problem with the stable builds? -- Greg Wooledge | "Truth belongs to everybody." [EMAIL PROTECTED] |- The Red Hot Chili Peppers http://wooledge.org/~greg/ | msg02883/pgp0.pgp Description: PGP signature
Re: [freenet-support] Announcement problem
On Sun, 2003-02-09 at 13:00, bdonlan wrote: > Have you tried deleteing your rt*, ls*, and store_* files/directories? That > might help. My node has also been unable to announce... In the hope that some files were corrupted, I tried a fresh install of freenet-unstable-20030208.tgz (build 611), with the same result. I can retrieve and insert all day long, but my node hasn't made one successful announcement in over 2 days of uptime. (Using j2re 1.4.1_01 on Linux.) Also tried completely disabling my firewall, just in case, but that didn't help. There are a few log entries like this: Feb 10, 2003 3:38:43 PM (freenet.Ticker, QThread-10): cancelled freenet.node.states.announcement.NoReply@1eb2c1b @ 1044909890793 java.lang.Exception: debug at freenet.Ticker$Event.cancel(Ticker.java:192) at freenet.node.EventMessageObject.cancel(EventMessageObject.java:55) at freenet.node.states.announcing.ExecuteAnnouncement.receivedMessage(ExecuteAnnouncement.java:93) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at freenet.node.State.received(State.java:126) at freenet.node.states.announcing.AnnouncingState.received(AnnouncingState.java:47) at freenet.node.StateChain.received(StateChain.java:161) at freenet.node.StateChain.received(StateChain.java:52) at freenet.node.AggregatingState.received(AggregatingState.java:40) at freenet.node.states.announcing.Announcing.received(Announcing.java:270) at freenet.node.StateChain.received(StateChain.java:161) at freenet.node.StateChain.received(StateChain.java:52) at freenet.node.StandardMessageHandler$Ticket.run(StandardMessageHandler.java:212) at freenet.node.StandardMessageHandler$Ticket.received(StandardMessageHandler.java:159) at freenet.node.StandardMessageHandler$Ticket.access$0(StandardMessageHandler.java) at freenet.node.StandardMessageHandler.handle(StandardMessageHandler.java:68) at freenet.Ticker$Event.run(Ticker.java:214) at freenet.thread.QThreadFactory$QThread.run(QThreadFactory.java:213) ...and lots and lots like this: Feb 10, 2003 4:15:40 PM (freenet.node.states.announcing.Announcing, QThread-5): Announcement failed to d3b0 b594 e297 5b70 74a2 cfcb eef5 22a1 3592 6cde at depth 13. ...a few of which are preceded by: Feb 10, 2003 4:15:40 PM (freenet.node.states.announcing.SendAnnouncement, QThread-5): Sending NodeAnnouncement failed: freenet.ConnectFailedException: Against peer DSA(d3b0 b594 e297 5b70 74a2 cfcb eef5 22a1 3592 6cde) @ 212.204.236.151:24588 - I/O error during outbound auth: java.net.SocketException: Broken pipe (terminal) Let me know if more logs or other info would help. -Brian ___ Support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/mailman/listinfo/support
Re: [freenet-support] Announcement problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 09 February 2003 01:36 am, Niklas Bergh wrote: > Upgraded to 555, restarted. Has had it up for 22 hours now and still no > connections > a.. Local mean traffic (queries per hour): 5.747573011459878 > > It seems that my node has successfully announced about 14 times during the > time it has been up is that a normal amount for a completely idle node? > Advertice probability has been constantly at 0.5. > > I haven't changed a thing for this problem to appear, it just happened. I > have a fixed IP, am not using ARK:s sun jvm 1.4.1_01. I have a debug level > log covering this (in which I cant really find something bad) Have you tried deleteing your rt*, ls*, and store_* files/directories? That might help. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+Rpc/x533NjVSos4RAuz3AJ9ginwztLYBE7FS++s/z6ko0PD4kQCcCib3 5PW/vYo546XuJ13ejP89XL4= =evGX -END PGP SIGNATURE- ___ Support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/mailman/listinfo/support
