-
-
Notifications
You must be signed in to change notification settings - Fork 127
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] 197 errors in the logs since 20 July 2024, 12:23:17 #460
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
this is not a container issue, nextcloud offers their own support. that said, your container logs are telling you to do some certain tasks, i do suggest doing them. closing as out of scope. (also the logs are in the bind paths our container readme says to use, you are able to just delete them if you wish. logrotate is handled by nextcloud and covered in their documentation) |
This issue is locked due to inactivity |
Is there an existing issue for this?
Current Behavior
I get 197 errors in the logs since 20 July 2024, 12:23:17 show up when I do a scan. However, I cannot find where the errors are in the appdata logs folder or anywhere else
Expected Behavior
There should be some form of place of where the logs can be looked at or have some form of rotation so the logs can be cleared and thus remove the warning.
Steps To Reproduce
this issue is on unraid and shows up when once does a scan on the overview page
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: