On Wed, 12 Jun 2019 01:11:25 +0200, Krzysztof wrote: > HI, > > After starting the system, the page at 127.0.0.1:8888 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:8888 > 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?
