EPS logging at debug level despite config.cfg setting of INFO
See original GitHub issueThis is 99% probably my fault, so pardon the ticket (is there a better place to ask for support help?).
I have the following in my config.cfg
:
[logging]
log_level_stdout = INFO
And EPS is running with the above config file as the first command line parameters (also, I know it’s the active config file because the xpubs I’ve been adding are being indexed).
Despite this the log file at /tmp/
has many DEBUG
level lines. And it’s growing and growing on my poor raspi.
It should be noted that the log lines that reach journald
are INFO only. So the log level seems to be applied to stdout but not to file log targets perhaps?
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Working with the logging configuration file - IBM
In section 2.1 (specify log priority), choose a log priority. Priorities range from DISABLE to DEBUG. The log priority parameter is defined at...
Read more >Configuring Logging and Debugging
The following tasks describe some logging configuration scenarios: Stop DEBUG and INFO messages from going to the log file. Allow INFO level messages...
Read more >K5532: Configuring the level of information logged for Traffic ...
Log in to the Configuration utility. Go to System > Logs > Configuration > Options. Select the log levels for the Local Traffic...
Read more >Set Up Debug Logging - Salesforce Help
From Setup, enter Debug Logs in the Quick Find box, then click Debug Logs. · Click New. · Select the entity to trace,...
Read more >Logging - OpenStack Docs
To change the logging level, add DEBUG, INFO, WARNING, or ERROR as a parameter. The logging configuration file is an INI-style configuration file, ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
✌️ https://blockstream.info/tx/fffeef228271ffb929e0f14e73256fa30ca61050cdfe3f2cb8015361780e6f3d
The point of writing to the debug log is to that bugs can be more easily studied. So ideally the messages would be there even if the user doesnt want to see them in stdout.
The old version did write far too much to the debug output, with messages that didn’t add much value. The new version writes much less. The commits which did that are https://github.com/chris-belcher/electrum-personal-server/commit/6fa79cec1023395810599f8d8fced18b30bb8610 and https://github.com/chris-belcher/electrum-personal-server/commit/659b4c00278a69c9f817f33fad2fdb7d3f34f994
And yes the new version is much faster to start up, it indirectly uses the libsecp256k1 library which does fast elliptic curve calculations. The previous version did the calculations in slow pure python.