-
-
Notifications
You must be signed in to change notification settings - Fork 414
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
[🐛 BUG]: Failed logging by file_logger_options hide permission error #1708
Comments
There another "bug" with log. If I delete a file it won't be created automatically natefinch/lumberjack#52 |
Hey @Kaspiman 👋🏻 |
@rustatian I found another problem with lamberjack library. Default file permission 600 is too strict, we can't easy read logs by The package looks abandoned natefinch/lumberjack#170 @rustatian I have another question: is it possible to reliably rotate files with config:
During rotation, a file can be deleted and re-created. Will the logs disappear at this time? |
This package is quite small. I may fork it, add it to the RR organization, and continue to maintain it.
Should be possible, but you have to track the file size by yourself. |
@rustatian It would be nice to maintain that project. I can share information about the new fork among users of the old library. This will help attract more attention to Roadrunner |
@Kaspiman Done: https://github.com/roadrunner-server/filelogger |
Oh my, there are a lot of races in this package... |
|
I've decided to move towards the official |
No duplicates 🥲.
What happened?
Maybe bug, i'm not sure
Version (rr --version)
rr version 2023.2.0 (build time: 2023-07-06T19:02:11+0000, go1.20.5), OS: linux, arch: amd64
How to reproduce the issue?
Let's say we have application in Docker container with volume for dev purpose. Log file permissions can be changed due to volume synchronization: uid:guid inside and outside has different values.
docker-compose
fragment:RR logs fragment:
The file
rr.log
will be created, but the owner will be changed almost immediately. Nothing will be written to the file, nor will it be written to the output. Silence.Previous logging settings are ignored if
file_logger_options
are specified.Maybe there should be fallback to stdout or mixed logging with the previously specified parameters (output, level, mode):
zapcore.NewMultiWriteSyncer(zapcore.AddSync(os.Stdout), w)
Relevant log output
No response
The text was updated successfully, but these errors were encountered: