You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you are running a staking wallet, vm.log log file starts to get filled with messages
"Paying 39.999 Mwei from sender for gas ( 39999999 gas at 1 wei )" sometimes multiple times per one second.
Max size of this log file seems to be about 1GB, and it seems to be quite useless.
Purpose of this issue is to fix Hydra binaries to reduce max size of this log file (or reduce occurence of this log), so that stakers using system with low resources (e.g. raspberry pi) doesn't need to have additional 1GB of disk size for this logfile.
Some debug info:
In about 1 day of staking, log messages
"Paying 39.999 Mwei from sender for gas ( 39999999 gas at 1 wei )" were added more than 156 000 times to a log.
The text was updated successfully, but these errors were encountered:
Side note: If you would introduce some log rotation in a way that log files would be compressed, user would save LOTS of space.
E.g. my current vm.log file which is 360MB big, has been compressed to a zip/tar.gz file with size 6.8MB
When you are running a staking wallet, vm.log log file starts to get filled with messages
"Paying 39.999 Mwei from sender for gas ( 39999999 gas at 1 wei )" sometimes multiple times per one second.
Max size of this log file seems to be about 1GB, and it seems to be quite useless.
Purpose of this issue is to fix Hydra binaries to reduce max size of this log file (or reduce occurence of this log), so that stakers using system with low resources (e.g. raspberry pi) doesn't need to have additional 1GB of disk size for this logfile.
Some debug info:
In about 1 day of staking, log messages
"Paying 39.999 Mwei from sender for gas ( 39999999 gas at 1 wei )" were added more than 156 000 times to a log.
The text was updated successfully, but these errors were encountered: