The article explains what the access log is. Nextcloud desktop client is accessing your webserver to synchronize files hence the requests are logged to the access log.
Ouch. I understand the apache log file. So for a single desktop I am getting about 6MB of logs a week without ever changing any files. That will add up to a lot of logs with multiple users, especially if they change files.
The logs do rotate fine. I just like to keep my logs as clean as possible without repeating data, especially when it repeats that fast. It makes it much harder to find useful bits of logs.
And what fix are you thinking of? It’s possible to change the intervals for the desktop client: https://docs.nextcloud.com/desktop/3.0/advancedusage.html#options. But the sync clients will always talk to your web server. That’s what the sync client is supposed to do. Another option could be to not use the sync client and use web dav to mount it locally on demand (but this will also produce log entries).
You are doing it wrong To reduce the number of log entries is quite impossible for a service connected to the internet nowdays. But there are tools to analyze your log files and notify you if something unusual is happening.
I’m afraid that isn’t totally true. You can often do things to cut down on spurious logging but unfortunately you can’t use rsyslog filters on apache logs. I also use logwatch to have a look at the logs daily. There may be other tools but often there is no substitute for a glance at the logs.
Can you tell me how you are using logwatch with nextcloud logs? I am trying to use it, but it’s not a recognized service in the tool. I don’t know how to customize it, besides adding the nextcloud log folder location in the logwatch config file.
My NC installation logs directly to the apache logs in /var/log/httpd. I don’t find customisng logwatch easy and do it as little as possible, just tweaking here and there.
You can change the logging for the webserver as you wish. For me it was a bit tricky, because I’m running NC in Docker. I entered in the container’s terminal, printed out these two files, and mapped them as persistent data: