-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
debug file bug #21
Comments
mtail handles log file rotation (my logs rotate every 20 MB). So long as you're mounting the log directory into the container and not just the file it should work fine. Maybe it's another windows-only issue, in which case I recommend trying to run mtail natively on windows and not in a container. |
I do have mtail running on windows aswell but im not sure on how it would incorporate with the docker compose files. Any useful guides you could point me to set it up. I am using prometheus to monitor my progress remotely through my phone browser when im not at home or at work. |
If you have mtail running in windows then you can just remove the mtail service from the compose file, and update the prometheus config to scrape mtail at |
I have no issues with running mtail under Linux, logrotate works fine. Running mtail directly under windows works but introduces another problem, it prevents the log to rotate... |
@pikolos how did you run the mtail in windows, could you tell me the steps. |
This might be due to the promtail configuration:
Change the last line to:
Without that change, I would get all information added again whenever the logfile was rotated.
This is what happened to me using linux docker |
thanks @kevinkk525 , willl try that, I am also logging with v=2 to see what will happen at a logrotate. As for running mtail directly under windows just download the windows binary and run: putl .mtail config is in mtail\config and don't forget to modify the regex by adding \r add the end so it works with CRLF. Then you just modify the prometheus.yml to point to |
Since the log file is in INFO mode many logs are collected due to which after about 80MB of data a new log file is created which causes the mtail to malfunction and acquire random data for the variables.
only solution is to recompose the doc file in VSL which fixes the issue until another new log file is created and same happens again.
Probable solution: Maybe possible to increase the file size for log in chia or the mtail should automatically restart itself as the new file is created.
The text was updated successfully, but these errors were encountered: