Re: [freenet-support] Announcement problem

2003-02-10 Thread Brian Auton
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

2003-02-10 Thread Greg Wooledge
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

2003-02-10 Thread Brian Auton
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: RE :[freenet-support] PLEASE UNSUBSCRIBE ME

2003-02-10 Thread bdonlan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sunday 09 February 2003 11:18 pm, pingold wrote:
> Dear Sirs,
> Will you please unsubscribe me from your newsletters ?
> Thank you very much!
> [EMAIL PROTECTED]

There's an unsubscribe link at the end of each email, you can't miss it. Or 
email the list admin, not everyone on the list.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+R6y7x533NjVSos4RAoYYAJ9lAbYWJvtReodtdGVhPoFfkwBKFwCcCpKf
ZhZnIs3QOH60kZdy9v5OW/E=
=/15R
-END PGP SIGNATURE-

___
Support mailing list
[EMAIL PROTECTED]
http://hawk.freenetproject.org:8080/mailman/listinfo/support



RE: [freenet-support] Build 659 (unstable)

2003-02-10 Thread Niklas Bergh
659 seems to have solved the 'Node suddenly ceases traffic'-problem. I
have a node that has been up for close 120 hours now and there is till
no sign of stagnation. It is serving up 13000 q/h at about 1MBit/s.

One thing though:

Peer addr Send Count Send Size Receiving Messages Idle time Lifetime
Thread Type ID
155.239.180.179:34467 0 0 yes 1 0 393188783 QThread-12740 Inbound 33c0b6
80.134.237.85:21321 0 0 yes 2 0 353667846 QThread-25929 Inbound 7e5c44
80.134.237.85:15291 0 0 yes 8 0 305199082 QThread-34344 Inbound 5e833f
68.82.148.48:18230 0 0 yes 1 0 27095 QThread-36576 Inbound 514847
213.208.127.216:17565 0 0 yes 7 0 172335455 QThread-44615 Inbound 134183
64.252.121.1:34381 0 0 yes 10 0 22933808 QThread-45372 Inbound 323c46
216.15.192.235:56589 0 0 yes 2 0 42376945 QThread-42938 Inbound 13374f
134.193.75.29:3277 0 0 yes 8 0 18536034 QThread-45215 Inbound 1423d4
129.240.200.147:39076 1 147772 yes 471 0 19078844 QThread-45337 Inbound
3c54ad

This is the initial entries of my ocm table. I do not like that
idle-time always is zero on those connections where 'receiving' is
'yes'. It seems like the idletime is set to zero even if the connection
is idle. Should it really be so, couldn't idle-time be set to indicate
the time since the last packet was recieved on that connection instead?!

/N


___
Support mailing list
[EMAIL PROTECTED]
http://hawk.freenetproject.org:8080/mailman/listinfo/support