Re: FN cannot start
No. It didn't help. There is A part of wrapper.log below if you could look at it. STATUS | wrapper | 2019/06/12 22:47:54 | --> Wrapper Started as Daemon STATUS | wrapper | 2019/06/12 22:47:54 | Java Service Wrapper Community Edition 64-bit 3.5.20 STATUS | wrapper | 2019/06/12 22:47:54 | Copyright (C) 1999-2013 Tanuki Software, Ltd. All Rights Reserved. STATUS | wrapper | 2019/06/12 22:47:54 | http://wrapper.tanukisoftware.com STATUS | wrapper | 2019/06/12 22:47:54 | STATUS | wrapper | 2019/06/12 22:47:55 | Launching a JVM... INFO | jvm 1 | 2019/06/12 22:48:00 | setpriority() succeeded! INFO | jvm 1 | 2019/06/12 22:48:02 | BouncyCastle: BC version 1.59 INFO | jvm 1 | 2019/06/12 22:48:02 | SunPKCS11-NSS: null INFO | jvm 1 | 2019/06/12 22:48:02 | SUN: SUN version 1.8 INFO | jvm 1 | 2019/06/12 22:48:02 | SunJCE: SunJCE version 1.8 INFO | jvm 1 | 2019/06/12 22:48:02 | WrapperManager: Initializing... INFO | jvm 1 | 2019/06/12 22:48:03 | freenet.jar built with freenet-ext.jar Build #29 rv29 running with ext build 29 rv29 INFO | jvm 1 | 2019/06/12 22:48:03 | Creating config from freenet.ini INFO | jvm 1 | 2019/06/12 22:48:03 | Creating logger... INFO | jvm 1 | 2019/06/12 22:48:03 | Set interval to 10 and multiplier to 1 INFO | jvm 1 | 2019/06/12 22:48:03 | Starting executor... INFO | jvm 1 | 2019/06/12 22:48:03 | Finding old log files. New log file is /home/.../Freenet/logs/freenet-1484-2019-06-12-22.log.gz INFO | jvm 1 | 2019/06/12 22:48:03 | Using the NativeThread implementation (base nice level is 10) INFO | jvm 1 | 2019/06/12 22:48:04 | Old log file exists for this time period: /home/.../Freenet/logs/freenet-1484-2019-06-12-22.log.gz INFO | jvm 1 | 2019/06/12 22:48:04 | Renaming to: /home/.../Freenet/logs/freenet-1484-2019-06-12-22-2.log.gz INFO | jvm 1 | 2019/06/12 22:48:04 | Created log files INFO | jvm 1 | 2019/06/12 22:48:04 | Initializing Node using Freenet Build #1484 rbuild01484 and freenet-ext Build #29 rv29 with Oracle Corporation JVM version 1.8.0_212 running on amd64 Linux 4.9.0-9-amd64 INFO | jvm 1 | 2019/06/12 22:48:04 | Set fproxy max length to 2306867 and max length with progress to 57671680 = 57671680 INFO | jvm 1 | 2019/06/12 22:48:04 | Starting FProxy on 127.0.0.1,0:0:0:0:0:0:0:1: INFO | jvm 1 | 2019/06/12 22:48:04 | SHA1: using SUN version 1.8 INFO | jvm 1 | 2019/06/12 22:48:04 | MD5: using SUN version 1.8 INFO | jvm 1 | 2019/06/12 22:48:04 | SHA-256: using SUN version 1.8 INFO | jvm 1 | 2019/06/12 22:48:04 | SHA-384: using SUN version 1.8 INFO | jvm 1 | 2019/06/12 22:48:04 | SHA-512: using SUN version 1.8 INFO | jvm 1 | 2019/06/12 22:48:01 | AES/CTR/NOPADDING (SunJCE version 1.8): 700373ns INFO | jvm 1 | 2019/06/12 22:48:01 | AES/CTR/NOPADDING (BC version 1.59): 2018025ns INFO | jvm 1 | 2019/06/12 22:48:01 | Using JCA cipher provider: SunJCE version 1.8 INFO | jvm 1 | 2019/06/12 22:48:01 | Not enough entropy available. INFO | jvm 1 | 2019/06/12 22:48:01 | Trying to gather entropy (randomness) by reading the disk... INFO | jvm 1 | 2019/06/12 22:48:01 | You should consider installing a better random number generator e.g. haveged. INFO | jvm 1 | 2019/06/12 22:48:01 | Trying to read master keys file... INFO | jvm 1 | 2019/06/12 22:48:01 | Read old master keys file INFO | jvm 1 | 2019/06/12 22:48:02 | FNP port created on 0.0.0.0:23499 INFO | jvm 1 | 2019/06/12 22:48:02 | Testnet mode DISABLED. You may have some level of anonymity. :) INFO | jvm 1 | 2019/06/12 22:48:02 | Note that this version of Freenet is still a very early alpha, and may well have numerous bugs and design flaws. INFO | jvm 1 | 2019/06/12 22:48:02 | 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 1 | 2019/06/12 22:48:02 | Creating PeerManager INFO | jvm 1 | 2019/06/12 22:48:02 | Memory is 455MB INFO | jvm 1 | 2019/06/12 22:48:02 | Setting standard 500 thread limit. This should be enough for most nodes but more memory is usually a good thing. INFO | jvm 1 | 2019/06/12 22:48:03 | Deleted 0 of 0 temporary files (0 non-temp files in temp directory) in 0s STATUS | wrapper | 2019/06/12 22:50:46 | Anchor file deleted. Shutting down. INFO | jvm 1 | 2019/06/12 22:50:46 | Shutting down... INFO | jvm 1 | 2019/06/12 22:50:46 | Stopping database jobs...Stopping FEC decode threads... INFO | jvm 1 | 2019/06/12 22:50:46 | INFO | jvm 1 | 2019/06/12 22:50:46 | Waiting for jobs to finish INFO | jvm 1 | 2019/06/12 22:50:46 | FEC decoding threads finished. INFO | jvm 1 | 2019/06/12 22:50:46 | Saved persistent requests to disk INFO | jvm 1 | 2019/06/12 22:50:46 | Completed writing logs to disk. STATUS | wrapper | 2019/06/12 22:50:47
Re: FN cannot start
That’s a great use case for SSH local port forwarding the FProxy port! :) ssh -L :localhost: Sent from ProtonMail Mobile On Wed, Jun 12, 2019 at 9:19 AM, VT- Viral Therapy wrote: > Actually right now I am trying to create a project for my collage. My plan is > to run freenet on raspberry pi 3B+ and somehow use ssh/vpn/hotspot to connect > to the raspberry pi to surf freesite on my phone. > > On Wed, 12 Jun 2019, 5:26 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?
Re: FN cannot start
Actually right now I am trying to create a project for my collage. My plan is to run freenet on raspberry pi 3B+ and somehow use ssh/vpn/hotspot to connect to the raspberry pi to surf freesite on my phone. On Wed, 12 Jun 2019, 5:26 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? >
