Can you tell me what kind of information should I see?
I'm trying to connect with a wallet but I cannot see significant messages in the log file...
Topic: Running Electrum server: what can I do now? (Read 159 times)
Do you see anything interesting there? Any line related to connected peers?
That's very similar to what I see because my config file includes the setting log_filters="INFO". That's relatively basic logging including system errors, problems connecting to bitcoin, transaction processing, or errors from connected clients. If no connected wallets are experiencing errors you won't see any client connection details.
To escalate logging see here: https://github.com/romanz/electrs/blob/master/doc/upgrading.md
Yeah, the log file is indeed named "LOG" all caps, no extension. Sorry about that. I was at work when I posted before and I couldn't remember the exact file name.
In my case:
Edit: Ctrl+c to stop tailing.
In my case:
Code:
tail -f /var/lib/electrs/bitcoin/LOG
Edit: Ctrl+c to stop tailing.
Do you see anything interesting there? Any line related to connected peers?
This is my output:
Code:
2023/01/28-15:24:13.833331 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1391] [config] Manual flush finished, status: OK
2023/01/28-15:24:13.833340 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1380] [headers] Manual flush start.
2023/01/28-15:24:13.833346 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1391] [headers] Manual flush finished, status: OK
2023/01/28-15:24:13.833351 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1380] [txid] Manual flush start.
2023/01/28-15:24:13.833357 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1391] [txid] Manual flush finished, status: OK
2023/01/28-15:24:13.833362 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1380] [funding] Manual flush start.
2023/01/28-15:24:13.833367 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1391] [funding] Manual flush finished, status: OK
2023/01/28-15:24:13.833372 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1380] [spending] Manual flush start.
2023/01/28-15:24:13.833378 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1391] [spending] Manual flush finished, status: OK
2023/01/28-15:24:24.005166 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1380] [config] Manual flush start.
2023/01/28-15:24:24.005745 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1391] [config] Manual flush finished, status: OK
2023/01/28-15:24:24.005773 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1380] [headers] Manual flush start.
2023/01/28-15:24:24.005792 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1391] [headers] Manual flush finished, status: OK
2023/01/28-15:24:24.005808 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1380] [txid] Manual flush start.
2023/01/28-15:24:24.005826 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1391] [txid] Manual flush finished, status: OK
2023/01/28-15:24:24.005841 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1380] [funding] Manual flush start.
2023/01/28-15:24:24.005860 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1391] [funding] Manual flush finished, status: OK
2023/01/28-15:24:24.005874 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1380] [spending] Manual flush start.
2023/01/28-15:24:24.005891 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1391] [spending] Manual flush finished, status: OK
2023/01/28-15:24:34.531561 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1380] [config] Manual flush start.
2023/01/28-15:24:13.833340 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1380] [headers] Manual flush start.
2023/01/28-15:24:13.833346 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1391] [headers] Manual flush finished, status: OK
2023/01/28-15:24:13.833351 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1380] [txid] Manual flush start.
2023/01/28-15:24:13.833357 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1391] [txid] Manual flush finished, status: OK
2023/01/28-15:24:13.833362 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1380] [funding] Manual flush start.
2023/01/28-15:24:13.833367 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1391] [funding] Manual flush finished, status: OK
2023/01/28-15:24:13.833372 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1380] [spending] Manual flush start.
2023/01/28-15:24:13.833378 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1391] [spending] Manual flush finished, status: OK
2023/01/28-15:24:24.005166 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1380] [config] Manual flush start.
2023/01/28-15:24:24.005745 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1391] [config] Manual flush finished, status: OK
2023/01/28-15:24:24.005773 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1380] [headers] Manual flush start.
2023/01/28-15:24:24.005792 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1391] [headers] Manual flush finished, status: OK
2023/01/28-15:24:24.005808 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1380] [txid] Manual flush start.
2023/01/28-15:24:24.005826 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1391] [txid] Manual flush finished, status: OK
2023/01/28-15:24:24.005841 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1380] [funding] Manual flush start.
2023/01/28-15:24:24.005860 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1391] [funding] Manual flush finished, status: OK
2023/01/28-15:24:24.005874 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1380] [spending] Manual flush start.
2023/01/28-15:24:24.005891 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1391] [spending] Manual flush finished, status: OK
2023/01/28-15:24:34.531561 744b9e6010 [db/db_impl/db_impl_compaction_flush.cc:1380] [config] Manual flush start.
Code:
tail -f /path/to/data_dir/electrs.log
If anyone connects to your server the log file will provide the queries requested.
There I have "LOG" file (without extension) and some LOG.old.
Yeah, the log file is indeed named "LOG" all caps, no extension. Sorry about that. I was at work when I posted before and I couldn't remember the exact file name.
In my case:
Code:
tail -f /var/lib/electrs/bitcoin/LOG
Edit: Ctrl+c to stop tailing.
Code:
tail -f /path/to/data_dir/electrs.log
If anyone connects to your server the log file will provide the queries requested.
There I have "LOG" file (without extension) and some LOG.old.
Now, is it discoverable by others than me?
You need to have it included in some list, to be discoverable. Remember, running an Electrum server, isn't the same as running a Bitcoin node, because the latter connects with already existent nodes (which means you're been already advertised), while the former is exclusively connected with your Bitcoin node. Not with a peer-to-peer network.Alternatively with 1209k, you can create a pull request in the Electrum repository. You don't have anything to lose if you try.
I'm running an Electrum server (under Tor) using electrs and I successfully connected an Electrum wallet to it.
Good job, electrs has been good to me for personal use.
Now, is it discoverable by others than me?
It is, but without advertising your onion address it's not likely anyone else will connect to it. At least that's what I've noticed.
How can I see if any client connect to my server?
As others have mentioned you can use Prometheus, but personally I've never done so. You can follow the log file with the utilities that are included with Linux such as the journalctl (assuming your starting electrs with systemd,) or the tail commands. For example:
Code:
journalctl -f -u electrs.service
Or
Code:
tail -f /path/to/data_dir/electrs.log
If anyone connects to your server the log file will provide the queries requested.
Check if it's included in this list, but do not fully rely on it in case your server isn't listed there: https://1209k.com/bitcoin-eye/ele.php?chain=btc
Do you know what are the criteria for which my node can appear there or not? I'm not using electrs, but have your tried "monitoring.md" from their documentations?: github.com/romanz/electrs/tree/master/doc
It uses Prometheus that is a general purpose monitoring solution... anyway I couldn't get it to work: the query suggested in the documentation is not working ("No datapoints found").You can scroll to the bottom of the page you can add it. Nothing required beyond that.
If it can see it it will add it, if it can't it will not. If it goes offline it will mark it as such.
At least that's the way it used to work, have not used 1209 in a while.
-Dave
Check if it's included in this list, but do not fully rely on it in case your server isn't listed there: https://1209k.com/bitcoin-eye/ele.php?chain=btc
Do you know what are the criteria for which my node can appear there or not? I'm not using electrs, but have your tried "monitoring.md" from their documentations?: github.com/romanz/electrs/tree/master/doc
It uses Prometheus that is a general purpose monitoring solution... anyway I couldn't get it to work: the query suggested in the documentation is not working ("No datapoints found"). 
Now, is it discoverable by others than me?
Check if it's included in this list, but do not fully rely on it in case your server isn't listed there: https://1209k.com/bitcoin-eye/ele.php?chain=btcHow can I see if any client connect to my server?
I'm not using electrs, but have your tried "monitoring.md" from their documentations?: github.com/romanz/electrs/tree/master/doc
I'm running an Electrum server (under Tor) using electrs and I successfully connected an Electrum wallet to it.
Now, is it discoverable by others than me?
How can I see if any client connect to my server?
Now, is it discoverable by others than me?
How can I see if any client connect to my server?
Jump to: