Closed supervolot closed 3 years ago
@supervolot: Thanks for opening an issue, it is currently awaiting triage.
The triage/accepted label can be added by foundation members by writing /triage accepted
in a comment.
In the meantime, you can:
Hi @supervolot , thanks for your feedback. Network error could be due to your location, the peers nearby for the app to sync — you're running the node (wallet) by yourself after all. Personally, I sometimes face a disconnected node to to my internet spike dropping, and although I can still use other applications like Chrome, Spotify etc, the DeFi Wallet is affected. Please give us time to investigate. Thank you.
Hi @supervolot , thanks for your feedback. Network error could be due to your location, the peers nearby for the app to sync — you're running the node (wallet) by yourself after all. Personally, I sometimes face a disconnected node to to my internet spike dropping, and although I can still use other applications like Chrome, Spotify etc, the DeFi Wallet is affected. Please give us time to investigate. Thank you.
Hi, my internet is fine, so it looks like a bug on the new 2.3.4 wallet (ver. 2.3.3 was working fine)
Hi, got the same problem/behavior with 2.3.4 (2.3.3 Works without any issues) Run on Win Server 2019 with plenty of free storage and memory capacity in a datacenter (1 gbits up and down).
I have the same behavior. After some time when the wallet has run error messages about network errors. Old version has worked normally and i could keep running the wallet all the time.
Same issue for me with Windows server 2016 with 2 different hosting and location EU and US and defichain 2.3.3 and 2.3.4.
Issue still exist in 2.3.5. It even looks like the wallet app kills the whole connection from the pc to the internet. I have installed yesterday 2.3.5 and now i can't connect to the pc anymore from external
Still the same bug at v.2.3.5 main.log
Yes i also have same problems. What is see is that the background process for blockchain sync takes a lot more CPU power than in previous version 2.3.3. Maybe that causes the system instability. I also figured out that the Windows Firewall causes the issue. Maybe you do to many socketconnections. Check the Backgroundservices differences to previous version. Something does overhead there...
@izzycsy please take care that 2.3.3 is keep working until new version runs stable. Do not update peer nodes or keep downward compatiblity for now. I think the more CPU/RAM and Even DISK Power a Computer has, the more stable it runs. On my High Powered Gaming Notebook Version 2.3.5 did not crash right now! On my Crypto PC with small power it does not work without the issues mentioned above. Try to create a testenvironment with System with less power and test it. Be sure Windows Firewall is ON! For any further Questions i'm here to help. Thanks
@izzycsy You can create a VMPlayer VM-Machine with Windows 10 and give small Ressources to the Guest-System (3GB Ram, 1000 Mhz CPU, 1 Core and about 200GB for the Chain). I think you can reproduce it then. Cheers Roland
Still the same in Version 2.3.5. on a ryzen 3600x, 64 GB RAM and 2x 2 TB NVME SSD
Still the same in Version 2.3.5. on a ryzan 3600x, 64 GB RAM and 2x 2 TB NVME SSD
OK interesting. Wich Windows Version you Run? => WINVER CMD => Function Update Version?
Windows Server 2019 Std. [Version 10.0.17763.1879] and the latest available Updates
I have the same issue with 2.3.3 and 2.3.4 and 2.3.5. Using very large servers in 3 different hosting and locations with Windows Server 2016 and 2019 up to date. I always have this network error after few hours and i have to restart the APP. It would be very easy for the team to reproduce the issue i believe... As i have this issue with any version of the APP and any server... If the team need some servers to do their tests i can provide some.
@Faucet1313 For me problems currently exist for 2.3.4 and 2.3.5. Version 2.3.3 works normally
I downgraded yesterday to 2.3.3 and no more "Network Error" everything works finde for me with 2.3.3. Also tested 2.3.4 and 2.3.5 on a different server with the same Problem.
@izzycsy I have the same problem after update from 2.3.3 to 2.3.5 The wallet is going on error after 1-2 h and stop network. Here my log files from the wallet...
Same problem on Windows 10 on PC and on VPS (Windows 10 Enterprice)
This problem is not new, we have it already at version 2.3.1 when SPV is enabled. https://github.com/DeFiCh/app/issues/644
With version >=2.3.4 SPV is enabled by default. See https://github.com/DeFiCh/app/commit/7d82d5a5313e4baa510b805dedc150e67aff57ee
We need urgent a fix, otherwise the Atomic Swap is not useable for this users. Please @all try following to ensure that this is really the problem:
Add spv=0 in your defi.conf (Windows: C:\Users\
@Stonygan Thanks, i will try. I guess it is the windows firewall which goes down because other pc in same network with version 2.3.3 still works
It seems to work, Thank you!
Johannes Ott Künkelsgasse 19 98574 Schmalkalden
03683 665384
Von: Stonygan Gesendet: Sonntag, 16. Mai 2021 08:38 An: DeFiCh/app Cc: Otti24xx; Comment Betreff: Re: [DeFiCh/app] Network ERROR at new wallet 2.3.4 (#849)
This problem is not new, we have it already at version 2.3.1 when SPV is enabled. #644
With version >=2.3.4 SPV is enabled by default. See 7d82d5a
We need urgent a fix, otherwise the Atomic Swap is not useable for this users. Please @ALL try following to ensure that this is really the problem:
Add spv=0 in your defi.conf (Windows: C:\Users
@Stonygan What is SPV? And is there already an implementation of AtomicSwap. That whould be nice.
@thedoublejay @Stonygan @izzycsy I fully agree here to Stony. I think the first system that fails with too much connections is the Windows Firewall Service. I noticed that a few time.
Hi @Stonygan @Otti24xx @nordi6000 @rolandwellinger @m4rk88 @Faucet1313 @supervolot , thanks for your feedback, please give us time to investigate the issue. Appreciate if you can send your logs to help with investigation. Thank you!
@izzycsy I'm trying @Stonygan workaround and so far it works with no errors. Is working from this morning up to now.
@Stonygan Seems to work with spv=0 and v2.3.3 Thanks a lot.
yes, spv=0 in defi.conf works fine for now
Dear support,
System: W10
after upgrading to version 2.3.4 and 2.3.5 I got a NETWORK Error after some minutes (60-120 min) running the wallet. This seems to be not so hard, but also all browsers are concerned. This network error is also present during the resync and this is time robbing. Although the message "Network Error" appears, the wallet continues to sync, hä, although all browsers are dead (Chrome, Edge, Brave ....) . If you close the wallet during the sync, the network is back and all browsers are running. I heard in the chat, that I am not the only person with these problems. spv is not set.
RAM and C:\ have enough space.... Now I test it with less value DFI. LM is dissolved because of this error, also my Masternode plans have been stopped.
Now I have deleted all after uninstall defichain wallet. Appdata\roaming appdata\local and
I installed new with snapshot and will test a longrun over some hours waiting for the problem.
Kind regards
Olaf Knauber
OS: Win10 free Space 603 GB Defi-wallet: 2.3.5 i have the same problem and try now spv=0
i changed it to spv=0 and won't work! On v2.3.5, any suggestions! Location is US - OS is MAC
[2021-05-16 18:44:52.342] [IPC-RENDERER-error] [isBlockchainStarted] "Request failed with status code 503"
Hi all, we are currently investigating this issue regarding network disconnection. As @Stonygan reported, SPV is not enabled by default since >=2.3.4. We have removed it on the builds due to some reports of network disconnection. It seems that the network disconnection might not be due to spv only as some users report that they still encounter this issue even with SPV disconnected. Will continue investigating this issue and will update this thread once bug has been identified. Thank you.
Hi @Stonygan , looks like working after setting spv=0. Keept it running over night and no network errors so far.
@memzila @Stonygan Nice, i'll give it a try too. Thanks for your tests.
Bad surprise today. Finally got the network error with spv=0 and version 2.3.5
Hi all, we are currently investigating this issue regarding network disconnection. As @Stonygan reported, SPV is not enabled by default since >=2.3.4. We have removed it on the builds due to some reports of network disconnection. It seems that the network disconnection might not be due to spv only as some users report that they still encounter this issue even with SPV disconnected. Will continue investigating this issue and will update this thread once bug has been identified. Thank you.
Thanks for the info, you are right, code is excluded, but SPV is already active without spv=0. When i start the current downloadable 2.3.5 APP without explicit spv=0 in the conf and type spv_syncstatus in the CLI, i get infos see below. When spv=0 is in the defi.conf, i got the message SPV are disabled when i run spv_syncstatus. Its a strange error, hope we can find a solution together.
I have no problems with network errors over 36hours now, when i set spv=0.
With 2.3.3 and without spv=0, spv is disabled by default, 2.3.5 its enabled.
Sure thanks for your help @Stonygan! Will be investigating this issue
A lot more stable with spv disabled. Now i have this network error only once a day. Before i had to restart the wallet 3-4 time daily.
Hi @Faucet1313 . I think the config has not worked for you, because when i give in the command it shows the following
Configfile i use: rpcauth=some string rpcuser=some string rpcpassword=some string datadir=D:\defichain rpcconnect=127.0.0.1 testnet=0 regtest=0
[main] wallet=Wallet.dat walletdir=D:\defichain datadir=D:\defichain rpcbind=127.0.0.1 rpcport=8555 spv=0
[test] rpcbind=127.0.0.1 rpcport=8555
@memzila you are right. Thank you. But i am little bit confused when SPV is disabled my node is disabled and when i enable my node it will also enable the spv in the config.
guys any updates regarding this issue?
No success here. SVP=0 !!! Still stopping Chain Sync after a while....
@rolandwellinger add it exactly as in my config example. And what say the command spv_syncstatus?
Guys i do have the same ptoblem as you do, 2.3.5 simply won't sync the blockchain at all, whatever the tricks i try to throw a it
Any help maybe ?
We're still investigating the node issue. It's not an app issue but on the node side. We'll update you once we got a fix from the node side.
In case you're facing this. you can follow @Stonygan's workaround to disable SPV (spv=0 on [main]) in your defi.conf
.
Yes. Regarding the nodes, sometime i have this issue below and when i check the logs i see the same "Network error"
Today when i had the network error i shutdown the wallet like usual and i checked if there is still some active processses and i saw defid still active and use a lot of RAM and no way to kill the process.
Is linux affected by this error ?
Actual behavior: Wallt dont work in case of network error
Expected behavior: working wallet
How to reproduce it (as minimally and precisely as possible): run the wallet
What are your environment parameters?
Anything else we need to know? Many Errors at spv and a huge 240mb log file !!!
debug.log main.log