Re: Freenet infinite restart
Try to delete client.dat.crypt file. It may help. Regards On 9/23/19 4:23 AM, kobatofu leixi wrote: Freenet will open and run until "INFO | jvm 1 | 2019/09/22 22:12:22 | Deleted 0 of 0 temporary files (0 non-temp files in temp directory) in 0s" this point in the log, where it will stop doing anything until it times itself out waiting for a signal from the JVM, and then will restart over and over, until it gives up on the 5th retry. It was working fine a couple days ago. I tried increasing the java.exit.timeout in conf to no avail.
Re: Fwd: Re: Reproduced: Re: FN cannot start
This could be the case. With about 20 downloads, FN starts normally each time. Over 100 downloads make it difficult. Regards Krzysztof On 6/19/19 1:36 AM, Arne Babenhauserheide wrote: How many downloads do you have? More than 20 or so? Krzysztof writes: Morover, I had to delete all client* files for node to start. Regards Krzysztof Forwarded Message Subject:Re: Reproduced: Re: FN cannot start Date: Tue, 18 Jun 2019 23:11:33 +0200 From: Krzysztof To: Support Reproduced once more. Any clues? It definitely has nothing to do with JRE. Both Open and Sun on Linux Debian 64b fail after some time. Regards Krzysztof On 6/13/19 5:19 PM, Steve Dougherty wrote: Oh, interesting! Is this a symptom of a malformed client.dat.crypt? If you restore the file, does it fail in the same way again? - Steve Sent from ProtonMail Mobile On Thu, Jun 13, 2019 at 10:36 AM, Krzysztof mailto:k...@limes.com.pl>> wrote: No, I don't. What I discovered so far, after deleting file 'client.dat.crypt', the node started normally. Of course, all downloads were gone. Maybe there is a way to test or repair this file? Regards Krzysztof On 6/13/19 12:29 PM, Arne Babenhauserheide wrote: My node now also stopped starting. Question to Krzysztof: Do you have a darknet connection? When run via ./run.sh console, this is the last line I see before startup fails: jvm 2 | Deleted 0 of 0 temporary files (0 non-temp files in temp directory) in 0s This is what I should see: jvm 1 | Resumed 4 requests ... jvm 1 | Initializing USK Manager jvm 1 | Loading cache of request statuses... jvm 1 | Initializing Node Updater Disabling all plugins does not make a difference. Starting without the wrapper does not make a difference either. Moving tmp away does not make a difference, either. Moving datastore to datastore.broken does not make a difference. Moving persistent-temp to persistent-temp.broken only lets it show one more error: jvm 1 | Unable to resume request freenet.clients.fcp.ClientGet@45d042f9 after loading it. So it looks like there is some broken state which blocks startup. logs/freenet-latest.log says Jun 13, 2019 09:18:00:317 (freenet.io.AddressTracker, WrapperListener_start_runner, WARNING): Failed to load from disk for port : freenet.node.FSParseException: Unable to load address tracker table, assuming an unclean shutdown: Last ID was but stored freenet.node.FSParseException: Unable to load address tracker table, assuming an unclean shutdown: Last ID was but stored at freenet.io.AddressTracker.(AddressTracker.java:115) at freenet.io.AddressTracker.create(AddressTracker.java:84) at freenet.io.comm.UdpSocketHandler.(UdpSocketHandler.java:161) at freenet.node.NodeCrypto.(NodeCrypto.java:121) at freenet.node.Node.(Node.java:1489) at freenet.node.NodeStarter.start(NodeStarter.java:194) at org.tanukisoftware.wrapper.WrapperManager$11.run(WrapperManager.java:4048) I took an application snapshot with jvisualvm: Here’s the threaddump Full thread dump OpenJDK 64-Bit Server VM (25.191-b12 mixed mode): "Pooled thread awaiting work @1 for prio 5" #42 daemon prio=5 os_prio=0 tid=0x7f68005f7000 nid=0x27ae in Object.wait() [0x7f681dc9e000] java.lang.Thread.State: TIMED_WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x9d22ff80> (a freenet.support.PooledExecutor$MyThread) at freenet.support.PooledExecutor$MyThread.innerRun(PooledExecutor.java:218) - locked <0x9d22ff80> (a freenet.support.PooledExecutor$MyThread) at freenet.support.PooledExecutor$MyThread.realRun(PooledExecutor.java:189) at freenet.support.io.NativeThread.run(NativeThread.java:156) Locked ownable synchronizers: - None "Timer-0" #36 daemon prio=5 os_prio=0 tid=0x7f680009d000 nid=0x27a1 in Object.wait() [0x7f681e19f000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x9cfdf0b0> (a java.util.TaskQueue) at java.lang.Object.wait(Object.java:502) at java.util.TimerThread.mainLoop(Timer.java:526) - locked <0x9cfdf0b0> (a java.util.TaskQueue) at java.util.TimerThread.run(Timer.java:505) Locked ownable synchronizers: - None "SimpleToadletServer" #29 daemon prio=5 os_prio=0 tid=0x7f6800844800 nid=0x2788 waiting on condition [0x7f681e4a] java.lang.Thread.State: WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0x9cfdf740> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitUninterruptibly(AbstractQueuedSynchronizer.java:1976) at freenet.io.NetworkInterface.accept(NetworkInterface.java:249) at freenet.clients.http.SimpleToadletServer.run(SimpleToadletServer.j
Re: Fwd: Re: Reproduced: Re: FN cannot start
Yes, about 130 currently. Most of them are paused. Regards Krzysztof On 6/19/19 1:36 AM, Arne Babenhauserheide wrote: How many downloads do you have? More than 20 or so? Krzysztof writes: Morover, I had to delete all client* files for node to start. Regards Krzysztof Forwarded Message Subject:Re: Reproduced: Re: FN cannot start Date: Tue, 18 Jun 2019 23:11:33 +0200 From: Krzysztof To: Support Reproduced once more. Any clues? It definitely has nothing to do with JRE. Both Open and Sun on Linux Debian 64b fail after some time. Regards Krzysztof On 6/13/19 5:19 PM, Steve Dougherty wrote: Oh, interesting! Is this a symptom of a malformed client.dat.crypt? If you restore the file, does it fail in the same way again? - Steve Sent from ProtonMail Mobile On Thu, Jun 13, 2019 at 10:36 AM, Krzysztof mailto:k...@limes.com.pl>> wrote: No, I don't. What I discovered so far, after deleting file 'client.dat.crypt', the node started normally. Of course, all downloads were gone. Maybe there is a way to test or repair this file? Regards Krzysztof On 6/13/19 12:29 PM, Arne Babenhauserheide wrote: My node now also stopped starting. Question to Krzysztof: Do you have a darknet connection? When run via ./run.sh console, this is the last line I see before startup fails: jvm 2 | Deleted 0 of 0 temporary files (0 non-temp files in temp directory) in 0s This is what I should see: jvm 1 | Resumed 4 requests ... jvm 1 | Initializing USK Manager jvm 1 | Loading cache of request statuses... jvm 1 | Initializing Node Updater Disabling all plugins does not make a difference. Starting without the wrapper does not make a difference either. Moving tmp away does not make a difference, either. Moving datastore to datastore.broken does not make a difference. Moving persistent-temp to persistent-temp.broken only lets it show one more error: jvm 1 | Unable to resume request freenet.clients.fcp.ClientGet@45d042f9 after loading it. So it looks like there is some broken state which blocks startup. logs/freenet-latest.log says Jun 13, 2019 09:18:00:317 (freenet.io.AddressTracker, WrapperListener_start_runner, WARNING): Failed to load from disk for port : freenet.node.FSParseException: Unable to load address tracker table, assuming an unclean shutdown: Last ID was but stored freenet.node.FSParseException: Unable to load address tracker table, assuming an unclean shutdown: Last ID was but stored at freenet.io.AddressTracker.(AddressTracker.java:115) at freenet.io.AddressTracker.create(AddressTracker.java:84) at freenet.io.comm.UdpSocketHandler.(UdpSocketHandler.java:161) at freenet.node.NodeCrypto.(NodeCrypto.java:121) at freenet.node.Node.(Node.java:1489) at freenet.node.NodeStarter.start(NodeStarter.java:194) at org.tanukisoftware.wrapper.WrapperManager$11.run(WrapperManager.java:4048) I took an application snapshot with jvisualvm: Here’s the threaddump Full thread dump OpenJDK 64-Bit Server VM (25.191-b12 mixed mode): "Pooled thread awaiting work @1 for prio 5" #42 daemon prio=5 os_prio=0 tid=0x7f68005f7000 nid=0x27ae in Object.wait() [0x7f681dc9e000] java.lang.Thread.State: TIMED_WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x9d22ff80> (a freenet.support.PooledExecutor$MyThread) at freenet.support.PooledExecutor$MyThread.innerRun(PooledExecutor.java:218) - locked <0x9d22ff80> (a freenet.support.PooledExecutor$MyThread) at freenet.support.PooledExecutor$MyThread.realRun(PooledExecutor.java:189) at freenet.support.io.NativeThread.run(NativeThread.java:156) Locked ownable synchronizers: - None "Timer-0" #36 daemon prio=5 os_prio=0 tid=0x7f680009d000 nid=0x27a1 in Object.wait() [0x7f681e19f000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x9cfdf0b0> (a java.util.TaskQueue) at java.lang.Object.wait(Object.java:502) at java.util.TimerThread.mainLoop(Timer.java:526) - locked <0x9cfdf0b0> (a java.util.TaskQueue) at java.util.TimerThread.run(Timer.java:505) Locked ownable synchronizers: - None "SimpleToadletServer" #29 daemon prio=5 os_prio=0 tid=0x7f6800844800 nid=0x2788 waiting on condition [0x7f681e4a] java.lang.Thread.State: WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0x9cfdf740> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitUninterruptibly(AbstractQueuedSynchronizer.java:1976) at freenet.io.NetworkInterface.accept(NetworkInterface.java:249) at freenet.clients.http.SimpleToadletServer.run(SimpleToadletServer.java:999) at java.lang.Thread.run(Thread.java:748) Locked ownable sy
Fwd: Re: Reproduced: Re: FN cannot start
Morover, I had to delete all client* files for node to start. Regards Krzysztof Forwarded Message Subject:Re: Reproduced: Re: FN cannot start Date: Tue, 18 Jun 2019 23:11:33 +0200 From: Krzysztof To: Support Reproduced once more. Any clues? It definitely has nothing to do with JRE. Both Open and Sun on Linux Debian 64b fail after some time. Regards Krzysztof On 6/13/19 5:19 PM, Steve Dougherty wrote: Oh, interesting! Is this a symptom of a malformed client.dat.crypt? If you restore the file, does it fail in the same way again? - Steve Sent from ProtonMail Mobile On Thu, Jun 13, 2019 at 10:36 AM, Krzysztof <mailto:k...@limes.com.pl>> wrote: No, I don't. What I discovered so far, after deleting file 'client.dat.crypt', the node started normally. Of course, all downloads were gone. Maybe there is a way to test or repair this file? Regards Krzysztof On 6/13/19 12:29 PM, Arne Babenhauserheide wrote: > My node now also stopped starting. > > > Question to Krzysztof: Do you have a darknet connection? > > > When run via ./run.sh console, this is the last line I see before > startup fails: > > > jvm 2 | Deleted 0 of 0 temporary files (0 non-temp files in temp directory) in 0s > > > This is what I should see: > > > jvm 1 | Resumed 4 requests ... > jvm 1 | Initializing USK Manager > jvm 1 | Loading cache of request statuses... > jvm 1 | Initializing Node Updater > > > Disabling all plugins does not make a difference. > Starting without the wrapper does not make a difference either. > Moving tmp away does not make a difference, either. > Moving datastore to datastore.broken does not make a difference. > Moving persistent-temp to persistent-temp.broken only lets it show one > more error: > jvm 1 | Unable to resume request > freenet.clients.fcp.ClientGet@45d042f9 after loading it. > > So it looks like there is some broken state which blocks startup. > > > logs/freenet-latest.log says > > Jun 13, 2019 09:18:00:317 (freenet.io.AddressTracker, WrapperListener_start_runner, WARNING): Failed to load from disk for port : freenet.node.FSParseException: Unable to load address tracker table, assuming an unclean shutdown: Last ID was but stored > freenet.node.FSParseException: Unable to load address tracker table, assuming an unclean shutdown: Last ID was but stored > at freenet.io.AddressTracker.(AddressTracker.java:115) > at freenet.io.AddressTracker.create(AddressTracker.java:84) > at freenet.io.comm.UdpSocketHandler.(UdpSocketHandler.java:161) > at freenet.node.NodeCrypto.(NodeCrypto.java:121) > at freenet.node.Node.(Node.java:1489) > at freenet.node.NodeStarter.start(NodeStarter.java:194) > at org.tanukisoftware.wrapper.WrapperManager$11.run(WrapperManager.java:4048) > > > > I took an application snapshot with jvisualvm: Here’s the threaddump > > > Full thread dump OpenJDK 64-Bit Server VM (25.191-b12 mixed mode): > > "Pooled thread awaiting work @1 for prio 5" #42 daemon prio=5 os_prio=0 tid=0x7f68005f7000 nid=0x27ae in Object.wait() [0x7f681dc9e000] > java.lang.Thread.State: TIMED_WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x9d22ff80> (a freenet.support.PooledExecutor$MyThread) > at freenet.support.PooledExecutor$MyThread.innerRun(PooledExecutor.java:218) > - locked <0x9d22ff80> (a freenet.support.PooledExecutor$MyThread) > at freenet.support.PooledExecutor$MyThread.realRun(PooledExecutor.java:189) > at freenet.support.io.NativeThread.run(NativeThread.java:156) > > Locked ownable synchronizers: > - None > > "Timer-0" #36 daemon prio=5 os_prio=0 tid=0x7f680009d000 nid=0x27a1 in Object.wait() [0x7f681e19f000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x9cfdf0b0> (a java.util.TaskQueue) > at java.lang.Object.wait(Object.java:502) > at java.util.TimerThread.mainLoop(Timer.java:526) > - locked <0x9cfdf0b0> (a java.util.TaskQueue) > at java.util.TimerThread.run(Timer.java:505) > > Locked ownable synchronizers: > - None > > "SimpleToadletServer" #29 daemon prio=5 os_prio=0 tid=0x7f6800844800 nid=0x2788 waiting on condition [0x7f681e4a] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x9cfdf740> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitUninterruptibly(AbstractQueuedSynchronizer.java:1976) &
Re: Reproduced: Re: FN cannot start
Reproduced once more. Any clues? It definitely has nothing to do with JRE. Both Open and Sun on Linux Debian 64b fail after some time. Regards Krzysztof On 6/13/19 5:19 PM, Steve Dougherty wrote: Oh, interesting! Is this a symptom of a malformed client.dat.crypt? If you restore the file, does it fail in the same way again? - Steve Sent from ProtonMail Mobile On Thu, Jun 13, 2019 at 10:36 AM, Krzysztof <mailto:k...@limes.com.pl>> wrote: No, I don't. What I discovered so far, after deleting file 'client.dat.crypt', the node started normally. Of course, all downloads were gone. Maybe there is a way to test or repair this file? Regards Krzysztof On 6/13/19 12:29 PM, Arne Babenhauserheide wrote: > My node now also stopped starting. > > > Question to Krzysztof: Do you have a darknet connection? > > > When run via ./run.sh console, this is the last line I see before > startup fails: > > > jvm 2 | Deleted 0 of 0 temporary files (0 non-temp files in temp directory) in 0s > > > This is what I should see: > > > jvm 1 | Resumed 4 requests ... > jvm 1 | Initializing USK Manager > jvm 1 | Loading cache of request statuses... > jvm 1 | Initializing Node Updater > > > Disabling all plugins does not make a difference. > Starting without the wrapper does not make a difference either. > Moving tmp away does not make a difference, either. > Moving datastore to datastore.broken does not make a difference. > Moving persistent-temp to persistent-temp.broken only lets it show one > more error: > jvm 1 | Unable to resume request > freenet.clients.fcp.ClientGet@45d042f9 after loading it. > > So it looks like there is some broken state which blocks startup. > > > logs/freenet-latest.log says > > Jun 13, 2019 09:18:00:317 (freenet.io.AddressTracker, WrapperListener_start_runner, WARNING): Failed to load from disk for port : freenet.node.FSParseException: Unable to load address tracker table, assuming an unclean shutdown: Last ID was but stored > freenet.node.FSParseException: Unable to load address tracker table, assuming an unclean shutdown: Last ID was but stored > at freenet.io.AddressTracker.(AddressTracker.java:115) > at freenet.io.AddressTracker.create(AddressTracker.java:84) > at freenet.io.comm.UdpSocketHandler.(UdpSocketHandler.java:161) > at freenet.node.NodeCrypto.(NodeCrypto.java:121) > at freenet.node.Node.(Node.java:1489) > at freenet.node.NodeStarter.start(NodeStarter.java:194) > at org.tanukisoftware.wrapper.WrapperManager$11.run(WrapperManager.java:4048) > > > > I took an application snapshot with jvisualvm: Here’s the threaddump > > > Full thread dump OpenJDK 64-Bit Server VM (25.191-b12 mixed mode): > > "Pooled thread awaiting work @1 for prio 5" #42 daemon prio=5 os_prio=0 tid=0x7f68005f7000 nid=0x27ae in Object.wait() [0x7f681dc9e000] > java.lang.Thread.State: TIMED_WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x9d22ff80> (a freenet.support.PooledExecutor$MyThread) > at freenet.support.PooledExecutor$MyThread.innerRun(PooledExecutor.java:218) > - locked <0x9d22ff80> (a freenet.support.PooledExecutor$MyThread) > at freenet.support.PooledExecutor$MyThread.realRun(PooledExecutor.java:189) > at freenet.support.io.NativeThread.run(NativeThread.java:156) > > Locked ownable synchronizers: > - None > > "Timer-0" #36 daemon prio=5 os_prio=0 tid=0x7f680009d000 nid=0x27a1 in Object.wait() [0x7f681e19f000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x9cfdf0b0> (a java.util.TaskQueue) > at java.lang.Object.wait(Object.java:502) > at java.util.TimerThread.mainLoop(Timer.java:526) > - locked <0x9cfdf0b0> (a java.util.TaskQueue) > at java.util.TimerThread.run(Timer.java:505) > > Locked ownable synchronizers: > - None > > "SimpleToadletServer" #29 daemon prio=5 os_prio=0 tid=0x7f6800844800 nid=0x2788 waiting on condition [0x7f681e4a] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x9cfdf740> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitUninterruptibly(AbstractQueuedSynchronizer.java:1976) > at freenet.io.NetworkInterface.accept(NetworkInterface.java:249) > at freenet.clients.http.SimpleToadletServer.run(SimpleToadletServer.java:999) > at java.lang.Thread.run(Thread.java:748) > > Locked ownable synchroniz
Re: Reproduced: Re: FN cannot start
No, I don't. What I discovered so far, after deleting file 'client.dat.crypt', the node started normally. Of course, all downloads were gone. Maybe there is a way to test or repair this file? Pozdrawiam Krzysztof Jasieński On 6/13/19 12:29 PM, Arne Babenhauserheide wrote: My node now also stopped starting. Question to Krzysztof: Do you have a darknet connection? When run via ./run.sh console, this is the last line I see before startup fails: jvm 2| Deleted 0 of 0 temporary files (0 non-temp files in temp directory) in 0s This is what I should see: jvm 1| Resumed 4 requests ... jvm 1| Initializing USK Manager jvm 1| Loading cache of request statuses... jvm 1| Initializing Node Updater Disabling all plugins does not make a difference. Starting without the wrapper does not make a difference either. Moving tmp away does not make a difference, either. Moving datastore to datastore.broken does not make a difference. Moving persistent-temp to persistent-temp.broken only lets it show one more error: jvm 1| Unable to resume request freenet.clients.fcp.ClientGet@45d042f9 after loading it. So it looks like there is some broken state which blocks startup. logs/freenet-latest.log says Jun 13, 2019 09:18:00:317 (freenet.io.AddressTracker, WrapperListener_start_runner, WARNING): Failed to load from disk for port : freenet.node.FSParseException: Unable to load address tracker table, assuming an unclean shutdown: Last ID was but stored freenet.node.FSParseException: Unable to load address tracker table, assuming an unclean shutdown: Last ID was but stored at freenet.io.AddressTracker.(AddressTracker.java:115) at freenet.io.AddressTracker.create(AddressTracker.java:84) at freenet.io.comm.UdpSocketHandler.(UdpSocketHandler.java:161) at freenet.node.NodeCrypto.(NodeCrypto.java:121) at freenet.node.Node.(Node.java:1489) at freenet.node.NodeStarter.start(NodeStarter.java:194) at org.tanukisoftware.wrapper.WrapperManager$11.run(WrapperManager.java:4048) I took an application snapshot with jvisualvm: Here’s the threaddump Full thread dump OpenJDK 64-Bit Server VM (25.191-b12 mixed mode): "Pooled thread awaiting work @1 for prio 5" #42 daemon prio=5 os_prio=0 tid=0x7f68005f7000 nid=0x27ae in Object.wait() [0x7f681dc9e000] java.lang.Thread.State: TIMED_WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x9d22ff80> (a freenet.support.PooledExecutor$MyThread) at freenet.support.PooledExecutor$MyThread.innerRun(PooledExecutor.java:218) - locked <0x9d22ff80> (a freenet.support.PooledExecutor$MyThread) at freenet.support.PooledExecutor$MyThread.realRun(PooledExecutor.java:189) at freenet.support.io.NativeThread.run(NativeThread.java:156) Locked ownable synchronizers: - None "Timer-0" #36 daemon prio=5 os_prio=0 tid=0x7f680009d000 nid=0x27a1 in Object.wait() [0x7f681e19f000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x9cfdf0b0> (a java.util.TaskQueue) at java.lang.Object.wait(Object.java:502) at java.util.TimerThread.mainLoop(Timer.java:526) - locked <0x9cfdf0b0> (a java.util.TaskQueue) at java.util.TimerThread.run(Timer.java:505) Locked ownable synchronizers: - None "SimpleToadletServer" #29 daemon prio=5 os_prio=0 tid=0x7f6800844800 nid=0x2788 waiting on condition [0x7f681e4a] java.lang.Thread.State: WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0x9cfdf740> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitUninterruptibly(AbstractQueuedSynchronizer.java:1976) at freenet.io.NetworkInterface.accept(NetworkInterface.java:249) at freenet.clients.http.SimpleToadletServer.run(SimpleToadletServer.java:999) at java.lang.Thread.run(Thread.java:748) Locked ownable synchronizers: - None "Network Interface Acceptor for ServerSocket[addr=/127.15.9.6,localport=8988](0)" #28 daemon prio=5 os_prio=0 tid=0x7f6800843000 nid=0x2787 runnable [0x7f681e5a1000] java.lang.Thread.State: RUNNABLE at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:409) at java.net.ServerSocket.implAccept(ServerSocket.java:545) at java.net.ServerSocket.accept(ServerSocket.java:513) at freenet.io.NetworkInterface$Acceptor.run(
Re: FN cannot start
:47 | <-- Wrapper Stopped Regards Krzysztof On 6/12/19 1:22 AM, Dennis New wrote: On Wed, 12 Jun 2019 01:11:25 +0200, Krzysztof wrote: HI, After starting the system, the page at 127.0.0.1: looks as follows: Freenet is starting up Freenet is starting up Your Freenet node is starting up, please hold on. Current status INFO | jvm 2 | 2019/06/12 01:00:08 | Set fproxy max length to 2306867 and max length with progress to 57671680 = 57671680 INFO | jvm 2 | 2019/06/12 01:00:08 | Starting FProxy on 127.0.0.1,0:0:0:0:0:0:0:1: INFO | jvm 2 | 2019/06/12 01:00:08 | SHA1: using SUN version 1.8 INFO | jvm 2 | 2019/06/12 01:00:08 | MD5: using SUN version 1.8 INFO | jvm 2 | 2019/06/12 01:00:08 | SHA-256: using SUN version 1.8 INFO | jvm 2 | 2019/06/12 01:00:08 | SHA-384: using SUN version 1.8 INFO | jvm 2 | 2019/06/12 01:00:08 | SHA-512: using SUN version 1.8 INFO | jvm 2 | 2019/06/12 01:00:08 | AES/CTR/NOPADDING (SunJCE version 1.8): 705107ns INFO | jvm 2 | 2019/06/12 01:00:08 | AES/CTR/NOPADDING (BC version 1.59): 1980691ns INFO | jvm 2 | 2019/06/12 01:00:08 | Using JCA cipher provider: SunJCE version 1.8 INFO | jvm 2 | 2019/06/12 01:00:08 | Trying to read master keys file... INFO | jvm 2 | 2019/06/12 01:00:08 | Read old master keys file INFO | jvm 2 | 2019/06/12 01:00:08 | FNP port created on 0.0.0.0:23499 INFO | jvm 2 | 2019/06/12 01:00:08 | Testnet mode DISABLED. You may have some level of anonymity. :) INFO | jvm 2 | 2019/06/12 01:00:08 | Note that this version of Freenet is still a very early alpha, and may well have numerous bugs and design flaws. INFO | jvm 2 | 2019/06/12 01:00:08 | In particular: YOU ARE WIDE OPEN TO YOUR IMMEDIATE PEERS! They can eavesdrop on your requests with relatively little difficulty at present (correlation attacks etc). INFO | jvm 2 | 2019/06/12 01:00:08 | Creating PeerManager INFO | jvm 2 | 2019/06/12 01:00:08 | Memory is 455MB INFO | jvm 2 | 2019/06/12 01:00:08 | Setting standard 500 thread limit. This should be enough for most nodes but more memory is usually a good thing. INFO | jvm 2 | 2019/06/12 01:00:08 | Deleted 0 of 0 temporary files (0 non-temp files in temp directory) in 0s It doesn't go on now although after fresh install a few days ago it ran perfectly every day. What can I do to solve the case? You can check the wrapper.log file in freenet's folder - maybe there was more information appended to it? Also, is your computer doing anything when it reaches this point (high cpu or disk usage)? Maybe you can also try moving/deleting the freenet.ini file to make it go through the initial setup process again?
FN cannot start
HI, After starting the system, the page at 127.0.0.1: looks as follows: Freenet is starting up Freenet is starting up Your Freenet node is starting up, please hold on. Current status INFO | jvm 2 | 2019/06/12 01:00:08 | Set fproxy max length to 2306867 and max length with progress to 57671680 = 57671680 INFO | jvm 2 | 2019/06/12 01:00:08 | Starting FProxy on 127.0.0.1,0:0:0:0:0:0:0:1: INFO | jvm 2 | 2019/06/12 01:00:08 | SHA1: using SUN version 1.8 INFO | jvm 2 | 2019/06/12 01:00:08 | MD5: using SUN version 1.8 INFO | jvm 2 | 2019/06/12 01:00:08 | SHA-256: using SUN version 1.8 INFO | jvm 2 | 2019/06/12 01:00:08 | SHA-384: using SUN version 1.8 INFO | jvm 2 | 2019/06/12 01:00:08 | SHA-512: using SUN version 1.8 INFO | jvm 2 | 2019/06/12 01:00:08 | AES/CTR/NOPADDING (SunJCE version 1.8): 705107ns INFO | jvm 2 | 2019/06/12 01:00:08 | AES/CTR/NOPADDING (BC version 1.59): 1980691ns INFO | jvm 2 | 2019/06/12 01:00:08 | Using JCA cipher provider: SunJCE version 1.8 INFO | jvm 2 | 2019/06/12 01:00:08 | Trying to read master keys file... INFO | jvm 2 | 2019/06/12 01:00:08 | Read old master keys file INFO | jvm 2 | 2019/06/12 01:00:08 | FNP port created on 0.0.0.0:23499 INFO | jvm 2 | 2019/06/12 01:00:08 | Testnet mode DISABLED. You may have some level of anonymity. :) INFO | jvm 2 | 2019/06/12 01:00:08 | Note that this version of Freenet is still a very early alpha, and may well have numerous bugs and design flaws. INFO | jvm 2 | 2019/06/12 01:00:08 | In particular: YOU ARE WIDE OPEN TO YOUR IMMEDIATE PEERS! They can eavesdrop on your requests with relatively little difficulty at present (correlation attacks etc). INFO | jvm 2 | 2019/06/12 01:00:08 | Creating PeerManager INFO | jvm 2 | 2019/06/12 01:00:08 | Memory is 455MB INFO | jvm 2 | 2019/06/12 01:00:08 | Setting standard 500 thread limit. This should be enough for most nodes but more memory is usually a good thing. INFO | jvm 2 | 2019/06/12 01:00:08 | Deleted 0 of 0 temporary files (0 non-temp files in temp directory) in 0s It doesn't go on now although after fresh install a few days ago it ran perfectly every day. What can I do to solve the case? -- Regards Krzysztof
Unknown file size
When downloading files most of them have unknown file size while percent of file downloaded so far is displayed. Thus FN must know its size. Could it be fixed in some way? -- Regards Krzysztof
Re: [freenet-support] explanation needed onJava HotSpot warning
Thanks for reply. Indeed, this message has been present for some time, as I remember. But now, I decided to ask. On 12/17/2014 03:18 PM, Steve Dougherty wrote: On 12/14/2014 12:57 AM, Krzysztof wrote: There is such an info in my log file. It is written short after starting Freenet. Is it something I should do with the library? INFO | jvm 1 | 2014/12/14 06:27:49 | Java HotSpot(TM) 64-Bit Server VM warning: You have loaded library /tmp/jbigi7616677911837003715lib.tmp which might have disabled stack guard. The VM will try to fix the stack guard now. INFO | jvm 1 | 2014/12/14 06:27:49 | It's highly recommended that you fix the library with 'execstack -c libfile', or link it with '-z noexecstack'. My understanding is it has something to do with the big integer native library used for faster cryptography. I'm not certain, but I think it has always been the case but Java 7 started warning about it? I don't suppose you've found things about the message already? We will continue looking into it. Thanks, Steve ___ 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:support-requ...@freenetproject.org?subject=unsubscribe -- Regards Krzysztof ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
[freenet-support] explanation needed onJava HotSpot warning
There is such an info in my log file. It is written short after starting Freenet. Is it something I should do with the library? INFO | jvm 1 | 2014/12/14 06:27:49 | Java HotSpot(TM) 64-Bit Server VM warning: You have loaded library /tmp/jbigi7616677911837003715lib.tmp which might have disabled stack guard. The VM will try to fix the stack guard now. INFO | jvm 1 | 2014/12/14 06:27:49 | It's highly recommended that you fix the library with 'execstack -c libfile', or link it with '-z noexecstack'. -- Regards Krzysztof ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
[freenet-support] what to fix?
After starting Freenet There is such a recommendation: /It's highly recommended that you fix the library with 'execstack -c libfile', or link it with '-z noexecstack'./ Is this something to aware of? -- Pozdrawiam Krzysztof Jasieński ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
[freenet-support] info from wrapper.log
More detailed log entry: INFO | jvm 1| 2014/05/29 20:40:37 | Java HotSpot(TM) 64-Bit Server VM warning: You have loaded library /tmp/jbigi5463615249108790625lib.tmp which might have disabled stack guard. The VM will try to fix the stack guard now. INFO | jvm 1| 2014/05/29 20:40:37 | It's highly recommended that you fix the library with 'execstack -c libfile', or link it with '-z noexecstack'. Is it something I should be aware of? What should I do exactly? -- Regards KJ ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
[freenet-support] an entry from log
Every time I start FN it advises me: It's highly recommended that you fix the library with 'execstack -c libfile', or link it with '-z noexecstack'. Is it something I should be aware of? -- Regards KJ ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
[freenet-support] downloading
When files are partially downloaded where are the parts located: in node.db4o.crypt or persistent-blob.tmp? kj ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
[freenet-support] node.db4o.crypt
The file node.db4o.crypt got corrupted again. Does anybody know the structure of it or a method to extract keys from it? -- liquid ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
[freenet-support] downloads
I have some files in the download list under the note: Failed downloads: unknown type application/octet-stream I can do nothing with them: neither restart nor delete. What can I do now? liquid ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
