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
I hope this is the right place (if it belongs to nextcloud/server let me know).
The nextcloud:fpm image apparently puts the access log to stderr. Therefore, podman writes a lot of lines like nextcloud[6638]: - - username 21/Feb/2024:09:21:45 +0000 "PROPFIND /remote.php" 207 to the error level of journald.
This makes debugging real errors a lot harder.
The only thing I was able to find is #1667, but it is using the apache image where apparently there are symlinks in /var/log/apache2/, but that folder doesn't even exist in the fpm image. Is there anything else I can do to get rid of those logs?
The text was updated successfully, but these errors were encountered:
Alright, awesome, thanks a lot for the input. I redirected it to a file for now because I couldn't get the trick from the last comment to work. Seems it's not a bug of the docker image though so sorry for asking here (at least the next person can find it hopefully)
I hope this is the right place (if it belongs to nextcloud/server let me know).
The nextcloud:fpm image apparently puts the access log to stderr. Therefore, podman writes a lot of lines like
nextcloud[6638]: - - username 21/Feb/2024:09:21:45 +0000 "PROPFIND /remote.php" 207
to the error level of journald.This makes debugging real errors a lot harder.
The only thing I was able to find is #1667, but it is using the apache image where apparently there are symlinks in
/var/log/apache2/
, but that folder doesn't even exist in the fpm image. Is there anything else I can do to get rid of those logs?The text was updated successfully, but these errors were encountered: