[freenet-support] freenet not working

2012-11-17 Thread jordi
Hi, some time ago, my freenet node does not work fine. I hoped the last
update solved this but now it's worst. Some times I have more than 30
strangers connected but suddently the node disconnects from them. I see
lots of erros in the logs. I send some information, but please tell me
which files do you need to help.

-- excuse my poor English --

Freenet Version:
Freenet 0.7.5 Build #1423 build01423
Freenet-ext Build #29 rv29
System Information:
Used Java memory: 398 MiB
Allocated Java memory: 579 MiB
Maximum Java memory: 632 MiB
Running threads: 253/600
Available CPUs: 4
Java Version: 1.7.0_09
Java VM Vendor: Oracle Corporation
Java VM Name: Java HotSpot(TM) Server VM
Java VM Version: 23.5-b02
OS Name: Linux
OS Version: 2.6.32-5-686
OS Architecture: i386

Store Size:
Store: (CHK)
  Keys: 537.055
  Capacity: 537.055
  Data Size: 16.3 GiB
  Utilization: 100,0%
  Read-Requests: 13.373 (83.090.104)
  Successful Reads: 1.549 (7.156.844)
11,5830% (8,6134%)
Cache: (CHK)
  Keys: 537.055
  Capacity: 537.055
  Data Size: 16.3 GiB
  Utilization: 100,0%
  Read-Requests: 11.824 (75.927.480)
  Successful Reads: 1.665 (4.705.594)
14,0815% (6,1975%)
Slashdot cache: (CHK)
  Keys: 789
  Capacity: 790
  Data Size: 24.6 MiB
  Utilization: 99,9%
  Read-Requests: 13.496
  Successful Reads: 123
0,9114%
Client cache: (CHK)
  Keys: 5.993
  Capacity: 5.993
  Data Size: 187 MiB
  Utilization: 100,0%
  Read-Requests: 5.173 (3.146.165)
  Successful Reads: 1.821 (679.563)
35,2020% (21,5997%)
Store: (SSK)
  Keys: 356.666
  Capacity: 537.055
  Data Size: 348 MiB
  Utilization: 66,4%
  Read-Requests: 149.403 (385.771.833)
  Successful Reads: 4.295 (4.541.784)
2,8748% (1,1773%)
Cache: (SSK)
  Keys: 470.372
  Capacity: 537.055
  Data Size: 459 MiB
  Utilization: 87,6%
  Read-Requests: 145.108 (381.282.278)
  Successful Reads: 5.696 (4.369.508)
3,9254% (1,1460%)
Slashdot cache: (SSK)
  Keys: 789
  Capacity: 790
  Data Size: 789 KiB
  Utilization: 99,9%
  Read-Requests: 149.767
  Successful Reads: 364
0,2430%
Client cache: (SSK)
  Keys: 5.993
  Capacity: 5.993
  Data Size: 5.85 MiB
  Utilization: 100,0%
  Read-Requests: 129.122 (223.321.484)
  Successful Reads: 3.292 (1.859.979)
2,5495% (0,8329%)
Store: (Pubkey)
  Keys: 46.474
  Capacity: 537.055
  Data Size: 45.3 MiB
  Utilization: 8,7%
  Read-Requests: 5.207 (14.307.904)
  Successful Reads: 1.612 (3.814.211)
30,9583% (26,6581%)
Cache: (Pubkey)
  Keys: 190.615
  Capacity: 537.055
  Data Size: 186 MiB
  Utilization: 35,5%
  Read-Requests: 3.595 (10.493.579)
  Successful Reads: 3.209 (7.308.442)
89,2629% (69,6468%)
Slashdot cache: (Pubkey)
  Keys: 654
  Capacity: 790
  Data Size: 654 KiB
  Utilization: 82,8%
  Read-Requests: 11
  Successful Reads: 1
9,0909%
Client cache: (Pubkey)
  Keys: 5.993
  Capacity: 5.993
  Data Size: 5.85 MiB
  Utilization: 100,0%
  Read-Requests: 9.864 (26.174.515)
  Successful Reads: 5.127 (14.520.361)
51,9769% (55,4752%)

Activity:
Inserts: 58 CHK handlers, 8 SSK handlers (2/2 local)
Requests: 191 CHK handlers, 113 SSK handlers (3/32 local)
Transferring Requests: sending 58, receiving 138
Block transfers: 153 sends, 89 receives

Peer Statistics:
Connected: 24
Backed off: 8
Never connected: 8
Disconnecting: 1
Seed nodes: 2
Max peers: 40
Max strangers: 40

Bandwidth:
Input Rate: 85.9 KiB/s (of 500 KiB/s)
Output Rate: 110 KiB/s (of 150 KiB/s)
Session Total Input: 124 MiB (29.9 KiB/s average)
Session Total Output: 171 MiB (41.1 KiB/s average)
Payload Output: 135 MiB (32.4 KiB/sec)(78%)
Global Total Input: 209 GiB
Global Total Output: 275 GiB
Request output (excluding payload): CHK -3.35 MiB SSK 6.76 MiB.
Insert output (excluding payload): CHK -1.82 MiB SSK 109 KiB.
Offered keys: sending keys -27.0 KiB, sending offers 85.4 KiB
Swapping Output: 1.26 MiB.
Connection setup: 1.97 MiB output
Ack-only packets: 2.33 MiB
Resent bytes: 13.8 MiB (8%)
Updater Output: 962 KiB
Announcement output: 1.61 MiB (transferring node refs payload 1.48 MiB)
Admin bytes: 194 KiB initial messages, 0 B IP change messages, 749 B
disconnection notifications, 0 B routing status
Debugging bytes: 0 B network coloring, 11.2 KiB ping, 93 B probe
requests, 0 B routed test messages.
Node to node messages: 81.8 KiB
Load allocation notices: 1.53 MiB
FOAF related: 0 B
Other output: 10.7 MiB (6%)
Total non-request overhead: 5.39 KiB/sec (13%).

Plugins:
Plugins currently loaded
/home/freenet/Freemail.jar (freemail.FreemailPlugin) - 0.1 Pet Shop
(v15-zidel-rc1-7-g013c) (14) pfreemail.FreemailPlugin_1277766
http://localhost:/freenet:USK@nwa8lHa271k2QvJ8aa0Ov7IHAV-DFOCFgmDt3X6BpCI,DuQSUZiI~agF8c-6tjsFFGuZ8eICrzWCILB60nT8KKo,AQACAAE/sone/56/sone-current.jar
 (net.pterodactylus.sone.main.SonePlugin) - 0.8.4 
pnet.pterodactylus.sone.main.SonePlugin_3162350
Freetalk (plugins.Freetalk.Freetalk) - 0.1 build0013 (13)
pplugins.Freetalk.Freetalk_12119823
JSTUN (plugins.JSTUN.JSTUN) - 1.2 (3) pplugins.JSTUN.JSTUN_30654707
KeyUtils (plugins.KeyUtils.KeyUtilsPlugin) - 0.5.3 v5018 (5018)

Re: [freenet-support] freenet not working

2012-11-17 Thread jordi
El ds 17 de 11 de 2012 a les 08:39 -0500, en/na Dennis Nezic va
escriure:

 
 For a start, you can check your wrapper.log file -- perhaps output a
 thread dump when you think it's broken (via the web/fproxy interface, in
 the Statistics section, Generate a Thread Dump) -- the output will
 also get dumped into wrapper.log. If none of that is informative, you
 can enable more detailed logging in the Logs section. Be careful to
 scrub any logs[1] of sensitive information before sending them.

I send some part of the logs. The sensitive information could be the
ips of the strangers which i am connected. Otherwise the logs are big,
but tell me if can I fully send them, and if strangers ips are
considered sensitive information.

At the moment I disable WoT and FreeTalk. 

Thanks.
nov. 17, 2012 18:01:14:727 (freenet.node.RequestTag, Slow callback for 
freenet.io.xfer.BlockReceiver$3@1798515(3396), WARNING): Removing wrong node or 
removing twice? on freenet.node.RequestTag@c79096:-2040080277077284646 : 
freenet.node.OpennetPeerNode@ed54bceb@
java.lang.Exception: debug
at freenet.node.UIDTag.removeRoutingTo(UIDTag.java:164)
at freenet.node.PeerNode.noLongerRoutingTo(PeerNode.java:5693)
at freenet.node.RequestSender.finish(RequestSender.java:1607)
at freenet.node.RequestSender.access$700(RequestSender.java:58)
at freenet.node.RequestSender$7.blockReceived(RequestSender.java:1163)
at freenet.io.xfer.BlockReceiver.complete(BlockReceiver.java:462)
at freenet.io.xfer.BlockReceiver.access$1400(BlockReceiver.java:74)
at freenet.io.xfer.BlockReceiver$3.onMatched(BlockReceiver.java:313)
at freenet.io.comm.MessageFilter$3.run(MessageFilter.java:419)
at 
freenet.support.PooledExecutor$MyThread.realRun(PooledExecutor.java:234)
at freenet.support.io.NativeThread.run(NativeThread.java:129)
nov. 17, 2012 18:01:16:342 (freenet.node.RequestTag, Slow callback for 
freenet.io.xfer.BlockReceiver$3@1dcb669(3434), WARNING): Removing wrong node or 
removing twice? on freenet.node.RequestTag@1cbce50:-6523420304190318096 : 
freenet.node.OpennetPeerNode@68c08589@--
java.lang.Exception: debug
at freenet.node.UIDTag.removeRoutingTo(UIDTag.java:164)
at freenet.node.PeerNode.noLongerRoutingTo(PeerNode.java:5693)
at freenet.node.RequestSender.finish(RequestSender.java:1607)
at freenet.node.RequestSender.access$700(RequestSender.java:58)
at freenet.node.RequestSender$7.blockReceived(RequestSender.java:1163)
at freenet.io.xfer.BlockReceiver.complete(BlockReceiver.java:462)
at freenet.io.xfer.BlockReceiver.access$1400(BlockReceiver.java:74)
at freenet.io.xfer.BlockReceiver$3.onMatched(BlockReceiver.java:313)
at freenet.io.comm.MessageFilter$3.run(MessageFilter.java:419)
at 
freenet.support.PooledExecutor$MyThread.realRun(PooledExecutor.java:234)
at freenet.support.io.NativeThread.run(NativeThread.java:129)
nov. 17, 2012 18:01:17:430 (freenet.node.RequestTag, Slow callback for 
freenet.node.RequestSender$MainLoopCallback@daa1f1:freenet.node.OpennetPeerNode@911fa26c@---:false:freenet.node.RequestSender@1bde717
 for 3772663083093595994(3432), WARNING): Removing wrong node or removing 
twice? on freenet.node.RequestTag@1fd6f87:3772663083093595994 : 
freenet.node.OpennetPeerNode@911fa26c@

-
-
-
--
-
nov. 17, 2012 18:04:43:123 (plugins.Freetalk.WoT.WoTIdentityManager, Freetalk 
WoTIdentityManager(76), ERROR): ROLLED BACK!
java.lang.RuntimeException: java.lang.NullPointerException
at 
plugins.Freetalk.WoT.WoTIdentityManager.importIdentity(WoTIdentityManager.java:736)
at 
plugins.Freetalk.WoT.WoTIdentityManager.parseIdentities(WoTIdentityManager.java:780)
at 
plugins.Freetalk.WoT.WoTIdentityManager.fetchIdentities(WoTIdentityManager.java:603)
at 
plugins.Freetalk.WoT.WoTIdentityManager.run(WoTIdentityManager.java:959)
at 
freenet.support.PooledExecutor$MyThread.realRun(PooledExecutor.java:234)
at freenet.support.io.NativeThread.run(NativeThread.java:129)
java.lang.NullPointerException(no stack trace)
nov. 17, 2012 18:04:43:124 (plugins.Freetalk.WoT.WoTIdentityManager, Freetalk 
WoTIdentityManager(76), ERROR): Importing a new identity failed.
java.lang.RuntimeException: java.lang.NullPointerException
at 
plugins.Freetalk.WoT.WoTIdentityManager.importIdentity(WoTIdentityManager.java:736)
at 
plugins.Freetalk.WoT.WoTIdentityManager.parseIdentities(WoTIdentityManager.java:780)
at 
plugins.Freetalk.WoT.WoTIdentityManager.fetchIdentities(WoTIdentityManager.java:603)
at 
plugins.Freetalk.WoT.WoTIdentityManager.run(WoTIdentityManager.java:959)
at 
freenet.support.PooledExecutor$MyThread.realRun(PooledExecutor.java:234)
   

[freenet-support] bug?

2008-11-16 Thread jordi
I send this message as a probable bug seen in the messages page.

Probably a bug: please report: 2 peers forcibly disconnected due to not 
acknowledging packets.
2 of your peers are having severe problems (not acknowledging packets even 
after 10 minutes). This is probably due to a bug in the code. Please report it 
to us at the bug tracker at https://bugs.freenetproject.org/ or at support at 
freenetproject.org. Please include this message and what version of the node 
you are running. The affected peers (you may not want to include this in your 
bug report if they are darknet peers) are:

* 213.238.213.47:42602
* 72.73.181.44:7420

Version Information & Node Control
Freenet 0.7 Build #1178 r23592M
Freenet-ext Build #24 r23199






[freenet-support] bug?

2008-11-16 Thread jordi
I send this message as a probable bug seen in the messages page.

Probably a bug: please report: 2 peers forcibly disconnected due to not 
acknowledging packets.
2 of your peers are having severe problems (not acknowledging packets even 
after 10 minutes). This is probably due to a bug in the code. Please report it 
to us at the bug tracker at https://bugs.freenetproject.org/ or at [EMAIL 
PROTECTED] Please include this message and what version of the node you are 
running. The affected peers (you may not want to include this in your bug 
report if they are darknet peers) are:

* 213.238.213.47:42602
* 72.73.181.44:7420

Version Information  Node Control
Freenet 0.7 Build #1178 r23592M
Freenet-ext Build #24 r23199


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


[freenet-support] 64 bits jvm

2006-07-07 Thread jordi
Hi, I'm trying to use freenet 0.7 but it seems that 64
bits is not supported yet. Maybe I'm doing something
wrong.

Any help will be wellcome.

Thanks.



__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam
protection around 
http://mail.yahoo.com 

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-- next part --
A non-text attachment was scrubbed...
Name: wrapper.log
Type: text/x-log
Size: 5758 bytes
Desc: 3418027544-wrapper.log
URL: