SomberNight
commented
3 years ago Please share debug logs.
Open blackhattokyo opened 3 years ago
SomberNight
commented
3 years ago Please share debug logs.
blackhattokyo
commented
3 years ago where is locate file debug logs
blackhattokyo
commented
3 years ago i'm not sure but i think i ever see debug like " too large history"
SomberNight
commented
3 years ago where is locate file debug logs
It clearly says in the faq linked above.
Using the (Qt) GUI, go to menubar>Tools>Preferences>General, and tick “Write logs to file”. After restarting Electrum, debug logs will be written to the logs/ folder inside the datadir.
What operating system are you using?
%APPDATA%\Electrum~/.electrum~/.electrumblackhattokyo
commented
3 years ago this is debug
blackhattokyo
commented
3 years ago i already check my internet everything is work and i don't click Cancelled
SomberNight
commented
3 years ago from these log lines:
20210721T022512.001047Z | INFO | network | switching to electrum.bitaroo.net:50002:s
it looks like you manually specified to use that server as your main server
From these lines:
INFO | interface.[electrum.bitaroo.net:50002] | disconnecting due to RequestTimedOut
it looks like that server does not respond in a timely manner.
Do you run this server? Can you try connecting to another server?
blackhattokyo
commented
3 years ago yes,run this server and sometime i switch sever after it reset conect ( i ever use select auto server too) , and i get same problem
SomberNight
commented
3 years ago So you've tried with other servers too, then? Are you using a proxy or VPN or behind some restrictive firewall? How many addresses and transactions are there in your wallet, approximately?
blackhattokyo
commented
3 years ago yes i treid to with other servers i'm not using proxy or VPN and about 120000 addresses in my wallet
SomberNight
commented
3 years ago and about 120000 addresses in my wallet
120k? :O you should have started by saying that
First of all, try opening a small wallet, just with a few dozen or few hundred addresses, and see if that works.
Once you have established that works:
--oneserver option, and with auto connect disabled; this will significantly increase the timeoutsResource usage limits section in the e-x docs
in particular, try setting:
COST_SOFT_LIMIT=0
COST_HARD_LIMIT=0Also, btw, mind sharing how you ended up with a wallet that has 120k addresses? Is it e.g. used for merchant payment-processing?
singpolyma
commented
3 years ago note that your wallet is too large for most public servers, but you said you run your own server, so let's try with that
We have a similar problem using electrum daemon with 40k addresses. What is the limit when using public servers, realistically? I upgraded our electrum yesterday and wallet synced right away, but fell out of sync today again.
SomberNight
commented
3 years ago Depends on the server, as operators can tweak the defaults (as shown above). Also, the rate limiting on the server works based on IP address, and is not reset when you disconnect; so you can accumulate "cost" over time (with periodic constant ticks reducing the accumulated cost). Reconnecting many times quickly or having some very busy addresses among those subscribed are some example factors that affect resource usage "cost". So there is not really a fixed number of addresses over which you will start to have problems; but I would say over 10k is where problems might start.
You could try running your own server though;
or for testing, try fortress.qtornado.com:443:s, which has resource cost limits disabled atm.
i use electrum version 4.1.5 when i open wallet it too long time synchronizing and never synchronize finishes because it reset connect when almost to finished