[freenet-support] Crashes with 6469

2004-02-10 Thread Fwolff33
After updating to 6469 I always get this log entry right after starting the node, 
before the first request is made.

12:13:07 Size was wrong reading in SimpleDataObjectStore 

Until now I was also not able to run the node for longer then one or two hours, while 
it before would run for more then one day. Now it always crashes ~1 hour after 
starting with an error I have not seen before. Something with the thread factory and 
AutoRequest. Will copy it the next time when it is prompted in the Linux Terminal. 
Freenet will run on after that Error, but there are no transfers anymore and no 
interface is working. (Just the threads stay there.)
Perhaps it's just another problem that will vanish on it's own, but since it occured 
on both restarts which were made after the update, the update and the crash seem 
related to me.
As before I have no logs with the status Normal, since I only let log events with 
the status Error, since this seem to avoid out of memory errors for me.
___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]


RE: [freenet-support] Crashes with 6469

2004-02-10 Thread Niklas Bergh


 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of 
 [EMAIL PROTECTED]
 Sent: den 10 februari 2004 12:26
 To: [EMAIL PROTECTED]
 Subject: [freenet-support] Crashes with 6469
 
 
 After updating to 6469 I always get this log entry right 
 after starting the node, before the first request is made.
 
 12:13:07 Size was wrong reading in SimpleDataObjectStore 

This is prbably not causing you trouble.. I have committed some logging
changes that will better say what the cause is now (will incluse a
callstack and what the atual sizes are). Let me know what it says.

Regards
/N

___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]


[freenet-support] Re: Freenet is Broken...HELP!

2004-02-10 Thread Toad
On Tue, Feb 10, 2004 at 12:04:34AM -0500, An Metet wrote:
 I have tried time and time again to get freenet running only to be met with
 one frustration after another.
 
 The last version of freenet that worked and actually allowed me to retrieve
 freesites and frost content was build 5017.
 
 Since that time the various changes have changed freenet into a time
 wasting resource hog that gets no results at all.
 
 Now I find out that enough changes have been made that 5017 no longer seems
 to work at all.  oh it starts ok, but it rejects every entry in the
 seednodes.ref file on the freenet site, and is thus unable to talk to any
 other nodes.  It has also gotten so busy that I can no longer run it on a
 p233, which with 5017 I *could* do!

I have heard some success stories with recent builds on PCs nearly as
slow as that. You are running a transient node? I doubt you'd be able to
run a permanent node, (but if you can it's much preferable). So please
try 5067 (and reseed first), and tell me what happens. PS how much RAM
do you have?
 
 Is there any chance that freenet will start working again soon?
 
 please don't just say that I need to get a hotter pc, it just is not an
 option... I am forced to stay within what I have.
 
 (please reply to [Freenet Support], I read it via web interface and anon
 proxies... thanks for humoring a paranoid.)
 
 

-- 
Matthew J Toseland - [EMAIL PROTECTED]
Freenet Project Official Codemonkey - http://freenetproject.org/
ICTHUS - Nothing is impossible. Our Boss says so.


signature.asc
Description: Digital signature
___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]

RE: RE: [freenet-support] Crashes with 6469

2004-02-10 Thread Fwolff33
In einer eMail vom Di, 10. Feb. 2004 12:44 MEZ schreibt Niklas Bergh [EMAIL 
PROTECTED]:

This is prbably not causing you trouble.. I have committed some logging
changes that will better say what the cause is now (will incluse a
callstack and what the atual sizes are). Let me know what it says.

Regards
/N

This logging changes are implemented in 6470? I just run the upgrade skript after I 
saw your Mail and upgraded this way to that version. Stopping Freenet was necessary 
anyway: It stopped working again, this time after 40mins uptime and without an error. 
After some time the interface was reachable again, but there was no internet traffic, 
so this was definatly not caused by overload.
If 6470 is the version with your changes, you have actually fixed it for me.. :/ At 
least the error did not appear until now, and before it appeared right after starting 
the node. I will send a mail, if I see the error again.
But after Fproxy responded again at the last half-crash (Thats also strange, since 
Freenet did not recover at all at the previous two crashes), I noticed also some 
freenet.Message: DataRequest @freenet.MuxConnectionHandler errors in the Recent Log 
thing. They occured somewhere near the death of the node, so they could have something 
to do with it, but I am not sure about the exact time of the death, so thats hard to 
judge.
After I have reduced the log level to Normal, I noticed, that I get sometimes several 
Unrecognized Trailer ID errors in just a second, but if I remember previous postings 
to the support list correctly, that error is common.
Perhaps it's just another of this errors, which just leave on their own, as I wrote in 
the first post... I would not be mad if it would be so. As I write this mail, the node 
is running fo 35 mins, no sign of the previus size error and it responds good, but I 
have not made any request, so perhaps it's just because of that. (Before the first and 
second request I made some Fproxy Requests and before the third some Fuqid downloads 
with 5 Threads.)

___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]


[freenet-support] Stable 5068 Bad Seednodes, Transient/Permanent Question, etc

2004-02-10 Thread box3
I hope this is the right place for these questions.

Windows XP.

I just updated to 5068 (stable) and got the new node references.  After 
running, apparently without problems, for a while, Freenet encountered 
problems (stopped functioning, flashing icon).

I exited Freenet and restarted it.  Looking at the log file I saw that it 
had problems with bad seednode references, among many other things.

   [While looking at the log again just now Freenet crashed.]

But my main question at the moment is:  Why is my node set as transient (as 
reflected in the log) and how can I change it?

I have a broadband connection and the computer is always on so it should be 
set as permanent, right?

___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]


[freenet-support] bug report (?)

2004-02-10 Thread Klaus BrĂ¼ssel
Sometimes I get this error message on stable build 5068 (and the builds 
before). I think client programs fetching keys via fcp stall , untill the 
socket timeouts (If set). I use linux and sun jvm 1.4.1_03-b02.

Caught java.lang.IllegalStateException: Not sending a trailer running 
maintenance queue
java.lang.IllegalStateException: Not sending a trailer
at 
freenet.ConnectionHandler$TrailerSendState.hasTrailerDataRemaining(ConnectionHandler.java:163)
at freenet.ConnectionHandler.jobDone(ConnectionHandler.java:1251)
at freenet.ConnectionHandler.terminate(ConnectionHandler.java:2413)
at freenet.ConnectionHandler.queuedClose(ConnectionHandler.java:1426)
at 
freenet.transport.AbstractSelectorLoop.queueClose(AbstractSelectorLoop.java:764)
at 
freenet.transport.ThrottledSelectorLoop.queueClose(ThrottledSelectorLoop.java:414)
at 
freenet.transport.AbstractSelectorLoop.queueClose(AbstractSelectorLoop.java:812)
at 
freenet.transport.ReadSelectorLoop.beforeSelect(ReadSelectorLoop.java:168)
at 
freenet.transport.AbstractSelectorLoop.loop(AbstractSelectorLoop.java:661)
at freenet.transport.ReadSelectorLoop.run(ReadSelectorLoop.java:674)
at java.lang.Thread.run(Thread.java:536)
___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]


Re: [freenet-support] Blackdown

2004-02-10 Thread John Huttley
On Tue, 2004-02-10 at 13:43, Todd wrote:
  Hello,
 
 Hey.
 
  I've tried running freenet stable with blackdown-1.4.1 under linux
  (gentoo)
  Unfortunately it fails after a little while.
 
 Fails with what?  Are you sure it's the JVM and not Freenet?

Yes, java seems to be running but fproxy is not contactable.
It seems to run for a few hours ok.


  I've switched back to sun 1.4.2_03
 
 Does it now not fail?

Runs Fine.

 I haven't used Freenet (or much of anything, actually) for two months 
 now.  Blackdown/Freenet was working for me as of December 12, 2003.  
 Funny.

Thats computers for you.


 -todd
 
 ___
 Support mailing list
 [EMAIL PROTECTED]
 http://news.gmane.org/gmane.network.freenet.support
 Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
 Or mailto:[EMAIL PROTECTED]
 
 

___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]


Re: [freenet-support] Stable 5068 Bad Seednodes, Transient/Permanent Question, etc

2004-02-10 Thread box3
Toad,

At 06:25 PM 2/10/2004 +, you wrote:
 But my main question at the moment is:  Why is my node set as transient 
(as
 reflected in the log) and how can I change it?

 I have a broadband connection and the computer is always on so it 
should be
 set as permanent, right?

Firewall? Datastore size?
The datastore size is set at the default 8381 mb).  I have the room to set 
it larger.  In my experience it gets larger anyway if Freenet is used to 
download large files.

I configured my router/firewall when I first installed Freenet last summer, 
and I don't remember the details but it has always worked.

When I go into settings the radio button for switching to permanent rather 
than transient is blacked out and it says to change that on the geek 
page.  How do I change it?  It isn't obvious and I am afraid to play around 
with settings blind.

___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]


[freenet-support] RE: number of connections

2004-02-10 Thread Steven
Niklaus:  You insist that If I have a low maximum connections setting, my node 
will have to make more connections, and therefore my node will overload.  
However, if I let my max connects get past 90 or so, it gets overloaded. It 
just SLOWLY adds more and more connections until my node freezes.  I see 
other people in this forum w/ much lower system specs than I have (1.3 
gigahertz athlon w/ 384 megs of ram and 2.5 mb/s internet connection.)

Is there a better way to keep my node from getting overloaded?  maybe I'm 
crazy, but limiting my max connects really seems to help.

on a different note, I think the network has really improved with the 5068 
release.  I've been able to retrieve a lot of stuff.  My node eventually 
overloads, but I'm going to restart it right now with a max connects of 80.  
as of right now my node has 140 connections, and it's frozen solid. 



--  Forwarded Message  --

Subject: number of connections
Date: Saturday 24 January 2004 23:21
From: Steven [EMAIL PROTECTED]
To: [EMAIL PROTECTED]

since multiplexing has been ported to the stable branch of freenet, we can
have a MUCH lower maxConnection setting right?  I used allow 300, now I only
allow 20.  Is this a bad idea?

I've had a lot of traffic on my node, and everything seems to be working fine
(although connecting initially took forever) according to the numbers, but i
can't retrieve much.

---
___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]


[freenet-support] Re: Stable 5068 Bad Seednodes, Transient/Permanent Question, etc

2004-02-10 Thread Someone
[EMAIL PROTECTED] schrieb:

I configured my router/firewall when I first installed Freenet last 
summer, and I don't remember the details but it has always worked.
Make shure the port freenet uses is still forwarded to the right machine
and not filtered by some sort of (personal) firewall, for ex. the WinXP
integrated fw.
When I go into settings the radio button for switching to permanent 
rather than transient is blacked out and it says to change that on the 
geek page.  How do I change it?  It isn't obvious and I am afraid to 
play around with settings blind.
Open freenet.ini with notepad or wordpad, search for transient and make
shure the line looks like:
%transient=false

not like:

transient=true

Which JRE do you use and from which build did you upgrade, best JREs for
windows the 1.4.2_03 and 1.5 beta from Sun as far as I can tell. If yours
is older upgrade it (go for 1.4.2_03 at the moment, 1.5 is faster but a
little bit wanky).
Greets someone

___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]


Re: [freenet-support] RE: number of connections

2004-02-10 Thread Toad
Operating system?

On Tue, Feb 10, 2004 at 06:31:46PM -0800, Steven wrote:
 Niklaus:  You insist that If I have a low maximum connections setting, my node 
 will have to make more connections, and therefore my node will overload.  
 However, if I let my max connects get past 90 or so, it gets overloaded. It 
 just SLOWLY adds more and more connections until my node freezes.  I see 
 other people in this forum w/ much lower system specs than I have (1.3 
 gigahertz athlon w/ 384 megs of ram and 2.5 mb/s internet connection.)
 
 Is there a better way to keep my node from getting overloaded?  maybe I'm 
 crazy, but limiting my max connects really seems to help.
 
 on a different note, I think the network has really improved with the 5068 
 release.  I've been able to retrieve a lot of stuff.  My node eventually 
 overloads, but I'm going to restart it right now with a max connects of 80.  
 as of right now my node has 140 connections, and it's frozen solid. 
 
 
 
 --  Forwarded Message  --
 
 Subject: number of connections
 Date: Saturday 24 January 2004 23:21
 From: Steven [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 
 since multiplexing has been ported to the stable branch of freenet, we can
 have a MUCH lower maxConnection setting right?  I used allow 300, now I only
 allow 20.  Is this a bad idea?
 
 I've had a lot of traffic on my node, and everything seems to be working fine
 (although connecting initially took forever) according to the numbers, but i
 can't retrieve much.
 
 ---
 ___
 Support mailing list
 [EMAIL PROTECTED]
 http://news.gmane.org/gmane.network.freenet.support
 Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
 Or mailto:[EMAIL PROTECTED]

-- 
Matthew J Toseland - [EMAIL PROTECTED]
Freenet Project Official Codemonkey - http://freenetproject.org/
ICTHUS - Nothing is impossible. Our Boss says so.


signature.asc
Description: Digital signature
___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]

[freenet-support] Fwd: number of connections

2004-02-10 Thread Steven

Gentoo linux kernel 2.6.2-mmsources
--  Forwarded Message  --

Subject: number of connections
Date: Saturday 24 January 2004 23:21
From: Steven [EMAIL PROTECTED]
To: [EMAIL PROTECTED]

since multiplexing has been ported to the stable branch of freenet, we can
have a MUCH lower maxConnection setting right?  I used allow 300, now I only
allow 20.  Is this a bad idea?

I've had a lot of traffic on my node, and everything seems to be working fine
(although connecting initially took forever) according to the numbers, but i
can't retrieve much.

---
___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]


Re: [freenet-support] Re: Stable 5068 Bad Seednodes, Transient/Permanent Question, etc

2004-02-10 Thread box3
Someone:

At 03:36 AM 2/11/2004 +0100, you wrote:

[EMAIL PROTECTED] schrieb:

I configured my router/firewall when I first installed Freenet last 
summer, and I don't remember the details but it has always worked.
Make shure the port freenet uses is still forwarded to the right machine
and not filtered by some sort of (personal) firewall, for ex. the WinXP
integrated fw.
I just realized what happened.  I had installed Freenet last summer, but a 
couple of days ago it stopped working, and update snapshot did not help, so 
I uninstalled and deleted everything and made a fresh install.  So the 
Freenet.ini file was new and the interface with my NAT router had to be 
reconfigured.  I just did that.


When I go into settings the radio button for switching to permanent 
rather than transient is blacked out and it says to change that on the 
geek page.  How do I change it?  It isn't obvious and I am afraid to play 
around with settings blind.
Open freenet.ini with notepad or wordpad, search for transient and make
shure the line looks like:
%transient=false
It says %transient=false

I guess fixing the NAT settings fixed everything else.  It seems to be 
working.


not like:

transient=true

Which JRE do you use and from which build did you upgrade, best JREs for
windows the 1.4.2_03 and 1.5 beta from Sun as far as I can tell. If yours
is older upgrade it (go for 1.4.2_03 at the moment, 1.5 is faster but a
little bit wanky).
Where do I get the JRE update to 1.4.2_03 ?  I have 1.4.1_03, and it runs 
out of memory.

Thanks for the help



___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]


[freenet-support] NPE at freenet.MuxConnectionHandler.sendPacket

2004-02-10 Thread Nomen Nescio
Getting these sporadically with 5068 on Linux 2.6.2 Blackdown-1.4.2-rc1:

11.02.2004 02:07:17 (freenet.transport.WriteSelectorLoop, Network writing thread, 
ERROR): Caught java.lang.NullPointerException notifying [EMAIL PROTECTED] 
MuxConnectionHandler[conn=[tcp/connection: xx.x.x.x:x,[EMAIL PROTECTED], [EMAIL 
PROTECTED], [EMAIL PROTECTED], identity=[DSA(x)], 
sock=[Socket[addr=x/x.x.x.x,port=x,localport=x]], 
chan=[java.nio.channels.SocketChannel[connected local=/x.x.x.x:x remote=x/x.x.x.x:x]], 
peer=[Peer [DSA(x) @ x.x.x.x:x (1/3)]], outbound=[true]] for 
java.nio.channels.SocketChannel[connected local=/x.x.x.x:x remote=x/x.x.x.x:x] in 
processConnections
java.lang.NullPointerException
at freenet.MuxConnectionHandler.sendPacket(MuxConnectionHandler.java:218)
at freenet.MuxConnectionHandler.jobDone(MuxConnectionHandler.java:354)
at 
freenet.transport.WriteSelectorLoop.processConnections(WriteSelectorLoop.java:698)
at freenet.transport.AbstractSelectorLoop.loop(AbstractSelectorLoop.java:729)
at freenet.transport.WriteSelectorLoop.run(WriteSelectorLoop.java:748)
at java.lang.Thread.run(Thread.java:534)

___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]


[freenet-support] Stable build 5068

2004-02-10 Thread Toad
Freenet stable build 5068 is now available. Upgrade using
freenet-webinstall.exe or update.sh , or download the jar from
http://freenetproject.org/snapshots/freenet-latest.jar . All users of
the stable network/branch should upgrade immediately.

This fixes a major bug in 5067 and a minor one, one that caused
NullPointerException's in routing after we had been up for a while, and
one optimization.
-- 
Matthew J Toseland - [EMAIL PROTECTED]
Freenet Project Official Codemonkey - http://freenetproject.org/
ICTHUS - Nothing is impossible. Our Boss says so.


signature.asc
Description: Digital signature
___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]